Loading Developer Playground

Loading ...

Skip to main content
Developer Playground
Share:
Back to WCAG Explorer

Success Criterion · WCAG 3.2.2

On Input

Changing the setting of any user interface component does not automatically cause a change of context unless the user has been advised of the behavior before using the component.

Level AWCAG 2.0Understandable3.2 · Predictable
Copy button ready

Success criterion

What WCAG 3.2.2 requires

Summarized directly from the official Understanding document so teams can quote the requirement accurately.

All non-text content that is presented to users must expose an equivalent text-based alternative unless a documented exception applies.

View Understanding 3.2.2Open QuickRef techniques

Fast facts

Conformance level
Level A
WCAG version introduced
WCAG 2.0
Principle
Understandable
Guideline
3.2 · Predictable

Implementation checklist

Capture progress and blockers

  • Document how this criterion impacts your product and note any exceptions.
  • Describe the user experience goal in plain language for designers and engineers.
  • List the components, templates, or workflows that must meet this requirement.
  • Capture manual and automated testing steps for future audits.

Testing ideas

Prove conformance with evidence

  • Pair automated linting with human review to verify visual, auditory, or temporal aspects.
  • Use assistive technology walkthroughs (screen reader, keyboard, switch, voice) to validate behavior.
  • Capture screenshots or recordings that demonstrate pass/fail conditions.

Related success criteria

More from Predictable (3.2)

View all criteria
WCAG 3.2.1On FocusLevel AWCAG 3.2.3Consistent NavigationLevel AAWCAG 3.2.4Consistent IdentificationLevel AAWCAG 3.2.5Change on RequestLevel AAAWCAG 3.2.6Consistent HelpLevel A
Back to WCAG Explorer