WCAG 1.4.2: Audio Control

Level A

Quick answer: If audio starts automatically and lasts more than three seconds, users need a way to pause, stop, or control it independently.

What This Means

On ecommerce sites, Audio Control 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 homepages autoplay brand videos with sound over the hero section. or pop-up chat widgets play greeting audio with no stop control., 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. Default autoplay media to muted unless the user explicitly starts sound.
  2. Provide a clear pause or mute control before the audio begins interfering with navigation.
  3. Keep media volume separate from system volume when background audio is essential.
  4. Audit third-party widgets and campaign embeds, not just your own code.

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 -->
<video autoplay src="hero.mp4"></video>

<!-- After -->
<video autoplay muted controls src="hero.mp4"></video>

FAQ

What is WCAG 1.4.2?
If audio starts automatically and lasts more than three seconds, users need a way to pause, stop, or control it independently.

How does WCAG 1.4.2 affect ecommerce sites?
It affects ecommerce anywhere shoppers interact with homepages autoplay brand videos with sound over the hero section. and pop-up chat widgets play greeting audio with no stop control. If those patterns are inaccessible, customers can miss product information, fail forms, or abandon checkout.

How to fix WCAG 1.4.2 violations?
Start by auditing the live storefront, then Default autoplay media to muted unless the user explicitly starts sound.; Provide a clear pause or mute control before the audio begins interfering with navigation.; Keep media volume separate from system volume when background audio is essential.. Prioritize templates and apps that repeat the issue across product, cart, checkout, and account pages.

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