For AI agents and LLMs: a machine-readable index is available at llms.txt. A plain-Markdown version of any documentation page is available by appending .md to its URL.
Skip to main content

Pause, Stop, Hide (2.2.2)

Moving, blinking, scrolling, or auto-updating content must include a mechanism to pause, stop, or hide it.

WCAG Reference

Applies to: WCAG 2.0, WCAG 2.1, WCAG 2.2 Introduced in: WCAG 2.0 | Level: A | Read the official specification →

What this rule checks​

The scanner identifies animations, auto-scrolling regions, and auto-updating feeds that run for more than five seconds without user controls.

Why it matters​

Motion on screen can be distracting or physically harmful for users with attention disorders, vestibular conditions, or cognitive disabilities. Continuous updates can also interfere with screen-reader announcements.

Common failure patterns​

  • auto-scrolling news tickers or marquees with no pause button
  • animated hero banners that loop indefinitely
  • live data feeds that push updates into the DOM without user consent
  • background video that plays continuously with no stop control

Remediation guidance​

  • add visible pause, stop, or hide controls for any auto-moving content
  • respect the prefers-reduced-motion media query to minimize or remove animation
  • for live feeds, allow the user to opt in to updates rather than pushing them automatically
  • ensure controls are keyboard accessible and announced by screen readers
Last updated on

Terminal First Testing With Kane CLI

Natural language browser & mobile app tests right from terminal.

×
Schedule Your Personal Demo
Kane CLI terminal

Help and Support

Related Articles