Provide user controls for moving content
How many times have you visited a website that tries to get your attention with movement? Your eyes catch the scrolling text or a blinking advert, and you take notice for a second or two. More often than not, what you looked at wasn’t why you were visiting the website.
You try to return to what you were doing, except now it’s harder to focus because the movement is in the corner of your eye. You end up leaving the website because you can’t complete what you started.
That’s the effect of scrolling and blinking content on your average user and that’s enough of a reason to avoid it altogether. Now, consider the effect on your users with reading or concentration difficulties. I hope that you can understand why you must provide your users with controls to pause moving content.
What to do
- Moving, blinking or scrolling content must have an option to pause, stop or hide it; and
- Auto-updating content must have the same options; or
- An option to control frequency (see Guideline 2.2.1 for advice).
The guideline is more forgiving than I am. It lets you offer your users a pause option, but I suggest you remove anything that moves, scrolls or blinks altogether.
It also covers auto-updating content, which is where the strength of the guideline lies. Auto-updating content can be great. You could use it to show the latest sports scores, share prices or your Twitter feed. While the guideline applies to all moving, blinking and scrolling content, I’d love to see you eliminate all but auto-updating content.
You can ignore the rules of moving content if:
- The moving content does not start automatically, without user interaction.
- Your moving, scrolling or blinking content lasts less than five seconds.
- The information is not parallel with content but separate (for example, a full-page advert displayed before users reach your webpage).
- The movement is an animation that runs to show your users that something is loading, if it would otherwise look like your website was frozen.
- Guideline 2.2.1 – Timing Adjustable
- Guideline 2.3.1 – Three Flashes or Below
- Guideline 2.3.2 – Three Flashes
- Understanding Success Criterion 2.2.2 (W3C)
Free Developer Resources
Join over 3,500 subscribers on my weekly web accessibility email and get free developer resources like WCAG 2.1 Checklists and special offers.
Over 600 developers like you have learned more about the Web Content Accessibility Guidelines with my guidebook.