Goal
Give users control over moving, blinking, scrolling, or auto-updating content.
Success Criterion · WCAG 2.2.2
Pause, Stop, Hide
For moving, blinking, scrolling, or auto-updating information that starts automatically, lasts more than five seconds, and is presented in parallel with other content, there is a mechanism to pause, stop, or hide it, or to control the frequency of the update.
Level AWCAG 2.0Operable2.2 · Enough Time
Copy button ready
What to do
If content moves/updates automatically for more than 5 seconds (and is not essential), provide controls to pause, stop, or hide it.
Why it matters
Movement and auto-updates can distract users, make reading difficult, and interfere with assistive technology.
Success criterion
What WCAG 2.2.2 requires
Summarized directly from the official Understanding document so teams can quote the requirement accurately.
For moving, blinking, scrolling, or auto-updating information, all of the following are true: (1) Moving, blinking, scrolling: For any moving, blinking or scrolling information that (a) starts automatically, (b) lasts more than five seconds, and (c) is presented in parallel with other content, there is a mechanism for the user to pause, stop, or hide it unless the movement, blinking, or scrolling is part of an activity where it is essential; and (2) Auto-updating: For any auto-updating information that (a) starts automatically and (b) is presented in parallel with other content, there is a mechanism for the user to pause, stop, or hide it or to control the frequency of the update unless the auto-updating is part of an activity where it is essential.
Intent
Why WCAG created this requirement
- Motion and updates can distract and reduce comprehension.
- Auto-updating content can interfere with screen reader navigation and focus.
- Users must be able to pause or control updates to read and interact.
Benefits
Who gains when you pass
- Users with ADHD or cognitive disabilities can focus without distraction.
- Low vision users can read content without it moving away.
- Screen reader users can avoid losing position due to updates.
- Users prone to vestibular disorders can reduce motion stimuli.
Why it matters
User impact when this criterion fails
Summaries drawn from the Understanding document help you socialize impact statements with product stakeholders.
Carousels may rotate before users finish reading.
Auto-refreshing lists may change under focus, causing users to lose place.
Moving banners may obscure other content or make it hard to concentrate.
Exception guidelines
Use the WCAG 2.2.2 exceptions correctly
Document the rationale for each exception and note which alternative support you provide.
Essential
Movement or auto-updating is essential to the activity.
Requirement
Only when essential to the activity itself.
Overview
Users need control over content that moves or updates automatically (carousels, tickers, live-updating panels). Provide pause/stop/hide controls (or update frequency controls) unless the motion/update is essential.
- If content is moving for more than 5 seconds and is parallel to other content, provide pause/stop/hide.
- For auto-updating regions, allow pause or control update frequency.
- Ensure controls are keyboard accessible and labeled.
- If motion is essential (e.g., a game), document why and ensure alternatives where possible.
Reference: All summaries and highlights originate from Understanding WCAG 2.2.2 and the W3C quick reference.
Fast facts
- Conformance level
- Level A
- WCAG version introduced
- WCAG 2.0
- Principle
- Operable
- Guideline
- 2.2 · Enough Time
Examples
Make success tangible for teams
Share pass/fail snapshots to coach designers, engineers, QA, and content authors.
Carousel
Pass
Carousel includes Pause button and does not auto-advance when paused.
Fail
Carousel auto-advances every 3 seconds with no pause control.
Live feed
Pass
Live feed has “Pause updates” toggle or “Update every: 10s/30s/Off.”
Fail
Feed refreshes automatically and reorders items while user is reading.
Ticker
Pass
Scrolling ticker can be paused or hidden.
Fail
Ticker scrolls continuously with no way to stop it.
Evidence to keep
Document conformance decisions
Capture artifacts for VPATs, procurement reviews, and regression testing.
- Document carousel/ticker behavior and the user controls provided.
- Capture evidence showing pause controls and update-frequency controls.
Official resources
Deep dives and supporting material
Keep these links handy when writing acceptance criteria or responding to audits.
Implementation checklist
Capture progress and blockers
- Inventory moving/auto-updating UI (carousels, tickers, live feeds, rotating promos).
- Add pause/stop/hide controls for motion content lasting >5 seconds.
- For auto-updating content, add pause control or update frequency control.
- Ensure controls are keyboard operable and have accessible names.
- Avoid unexpected focus shifts due to updates.
- Respect user preferences like reduced motion where applicable.
Testing ideas
Prove conformance with evidence
- Identify moving/blinking/scrolling content and verify a pause/stop/hide control is present.
- Verify motion content that lasts >5 seconds can be paused.
- Identify auto-updating content and verify the user can pause or control update frequency.
- Test with keyboard and screen reader to ensure controls are operable.
- Verify motion does not resume unexpectedly after user pauses it (unless user chooses).
Related success criteria