3.2 Predictable · SC 3.2.1

A2 min read

On Focus

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

In plain language

Moving keyboard focus to an element (like tabbing onto it) should never trigger a big change by itself, such as opening a new window, submitting a form, or going to a different page.

Why it matters

Keyboard users move focus around all the time just to explore a page. If landing on an element changes the context unexpectedly, they lose their place, get confused, or trigger actions they didn't intend.

In practice

Fails this criterion

Tabbing onto a form field opens a help pop-up and moves focus into it, interrupting the user's navigation without their asking.

Meets this criterion

The same field shows helpful information without moving focus or opening anything. The pop-up only appears when the user asks for it, for example by pressing a help button.

Test it yourself

Tab through the page's interactive elements one by one, without pressing Enter or activating anything. If landing on an element changes the page, opens something, or moves you elsewhere, this criterion is failing.

Read SC 3.2.1 on the official WCAG 2.2 specification ↗