Goal
Avoid unexpected changes of context across the site.
Success Criterion · WCAG 3.2.5
Change on Request
Changes of context are initiated only by user request or a mechanism is available to turn off such changes.
Level AAAWCAG 2.0Understandable3.2 · Predictable
Copy button ready
What to do
Only change context (open windows, navigate, submit) when the user requests it.
Why it matters
Unexpected context changes are disorienting and can cause users to lose their place.
Success criterion
What WCAG 3.2.5 requires
Summarized directly from the official Understanding document so teams can quote the requirement accurately.
Changes of context are initiated only by user request or a mechanism is available to turn off such changes.
Intent
Why WCAG created this requirement
- Users should stay in control of navigation and major UI changes.
- Automatic context changes can cause confusion and data loss.
- User-requested changes are predictable and expected.
Benefits
Who gains when you pass
- Users with cognitive disabilities avoid disorientation.
- Keyboard and screen reader users can maintain context.
- All users avoid accidental navigation or unexpected popups.
Why it matters
User impact when this criterion fails
Summaries drawn from the Understanding document help you socialize impact statements with product stakeholders.
Automatic redirects or popups can interrupt tasks and cause loss of work.
Users may not understand why they moved to a different page/state.
Overview
This AAA criterion extends predictability: context changes should occur only when users explicitly request them, or users can disable automatic context changes.
- Avoid auto-opening new windows or navigation on timers.
- If auto-advancing is required, provide settings to disable it.
- Ensure any context change is clearly caused by the user’s action.
Reference: All summaries and highlights originate from Understanding WCAG 3.2.5 and the W3C quick reference.
Fast facts
- Conformance level
- Level AAA
- 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.
Auto redirect
Pass
Redirect occurs only after user clicks “Continue”.
Fail
Page redirects after 5 seconds with no user request.
Popup window
Pass
New window opens only when user clicks “Open in new window”.
Fail
New window opens automatically on page load.
Evidence to keep
Document conformance decisions
Capture artifacts for VPATs, procurement reviews, and regression testing.
- Document policies forbidding auto context changes except by user request.
- Maintain a list of any disableable auto behaviors and their controls.
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 for automatic context changes (auto redirects, timed popups, auto-open windows).
- Require explicit user action to trigger context changes.
- If auto behavior exists, provide a user control to disable it.
- Ensure warnings are clear when context will change.
Testing ideas
Prove conformance with evidence
- Navigate through site and confirm no unexpected context changes occur.
- Verify any context changes are tied to explicit user actions.
- If disable mechanisms exist, verify they work and persist as expected.
Related success criteria