Skip to main content

WCAG 2.0 · Level A · Understandable

3.2.2 On Input

Manual verification

How to validate 3.2.2 by hand

Check that changing a control’s value does not unexpectedly change context unless users have been informed beforehand.

Start with the extension result

Reopen the reported URL and reproduce the same state (for example, after expanding a menu or submitting a form). Use the result’s Highlight action when available, or its affected-element details and CSS selector, to find the reported content. Apply the checks below to that content and its context. If the element or state has changed, rescan and record that difference before deciding whether the finding still applies.

  1. Change values in selects, checkboxes, radio groups, and other inputs without submitting the form.
  2. Observe whether the page navigates, submits, opens a new window, or changes the user’s focus/context.
  3. Check for clear prior instructions and a separate action control where a change is not expected.

Evidence to record

Record the input value, resulting change, and any instruction presented before the user changed it.

Scope and exceptions

A change in content alone is not always a context change. Determine whether the user’s location, focus, or active environment changes unexpectedly.

Record the review outcome

  • Confirmed: the recorded evidence shows the requirement is not met in the tested page state, and no applicable exception explains it.
  • Not reproduced: the reported issue is absent in the current state. Record the URL, state, and affected element you checked; this does not prove other pages or states conform.
  • Needs more review: evidence is incomplete, the content requires human judgment, or an exception is uncertain. Record what remains to be checked instead of treating it as a pass.