Goal
Prevent unexpected context changes when users input data.
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
What to do
Changing a setting or field value should not automatically cause navigation or major changes without user confirmation.
Why it matters
Users may make selections accidentally; unexpected changes can cause confusion or data loss.
Success criterion
What WCAG 3.2.2 requires
Summarized directly from the official Understanding document so teams can quote the requirement accurately.
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.
Intent
Why WCAG created this requirement
- Input changes should be predictable and reversible.
- Unexpected navigation can cause disorientation and lost work.
- If auto-change is used, users must be informed before they interact.
Benefits
Who gains when you pass
- Users can explore options without being forced into navigation.
- Users with cognitive disabilities experience predictable flows.
- Keyboard and screen reader users avoid accidental redirects.
Why it matters
User impact when this criterion fails
Summaries drawn from the Understanding document help you socialize impact statements with product stakeholders.
Selecting an option in a dropdown may unexpectedly load a new page.
Users may lose unsaved form data due to auto-submit.
Exception guidelines
Use the WCAG 3.2.2 exceptions correctly
Document the rationale for each exception and note which alternative support you provide.
User advised
Auto context change is allowed if users are advised beforehand.
Requirement
Provide clear, persistent notice before interaction.
Overview
When users change a control (like selecting an option), it must not automatically navigate, submit, or significantly change context unless users are clearly informed in advance. Prefer explicit submit buttons or confirmations.
- Prefer “Select option then press Apply/Go” patterns.
- If auto-submit is used, provide clear instructions (“Selecting an option will update results”).
- Ensure changes are not surprising and can be undone.
Reference: All summaries and highlights originate from Understanding WCAG 3.2.2 and the W3C quick reference.
Fast facts
- Conformance level
- Level A
- WCAG version introduced
- WCAG 2.0
- Principle
- Understandable
- Guideline
- 3.2 · Predictable
Examples
Make success tangible for teams
Share pass/fail snapshots to coach designers, engineers, QA, and content authors.
Navigation select
Pass
User picks destination then activates “Go” button.
Fail
Selecting an option immediately navigates with no warning.
Filter panel
Pass
Filters update results and UI indicates “Results updated” without navigation.
Fail
Changing a filter submits and reloads page unexpectedly without notice.
Evidence to keep
Document conformance decisions
Capture artifacts for VPATs, procurement reviews, and regression testing.
- Document patterns for filters vs navigation selects (apply button vs auto-update).
- Capture examples where users are advised of auto-updating behavior.
Official resources
Deep dives and supporting material
Keep these links handy when writing acceptance criteria or responding to audits.
Implementation checklist
Capture progress and blockers
- Audit `onChange` handlers for navigation and auto-submission.
- Replace auto-navigation with an explicit button when feasible.
- If auto-update is intended (filters), clearly inform users and ensure it’s not a major context change.
- Preserve user input where possible to avoid data loss.
Testing ideas
Prove conformance with evidence
- Change values in selects/inputs and verify no unexpected navigation occurs.
- Confirm any auto-update behavior is announced/obvious in advance.
- Test with keyboard and screen reader to ensure behavior is predictable.
Related success criteria