Unexpected changes can be disorienting. Change on Request ensures that significant changes only happen when users specifically request them, keeping control in their hands and making navigation more predictable.
Who this impacts
- People with cognitive impairments: Sudden, unrequested changes can create confusion and make it difficult to stay focused on the content.
- Keyboard and screen reader users: Users relying on assistive tech need predictable, user-initiated changes to avoid losing their place.
- Everyone: Predictable navigation and user-initiated changes improve usability.
How to meet Change on Request
- Only make changes upon explicit request: Actions, like loading new content or changing the page layout, are only allowed to happen after user input (like clicking a button).
- Provide clear prompts for interactions: If a change needs to occur, provide a clear option, such as a “Show More” button, rather than automatically updating.
- Verify predictable behavior: Test that content remains stable unless a user actively requests a change.
Practical example
Meowcation’s “Catcation Deals” page lets users load more offers by clicking “Show More Catcations,” ensuring they can control how much content appears at once. This also allows keyboard-only users better access to the rest of the site (navigation, footer, etc.) without getting trapped in an infinite scroll.
Top tips
- Let users initiate changes: Ensure that any major layout or content changes are user-driven, not automatic.
- Avoid unnecessary updates: Keep pages stable and prevent auto-refreshes that may disorient users.
- Say no to infinite scrolling: When content continuously loads in as you scroll, It can be notoriously difficult for assistive technology users to work with. How do you get to the footer when the content keeps loading in and expanding the page as you go?
- Test for predictable interactions: Make sure users can navigate smoothly, without losing control due to sudden shifts.