Loading...
Loading content...
Loading content...
Don't change context automatically; let the user request it.
Why it matters: Automatic changes can be disorienting.
Changes of context are initiated only by user request or a mechanism is available to turn off such changes.
What This Means: This success criterion requires that context changes (like page navigation, focus changes, or content updates) only occur when users explicitly request them, OR that users can disable automatic context changes. This gives users control over when major changes happen.
Why It's Important: Automatic context changes can be disorienting and disruptive, especially for users with cognitive disabilities or those using screen readers. When content changes unexpectedly, users can lose their place, become confused, or accidentally trigger actions they didn't intend. By requiring explicit user request or providing controls to disable automatic changes, users maintain control over their experience.
Remove automatic navigation, form submission, or content updates. If automatic updates are necessary (like live data feeds), provide controls to pause or disable them. Require explicit user action (button clicks, Enter key presses) for navigation and form submission. Make disabling automatic updates easy and discoverable. Provide clear settings for controlling automatic behaviors.
This criterion ensures that users with cognitive disabilities can access and understand the content, improving their overall experience and ability to use the website effectively.
This criterion ensures that screen reader users can access and understand the content, improving their overall experience and ability to use the website effectively.
Impact: When this criterion is properly implemented, it removes barriers for these user groups and creates a more inclusive web experience for everyone.
Selecting an option automatically navigates to a new page without user confirmation.
<select onchange="window.location = this.value">
<option value="/page1">Page 1</option>
<option value="/page2">Page 2</option>
</select>Selecting an option requires clicking a button to navigate.
<select id="page-select">
<option value="/page1">Page 1</option>
<option value="/page2">Page 2</option>
</select>
<button onclick="navigate()">Go</button>This success criterion benefits the following user groups:
Tip: Use this checklist during development and testing to ensure all requirements for 3.2.5 Change on Request are met. Check off items as you complete them.
To meet this success criterion, ensure the following requirements are met:
While meeting the minimum requirements ensures compliance, consider these enhancements for a better user experience:
If I provide a way to disable auto-updates, I can have automatic changes.
While providing disable options is acceptable, it's better practice to avoid automatic changes entirely. Make manual control the default.
Auto-refreshing content is fine if it's just updating data.
Even data updates can be disorienting. Provide controls to pause or disable auto-updates, or make updates user-initiated.
Automatic page refreshes or content updates without disable option.
Add controls to pause or disable automatic updates. Allow users to refresh manually when they choose.
Form submissions that occur automatically without user action.
Require explicit submit button clicks. Never auto-submit forms without clear user intent.
Navigation that occurs automatically without user request.
Require explicit user action for navigation. Add 'Go' buttons or require Enter key presses.
Note: These are official W3C resources for 3.2.5. For the most up-to-date information and detailed technical guidance, always refer to the official W3C documentation.
Implementing 3.2.5 Change on Request correctly requires understanding your specific context. Code solutions vary significantly based on multiple factors:
HTML, React, Vue, Angular, PHP, Python, and other frameworks each have different patterns and best practices.
Server-side rendering, client-side rendering, static generation, and hybrid approaches require different solutions.
Your existing components, styling approach, and UI library influence how accessibility must be implemented.
Your specific user base, content type, and interaction patterns determine the most appropriate implementation.
We provide tailored implementation guidance by analyzing your specific technology stack, coding patterns, design system, and project requirements. Our team reviews your codebase and provides custom solutions that integrate seamlessly with your existing architecture.
Get Custom Implementation HelpPart of
Understandable PrincipleGuideline
3.2 Predictable