WCAG Guideline 2.2.2: Pause, Stop, Hide Explained
Estimated read time: 7–8 minutes
Guideline 2: Operable
The Operable principle ensures that all users can interact with and control web content, regardless of their abilities. This includes giving users control over moving, blinking, or auto-updating content that can be distracting or inaccessible.
Guideline 2.2: Enough Time
Guideline 2.2 focuses on making sure users have enough time and control over content that changes or moves. This is especially important for users with cognitive or visual disabilities.
What Is Guideline 2.2.2 Pause, Stop, Hide?
"For any moving, blinking, scrolling, or auto-updating information, users must be able to pause, stop, or hide it."
Guideline 2.2.2 Pause, Stop, Hide is a requirement in the Web Content Accessibility Guidelines (WCAG) .
- Users must be able to pause, stop, or hide any moving, blinking, or auto-updating content.
- Applies to carousels, news tickers, auto-refreshing feeds, and similar elements.
- Does not apply to animations that are essential or last less than five seconds.
This ensures users can control moving, blinking, or auto-updating content and aren’t distracted or excluded by motion.
For more, see Does WCAG Pause, Stop, Hide Apply to Simple Animations? (BOIA) .
Why Does It Matter?
- Inclusivity: Moving or blinking content can distract or trigger users with cognitive or neurological disabilities.
- Legal Compliance: Pause, Stop, Hide is a Level A requirement in WCAG 2.1 and 2.2.
- Usability: Prevents frustration and improves focus for all users.
For more, see W3C’s guidance on moving content .
What Needs to Support Pause, Stop, Hide?
- Carousels and sliders
- News tickers and banners
- Animations and auto-updating content
- Any moving, blinking, or scrolling information
All must provide a way to pause, stop, or hide the content.
How to Make Content Pause, Stop, or Hide
- Provide visible controls to pause, stop, or hide moving content
- Ensure controls are keyboard accessible
- Document all controls and options
- Test with users who are sensitive to motion
For more, see the W3C's Pause, Stop, Hide Techniques .
Common Mistakes to Avoid
- No way to pause or stop moving content
- Controls not accessible by keyboard
- Not documenting controls
- Not testing with users who are sensitive to motion
Differences Between A, AA, and AAA for Guideline 2.2.2 in WCAG 2.2
- Level A: Requires users can pause, stop, or hide moving, blinking, or auto-updating content. This is the core requirement for 2.2.2 and is mandatory for basic accessibility.
- Level AA: For Guideline 2.2.2, there are no additional requirements beyond Level A in WCAG 2.2. Meeting Level A for this guideline also satisfies Level AA.
- Level AAA: For Guideline 2.2.2, there are no additional requirements beyond Level A in WCAG 2.2. Meeting Level A for this guideline also satisfies Level AAA.
For more, see the W3C’s official documentation for 2.2.2 Pause, Stop, Hide .
Quick Checklist
- All moving, blinking, or auto-updating content can be paused, stopped, or hidden
- Controls are visible and keyboard accessible
- All controls are documented for users
- Tested with users who are sensitive to motion
Summary
Guideline 2.2.2 is essential for preventing distractions and supporting users with cognitive or neurological disabilities. By allowing users to pause, stop, or hide moving content, you support users with disabilities, improve usability, and meet legal requirements. Test your site regularly and make content control a core part of your development process.