Understandable · Level AAA · Introduced in WCAG 2.0
WCAG 3.2.5: Change on Request
Published by whatisADA / Grow Wild Agency · Updated
What this criterion means
At Level AAA, context changes happen only at the user's request, or a mechanism allows the changes to be turned off. Users should retain control over their location and focus.
A practical example
A dashboard automatically redirects to a new detail view when fresh data arrives. Keep the user on the current view and offer an explicit Open update action, or provide a setting that disables the automatic transition.
How to check it
- Observe the page during normal activity, waiting periods and background updates.
- Identify navigation, focus shifts, new windows and comparable context changes.
- Verify that each follows a user request or can be disabled through an accessible mechanism.
What can be missed
A countdown warning can make a change less surprising but does not necessarily satisfy this enhanced rule. Compare this criterion separately with the A-level rules for focus and input.
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.