WCAG 2.0 · Level AAA · Understandable
3.2.5 Change on Request
Manual verification
How to validate 3.2.5 by hand
At Level AAA, check that context changes occur only on request or can be controlled by the user.
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.
- Use navigation links, form controls, and application settings and observe any context change.
- Determine whether the user explicitly activated a control requesting that change.
- For changes that occur automatically, check for a way to disable or postpone them and repeat the task.
Evidence to record
Record the trigger, context change, user request, and available control for automatic changes.
Scope and exceptions
This is Level AAA and broader than the focus/input change criteria. Some changes may be essential or explicitly requested by a user setting.
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.