Change on Request
Summary:
WCAG 3.2.5, "Change on Request," ensures that major changes on a website or application, like loading a new page or significantly altering the user interface, occur only after a user action. This criterion is particularly important for users with cognitive disabilities or those who use assistive technologies.
What:
It mandates that significant changes in the content or context on a web page should happen only in response to a user's request, not automatically.
Why:
Unexpected changes can be confusing or disorienting, especially for users who navigate differently or rely on predictability to understand and use digital content. Ensuring changes occur only upon user request enhances the usability and accessibility of web content.
Examples and Scenarios:
- Form Submission: A new page loads only after the user submits a form, not while they're still entering information.
- Settings Changes: Adjustments in settings take effect only after the user confirms or saves their choices.
- Navigation Menus: Expanding a dropdown menu or opening a new section only happens when the user selects it.
How to Comply:
- Websites: Design elements so that significant changes, like navigating to a new page or significantly altering the layout, happen only after a user action, like clicking a button.
- Mobile Apps: Ensure that changes within the app, such as moving to a new screen, are initiated by the user.
- Software Applications: Adopt similar practices, making sure that any major changes in the application's interface are user-initiated.
Exceptions:
- Real-time Updates: For functionalities that require real-time updates, like live sports scores or stock market tickers.
- User-Requested Automatic Updates: When the user has explicitly requested automatic updates, such as in a news feed.