Understandable / 3.2 Predictable
3.2.5Change on Request
Level AAAChanges of context -- opening a new window, auto-submitting, or auto-redirecting -- triggered by focus movement or input must occur only when the user explicitly requests them, or a way to stop such changes must be available. This matters most for screen reader users, who can't see the whole page at once and are more easily disoriented by unexpected changes.
Specification updated
- Enhancement#5187(opens in a new tab)Reinstate G200 as advisory for 3.2.5
Note
A detailed commentary for this success criterion is not yet available. In the meantime, this page lists related patterns, techniques, and links to the normative sources.
Related Techniques
Specific implementation techniques for meeting this success criterion. This site doesn't include the full text, so follow the links to the original W3C documents.
Sufficient Techniques(7)
- G76: Providing a mechanism to request an update of the content instead of updating automatically(opens in a new tab)waic.jp(opens in a new tab)
- G110: Using an instant client-side redirect(opens in a new tab)waic.jp(opens in a new tab)
- H76: Using meta refresh to create an instant client-side redirect(opens in a new tab)waic.jp(opens in a new tab)
- H83: Using the target attribute to open a new window on user request and indicating this in link text(opens in a new tab)waic.jp(opens in a new tab)
- SCR19: Using an onchange event on a select element without causing a change of context(opens in a new tab)waic.jp(opens in a new tab)
- SCR24: Using progressive enhancement to open new windows on user request(opens in a new tab)waic.jp(opens in a new tab)
- SVR1: Implementing automatic redirects on the server side instead of on the client side(opens in a new tab)waic.jp(opens in a new tab)
Advisory Techniques(1)
Failures(7)
- F9: Failure of Success Criterion 3.2.5 due to changing the context when the user removes focus from a form element(opens in a new tab)waic.jp(opens in a new tab)
- F22: Failure of Success Criterion 3.2.5 due to opening windows that are not requested by the user(opens in a new tab)waic.jp(opens in a new tab)
- F40: Failure due to using meta redirect with a time limit(opens in a new tab)waic.jp(opens in a new tab)
- F41: Failure of Success Criterion 2.2.1, 2.2.4, and 3.2.5 due to using meta refresh to reload the page(opens in a new tab)waic.jp(opens in a new tab)
- F52: Failure of Success Criterion 3.2.5 due to opening a new window as soon as a new page is loaded(opens in a new tab)waic.jp(opens in a new tab)
- F60: Failure of Success Criterion 3.2.5 due to launching a new window when a user enters text into an input field(opens in a new tab)waic.jp(opens in a new tab)
- F61: Failure of Success Criterion 3.2.5 due to complete change of main content through an automatic update that the user cannot disable from within the content(opens in a new tab)waic.jp(opens in a new tab)
Normative References
- Success Criterion 3.2.5 Change on Request — WCAG 2.2(opens in a new tab)The normative requirement text.
- Understanding Change on Request — W3C(opens in a new tab)Official guidance on intent, examples, and techniques.