Understandable · Level A · Introduced in WCAG 2.0
WCAG 3.2.1: On Focus
Published by whatisADA / Grow Wild Agency · Updated
What this criterion means
Receiving focus must not itself trigger a change of context. Users need to inspect a control before deciding to activate it, especially when navigating with a keyboard or assistive technology.
A practical example
Tabbing to a subscription field immediately opens a new page. Remove the focus-triggered navigation and provide a clearly labeled action that the user activates when ready.
How to check it
- Move focus through all controls without activating them.
- Watch for navigation, new windows, unexpected focus relocation or other context changes.
- Repeat in menus, conditional forms and embedded widgets, where focus handlers may behave differently.
What can be missed
Revealing helpful content is not automatically a change of context, but it can have its own requirements. Distinguish ordinary state information from changes that disrupt the user's current task or location.
Record your test
Use this worksheet to record what you actually checked. Notes stay on this device when you choose Save; they are not sent to us. Avoid personal or confidential information on shared devices.
These are your observations, not automated results or a conformance certificate. A complete evaluation needs appropriate scope, supported technologies, all applicable criteria and relevant page states.
Primary sources and scope
This is independent implementation guidance with original examples. The linked standard contains the full definitions, exceptions and conformance requirements. A criterion or checklist alone does not establish legal applicability or whole-site conformance.