Loading Developer Playground

Loading ...

Skip to main content
Developer Playground
Share:
Back to WCAG Explorer

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

Success criterion

What WCAG 2.2.2 requires

Summarized directly from the official Understanding document so teams can quote the requirement accurately.

All non-text content that is presented to users must expose an equivalent text-based alternative unless a documented exception applies.

View Understanding 2.2.2Open QuickRef techniques

Fast facts

Conformance level
Level A
WCAG version introduced
WCAG 2.0
Principle
Operable
Guideline
2.2 · Enough Time

Implementation checklist

Capture progress and blockers

  • Document how this criterion impacts your product and note any exceptions.
  • Describe the user experience goal in plain language for designers and engineers.
  • List the components, templates, or workflows that must meet this requirement.
  • Capture manual and automated testing steps for future audits.

Testing ideas

Prove conformance with evidence

  • Pair automated linting with human review to verify visual, auditory, or temporal aspects.
  • Use assistive technology walkthroughs (screen reader, keyboard, switch, voice) to validate behavior.
  • Capture screenshots or recordings that demonstrate pass/fail conditions.

Related success criteria

More from Enough Time (2.2)

View all criteria
WCAG 2.2.1Timing AdjustableLevel AWCAG 2.2.3No TimingLevel AAAWCAG 2.2.4InterruptionsLevel AAAWCAG 2.2.5Re-authenticatingLevel AAAWCAG 2.2.6TimeoutsLevel AAA
Back to WCAG Explorer