WCAG (Level AAA) SC 3.2.5 Change on Request (w3.org)
Issue description
WCAG 3.2.5, “Change on Request” focuses on giving users control over changes of context that might occur on a web page. This Level AAA criterion recognizes that some users, particularly those with cognitive disabilities, may find unexpected or automatic changes disorienting or disruptive.
Many websites have features that automatically change the context of the page, such as:
- Automatic redirects: Redirecting users to a different page without their explicit action.
- Opening new windows: Opening new browser windows or tabs without warning.
- Content updates: Automatically updating or replacing content on the page.
- Layout changes: Changing the layout of the page dynamically.
These changes can be problematic for users with:
- Cognitive disabilities: Users with cognitive disabilities may find it difficult to understand or adapt to sudden changes in context. This can lead to confusion and disorientation.
- Attention deficit disorders: Unexpected changes can be particularly disruptive for users with attention deficit disorders, making it hard to maintain focus.
- Assistive technology users: Automatic changes can interfere with the operation of assistive technologies, such as screen readers.
WCAG requirements
This guideline requires that changes of context are initiated only by user request or the user can turn off such changes. This means:
- User control: Provide users with clear controls to initiate changes of context, such as buttons or links.
- Disable changes: Offer a mechanism for users to disable automatic changes of context if they prefer.
- Warnings and confirmations: If automatic changes are essential, provide clear warnings and confirmations before they occur.
Benefits
- Predictability: Users can anticipate and control changes of context, making the website more predictable and less disorienting.
- Reduced distractions: It minimizes disruptions and helps users maintain focus.
- Improved user experience: It gives users more control over their browsing experience.
Essentially, this guideline promotes a more user-controlled and predictable web experience by ensuring that changes of context happen only when the user explicitly requests them or has the option to disable them. This is particularly beneficial for users with cognitive disabilities who may be more sensitive to unexpected changes.
Related requirements
The following WCAG source criteria are often related to this as well. They can provide additional insights into specific challenges you may be encountering.
- WCAG (Level A) SC 3.2.1 On Focus
- WCAG (Level A) SC 3.2.2 On Input
- WCAG (Level AA) SC 3.2.3 Consistent Navigation
- WCAG (Level AA) SC 3.2.4 Consistent Identification
- WCAG 2.2 (A) SC 3.2.6 Consistent Help
Who this issue impacts
Follow the links for additional information on user impairments:
Suggestions for remediation
Remediating WCAG 3.2.5, “Change on Request” involves ensuring that changes of context within your website are initiated only by user request, or that users have the option to turn off such changes. Here’s how:
User-initiated changes
- Explicit actions: Ensure that changes of context occur only when the user takes an explicit action, such as clicking a link, button, or form submission. Avoid automatic redirects, pop-ups, or content updates that are not triggered by user interaction.
- Clear controls: Provide clear and accessible controls for any actions that might cause a change of context. For example, use buttons with clear labels to trigger navigation or content updates.
Provide options to disable changes
- User settings: Offer a setting or preference that allows users to disable automatic changes of context. This could include options to:
- Prevent automatic redirects.
- Disable pop-up windows.
- Stop automatic content updates.
- Clear instructions: Provide clear instructions on how to disable these changes.
Warnings and confirmations
- Essential changes: If automatic changes are essential for functionality or security, provide clear warnings and confirmations before they occur.
- Example: Before automatically redirecting a user to a different page, display a message like, “You will be redirected to the homepage in 10 seconds. Click here to cancel.”
- Sufficient time: Give users enough time to react to the warning and take action if needed.
Testing
- Keyboard and mouse testing: Test the website using both keyboard and mouse interactions to ensure that changes of context occur only when expected.
- Assistive technology testing: Test with screen readers to ensure that users are informed about any changes of context and have control over them.
- User testing: Conduct user testing with people with cognitive disabilities to get feedback on the predictability and usability of the website’s interactions.
Examples
- Automatic redirects: Instead of automatically redirecting users after a form submission, provide a “Continue” button that they can click to proceed to the next page.
- Opening new windows: Provide a clear indication that a link will open in a new window (e.g., by adding “(opens in new window)” to the link text) and use target=”_blank” with rel=”noopener” in the link tag.
- Content updates: Instead of automatically updating content on the page, provide a “Refresh” button or a control that allows users to initiate the update.
By implementing these techniques, you can create a more predictable and user-controlled experience, minimizing unexpected changes and making your website more accessible to everyone, particularly those with cognitive disabilities who may be more sensitive to sudden changes in context.
