What WCAG 2.2.2 Requires
Moving, blinking, scrolling or auto-updating content that starts automatically and lasts more than 5 seconds needs a way to pause, stop or hide it.
New to this criterion? Read our plain-English guide, WCAG 2.2.2 Pause, Stop, Hide Explained in Plain English, with examples and code.
Can AccessBell Test This Automatically?
Yes. AccessBell's scanner runs axe-core, which includes 2 rules that catch code-level failures of this criterion:
blink— Ensure <blink> elements are not used (details (opens in a new tab))marquee— Ensure <marquee> elements are not used (details (opens in a new tab))
This criterion is included in: WCAG 2.2 AA Checker, WCAG 2.1 AA Checker, ADA Compliance Checker, Section 508 Checker, EN 301 549 Checker.
How to Test It by Hand
Find any auto-rotating carousel, ticker or auto-refreshing content and check for a visible pause or stop control.
Common Failures
- A homepage image carousel auto-rotates with no pause button.
- A live-updating stock ticker or news feed has no way to stop it.
Related Criteria in Enough Time
WCAG 2.2.2 Questions
What does WCAG 2.2.2 require?
Moving, blinking, scrolling or auto-updating content that starts automatically and lasts more than 5 seconds needs a way to pause, stop or hide it.
Can AccessBell test WCAG 2.2.2 automatically?
Yes. AccessBell runs 2 automated rules that can catch failures of this criterion, including in our WCAG 2.2 AA Checker, WCAG 2.1 AA Checker, ADA Compliance Checker, Section 508 Checker, EN 301 549 Checker.
What level is WCAG 2.2.2?
Level A, added in WCAG 2.0.
Sources
- W3C: Understanding 2.2.2 Pause, Stop, Hide (opens in a new tab)
- W3C: Web Content Accessibility Guidelines (WCAG) 2.2 (opens in a new tab)
This page explains a technical standard and is not legal advice. See our disclaimer.