Level AWCAG 2.2

3.2.1 On Focus

When any component receives focus, it does not initiate a change of context.

Why it matters

Keyboard users

If Tabbing through elements triggers navigation or popups, keyboard operation becomes impossible.

Motor impairment

Switch device users cannot precisely control focus, so unexpected changes can be catastrophic.

Cognitive impairment

Unexpected changes of context cause confusion and make users lose track of where they are.

Screen readers

When focus movement changes the screen, the reading position resets and information is lost.

Live demo

Context changes on focus

Radio button selection

Choose a shipping method:

Standard shippingExpressSame-day delivery

Focus on a text field

Email address:

A popup appears as soon as the field receives focus

Simply receiving focus must not trigger navigation, popups, or form submission. Wait for an explicit user action such as click, Enter, or Space.

Persona perspective

Nakamura (50) — Upper-limb motor impairment

I operate my PC with a head switch. Focus moves via scanning, so it can land on elements unintentionally. Whenever that triggers a popup or page change, I can't get back to what I was doing.

Checkpoints

Simply receiving focus does not navigate to a new pageFocus does not automatically open popups or modalsFocus does not auto-submit formsonfocus handlers do not cause changes of contextTooltips shown on focus are not considered changes of context (OK)

References

→ Understanding SC 3.2.1 (W3C)

→ Related: 3.2.2 On Input, 2.4.7 Focus Visible