Success criterion 3.2.5
Change on Request
Changes in context are only made upon the user's request, preventing disorientation or confusion by ensuring users have control over when changes occur.
- Level AAA
- Principle 3: Understandable
- Guideline 3.2: Predictable
In a user’s words
“Don't move the ground beneath me unless I say so. Changes should happen on my cue!”
What each role can do
- Product manager
- Design functionality that requires explicit user action to initiate any change in context.
- Designer
- Ensure that user interfaces are designed to minimize unexpected changes, providing controls for users to initiate changes.
- Developer
- Implement mechanisms that prevent automatic context changes unless initiated by the user.
- Tester
- Test to ensure that context changes do not occur without user initiation or clear options to disable such changes.
Once it is fixed
“Being in control of changes makes me feel empowered and oriented. Thanks for putting me in the driver's seat!”
Share this with your team
The quotes are written to illustrate the criterion. They are not testimonials from real people. For the official wording, find 3.2.5 in the W3C quick reference for WCAG 2.2 (opens in a new tab).
Or press ←the left arrow and →the right arrow.