- Level
- A
- Since
- WCAG 2.0
- Entries
- 43 / 193
2.2.2 Pause, Stop, Hide
Anything that moves, blinks, scrolls or updates by itself needs a control that lets the user pause, stop or hide it.
/ What it requires
Carousels that rotate on a timer, news tickers, animated banners, background video and feeds that refresh on their own all fall under this criterion. Movement at the edge of vision pulls attention away from the text someone is trying to read. For people with attention deficits or cognitive disabilities it can make the rest of the page unusable, and a slide that changes before a slow reader or a screen reader user has finished it takes the content away.
For moving, blinking or scrolling content the rule applies when it starts automatically, lasts more than five seconds and is shown alongside other content. Auto-updating content has no five second allowance. In both cases the user needs a mechanism to pause, stop or hide it, or, for updates, to control how often they happen. Movement that is essential to the activity is exempt, and a loading animation shown while nobody can interact with the page can be treated as essential.
/ How pages fail it
- A homepage carousel advances on a timer and offers only previous and next arrows, with no pause button.
- A hero video plays on a loop behind the headline with no control to stop it.
- A scrolling ticker of news or prices runs continuously across the top of the page.
- A live feed or scoreboard inserts new items on a timer and pushes the text the user is reading down the page.
- A pause button exists but is shown on mouse hover only or cannot be reached with the keyboard.
/ How to check it yourself
- Load the page and do nothing for more than five seconds. Note everything that is still moving, blinking, scrolling or changing.
- For each item look for a visible pause, stop or hide control close to it, and check that the control has a text name and not only an icon.
- Reach the control with Tab and operate it with Enter or Space. The movement must stop and stay stopped, not start again when focus moves on.
- Check that the paused content can still be read and that the rest of the page works while it is paused.
/ How to fix it
- Add a real button element to the carousel that switches autoplay off and on, with a text name such as Pause slides, and place it before the slides in the DOM so keyboard users meet it first.
- Or remove autoplay. A carousel that only moves when the user presses next has nothing to pause.
- For looping video, add the controls attribute or a pause button that calls pause() on the video element.
- Stop CSS animations with animation-play-state: paused when the user presses the control, and stop tickers and feeds by clearing their timer.
- Make decorative animation end within five seconds: give animation-iteration-count a finite number and keep the total running time under that limit.
/ What our scanner checks
The check carousel-no-pause looks at up to four visible regions marked aria-roledescription="carousel" or carrying carousel or slider in a class name. It passes a region that contains a button whose name or class mentions pause, stop or play, and reports the others if something inside animates endlessly or uses a CSS transition longer than 0.3 seconds. It does not time the movement, and tickers, video and feeds are outside it.
/ Who fails it, in our own measurements
One page per body, measured by automated checks on a weekly schedule. Any body that has fixed something since the last sweep will show it at the next one, and every entity page carries a right of reply.
/ Questions about this criterion
Does an auto-rotating carousel fail WCAG?
It fails 2.2.2 when it starts on its own, keeps moving for more than five seconds, sits next to other content and gives the user no way to pause, stop or hide it. Adding a pause button that works with a keyboard is enough to pass. A carousel that changes only when the user asks is not covered by the criterion.
What is the five second rule in WCAG 2.2.2?
Moving, blinking or scrolling content that starts automatically may run for up to five seconds without any control. Past that point a mechanism to pause, stop or hide it is required. The allowance does not extend to auto-updating information such as a live feed, which needs a control however short each update is.
Is an animated loading spinner a failure?
Usually not. The criterion applies to content shown in parallel with other content, and WCAG notes that an animation in a loading phase can be treated as essential when no one can interact with the page during it. A spinner that keeps turning beside content people are already reading, for longer than five seconds, is a different matter and needs a way to stop it.
