
Success criterion 3.2.1
On Focus
When any component receives focus, it does not initiate a change of context.
- Level A
- Principle 3: Understandable
- Guideline 3.2: Predictable
In a user’s words
“Whoa, what just happened? I only tabbed in!”
What each role can do
- Product manager
- Avoid actions that would disorient the user when they focus on elements.
- Designer
- Design interfaces that don't change context when a user simply focuses on a component.
- Developer
- Make sure no scripts change the context when elements receive focus.
- Tester
- Test navigation through keyboard focus to ensure it doesn't disrupt the user experience.
Once it is fixed
“Thanks for not throwing curveballs at me. Now, navigating your site is a breeze!”
Share this with your team
The quotes are written to illustrate the criterion. They are not testimonials from real people. For the official wording, find 3.2.1 in the W3C quick reference for WCAG 2.2 (opens in a new tab).
Or press ←the left arrow and →the right arrow.