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.
Can AccessBell Test This Automatically?
Not fully. Like most WCAG criteria that depend on meaning or context, this one needs a person to judge. AccessBell's report lists it for manual review rather than marking it pass or fail automatically, so it never gets missed.
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.
Related Criteria in Predictable
WCAG 3.2.1 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.