WCAG 2.2.2: Pause, Stop, Hide

Level A

Quick answer: Moving, blinking, scrolling, or auto-updating content needs controls so users can pause or stop it when it distracts from shopping.

What This Means

On ecommerce sites, Pause, Stop, Hide usually shows up in repeating storefront components such as product cards, PDP media, search results, cart drawers, checkout forms, and support content. If the live experience depends on patterns like homepage hero carousels auto-rotate with no pause button. or marquee announcement bars scroll endlessly across the screen., disabled shoppers can lose context or get blocked before purchase.

This criterion matters because D2C teams often fix the homepage but miss reusable app blocks, campaign pages, and mobile-specific UI. The practical standard is simple: build the same outcome for keyboard users, screen-reader users, low-vision users, and anyone relying on captions, labels, structure, or predictable behavior.

For Shopify, WooCommerce, and custom storefronts, the fastest remediation path is usually template-level work. Fix the repeated component once, then retest every place it appears across browse, buy, and post-purchase journeys.

Common Violations on Ecommerce Sites

How to Fix It

Start with the live customer journey, not isolated components in Storybook or Figma. Audit the problem on category pages, product detail pages, quick views, cart, checkout, account, and help templates.

  1. Provide pause or stop controls for carousels, sliders, and animated promos.
  2. Avoid motion that continues longer than five seconds unless it is essential.
  3. Let users dismiss countdowns or flashing urgency widgets.
  4. Keep auto-updating stock or price modules from re-rendering aggressively during data entry.

On Shopify, fix the theme section or app block that repeats the defect. On WooCommerce and WordPress, update the template override or plugin output. In custom React or headless storefronts, move the fix into shared components so merchandisers cannot reintroduce the issue with every campaign.

Code Example

<!-- Before -->
setInterval(nextSlide, 4000);

<!-- After -->
const autoplay = setInterval(nextSlide, 4000);
pauseButton.addEventListener('click', () => clearInterval(autoplay));

FAQ

What is WCAG 2.2.2?
Moving, blinking, scrolling, or auto-updating content needs controls so users can pause or stop it when it distracts from shopping.

How does WCAG 2.2.2 affect ecommerce sites?
It affects ecommerce anywhere shoppers interact with homepage hero carousels auto-rotate with no pause button. and marquee announcement bars scroll endlessly across the screen. If those patterns are inaccessible, customers can miss product information, fail forms, or abandon checkout.

How to fix WCAG 2.2.2 violations?
Start by auditing the live storefront, then Provide pause or stop controls for carousels, sliders, and animated promos.; Avoid motion that continues longer than five seconds unless it is essential.; Let users dismiss countdowns or flashing urgency widgets.. Prioritize templates and apps that repeat the issue across product, cart, checkout, and account pages.

Check if your store passes WCAG 2.2.2 → Free ADA Compliance Scan