
Success criterion 3.2.1 · Level A
On Focus

“Whoa, what just happened? I only tabbed in!”
Success criterion 3.2.1 · Level A
On Focus
When any component receives focus, it does not initiate a change of context.
Principle 3: Understandable · Guideline 3.2: Predictable
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!”
Next criterion: 3.2.2 On Input