Elements do not change without a request.
Some of your users will find automatic changes hard to deal with. Unexpected actions can interrupt their concentration and prevent them from reaching their goals. Help your users by keeping them in control and avoiding elements on your website that change automatically.
A change without a request is especially troublesome for users who navigate by keyboard, as well as those with visual disabilities or cognitive limitations.
How to Pass ‘Change on Request’
- If you have an element that updates or changes automatically (like a live news ticker), there is an option to pause this and update only when requested.
- All links open in the same window, unless it’s essential (for example, opening a transcript to a video).
- If a link does open in a new window, the user is aware of this (for example, in the anchor text of the link or by an icon).
- Forms do not auto-submit when fields are filled.
- Any redirect from one page to another is immediate.
‘Change on Request’ Tips
Avoid using the option to add a pause button wherever possible, it’s not as accessible as giving the user full control.
This guideline builds on 2.2.2 – Pause, Stop, Hide and 3.2.2 – On Input by removing some exceptions, so you may already have passed.
The best way to redirect a user from one webpage to another is to do it without them noticing. One of the simplest ways to do this is to edit a website’s .htaccess file, which is in the root directory (not all servers will allow you to edit this file, so check with your hosting provider).
Free Developer Resources
Join over 3,700 subscribers on my weekly web accessibility email and get free developer resources like WCAG Checklists and special offers.
Over 600 developers like you have learned more about the Web Content Accessibility Guidelines with my guidebook.