WCAG 3.2.1 On Focus
Simply moving keyboard focus onto an element must never trigger an unexpected change of context, such as auto-submitting a form or navigating away.
Table of contents
What WCAG 3.2.1 Requires
Simply moving keyboard focus onto an element must never trigger an unexpected change of context, such as auto-submitting a form or navigating away.
How to Test It by Hand
Tab through every field and control and confirm nothing unexpected happens (a new window, a page change, a form submission) just from receiving focus.
Common Failures
- A dropdown auto-submits the form the moment it receives focus, before the visitor has chosen an option.
- Tabbing into a field opens a new browser tab or window.
Testing WCAG 3.2.1 With AccessBell
This criterion depends on meaning or context, so it needs a person to judge. AccessBell's report lists it for manual review rather than marking it pass or fail automatically, so it is not missed.
Run a free scan to spot issues on your own pages.
Related Criteria in Predictable
- 3.2.2 On Input (Level A, WCAG 2.0)
- 3.2.3 Consistent Navigation (Level AA, WCAG 2.0)
- 3.2.4 Consistent Identification (Level AA, WCAG 2.0)
- 3.2.5 Change on Request (Level AAA, WCAG 2.0)
- 3.2.6 Consistent Help (Level A, WCAG 2.2)
Frequently Asked Questions
What does WCAG 3.2.1 require?
Simply moving keyboard focus onto an element must never trigger an unexpected change of context, such as auto-submitting a form or navigating away.
Can AccessBell test WCAG 3.2.1 automatically?
Not fully. This criterion needs a person to judge, so AccessBell's report lists it for manual review rather than marking it pass or fail on its own.
What level is WCAG 3.2.1?
Level A, added in WCAG 2.0.
Sources
- W3C: Understanding 3.2.1 On Focus (opens in a new tab)
- W3C: Web Content Accessibility Guidelines (WCAG) 2.2 (opens in a new tab)
This page explains a technical standard and is not legal advice. See our disclaimer.