What this criterion requires
Merely focusing an element must not trigger a change of context: no navigation, form submission, focus jump or new window just because something received focus.
Who it helps
Keyboard and screen reader users who must be able to explore safely.
Example: fails vs passes
input.addEventListener('focus', () => location.href = '/search');
/* focusing only highlights; navigation happens on explicit activation */
Focus must be safe. Nothing may navigate, submit or move focus just because an element was reached.
How to meet and fix it
- Trigger changes on activation (Enter, click), never on focus itself
Common failures auditors find
- Dropdowns that navigate the moment an option is focused with arrow keys
Automated scanning catches a share of these instantly - run a free check - and a manual audit covers the judgement calls a tool cannot make.
Sources
- W3C, Understanding 3.2.1: On Focus - w3.org/WAI
- W3C, How to Meet 3.2.1 (quick reference) - w3.org/WAI/quickref
Last updated . Reviewed by the EqualWeb accessibility team.
Does your site pass 3.2.1?
Run a free automated check now, or have certified IAAP/CPWA auditors test every criterion and document the result.