Understandable · Level A · Introduced in WCAG 2.0
WCAG 3.2.2: On Input
Published by whatisADA / Grow Wild Agency · Updated
What this criterion means
Changing a control's setting must not unexpectedly change context unless the user was told beforehand. Explicit action buttons are often clearer than automatically navigating when a radio or select value changes.
A practical example
A question advances as soon as a radio answer is chosen, losing keyboard focus. Keep the selection on the current question and let the person press Next, then move focus predictably to the next question.
How to check it
- Change checkboxes, radio buttons and select values using keyboard and pointer input.
- Observe whether the change causes navigation, new windows, moved focus or a major context shift.
- For any automatic context change, verify an understandable warning provided before the control is used.
What can be missed
Updating a nearby price or showing relevant fields is not necessarily a context change. Evaluate the actual effect; a visible animation does not compensate for unexpected navigation or lost focus.
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.