Success Criteria

WCAG 3.2.1 On Focus

Success Criterion 3.2.1 requires that when a user interface component receives focus, it doesn't trigger a change of context. It's a Level A criterion under Guideline 3.2 (Predictable).

What counts as a "change of context"

A change of context means something significant happens beyond the expected visual focus indicator: a new browser window opens, focus jumps elsewhere unexpectedly, a form submits, the current page navigates away, or the meaning of the page changes substantially — all without the user having done anything beyond simply moving focus to an element (tabbing to it, or a screen reader landing on it during navigation).

Why this violates a basic expectation

Moving focus is supposed to be a safe, non-committal action — a user should be able to Tab through a page freely to explore what's there, the same way a sighted user can look around a page with their eyes without anything happening as a side effect. If merely landing on a field can trigger a submission or navigate away, keyboard and screen reader users lose the ability to safely explore a page's structure at all; every Tab press becomes a gamble.

Common failure patterns

• A dropdown/select element that navigates to a different page the instant it receives focus (rather than waiting for an actual selection)
• A form field that auto-submits the entire form on focus, rather than on an explicit submit action
• Focusing an element that triggers an unexpected popup or new window to open

The related but distinct criterion: On Input (3.2.2)

This criterion is specifically about focus alone triggering unexpected changes. 3.2.2 On Input covers the related but distinct case of a user changing a value (typing, selecting an option) unexpectedly triggering a context change — the two are often discussed together since they protect the same underlying expectation (interacting with a form shouldn't produce surprising side effects) at two different interaction points.

The fix

Reserve context-changing actions (navigation, submission, opening new windows) for explicit user actions — a submit button click, an explicit "Go" action — never as an automatic side effect of focus alone landing on an element.

Common questions

What is WCAG 3.2.1 On Focus?

A Level A criterion: simply focusing a control (via Tab or click) must not cause an unexpected change of context like a page navigation or popup.

What is an example violation?

A dropdown that navigates to a new page as soon as it receives focus, or a field that opens a modal just on focus, disorienting keyboard users.

What counts as a change of context?

Opening a new window, moving focus, automatically submitting a form, or substantially changing page content in a way that disorients the user.