WCAG 1.4.7: Low or No Background Audio
Level AAAQuick answer: Speech in prerecorded audio-only content should not compete with background sound that makes it hard to understand.
What This Means
On ecommerce sites, Low or No Background Audio 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 podcast ads on brand pages mix narration with loud music beds. or audio care instructions use ambient store noise over spoken content., 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
- Podcast ads on brand pages mix narration with loud music beds.
- Audio care instructions use ambient store noise over spoken content.
- Founder-message recordings include background tracks nearly as loud as speech.
- Support audio clips for setup guidance have distracting warehouse noise.
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.
- Reduce or remove background sound under speech-dominant audio content.
- Offer a clean spoken track when music or ambience is part of the branded version.
- Check compression settings so music does not swell over instructions.
- Use transcripts as backup but still improve the original audio clarity.
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 -->
<audio controls src="founder-message-music-heavy.mp3"></audio>
<!-- After -->
<audio controls src="founder-message-clean-voice.mp3"></audio>
FAQ
What is WCAG 1.4.7?
Speech in prerecorded audio-only content should not compete with background sound that makes it hard to understand.
How does WCAG 1.4.7 affect ecommerce sites?
It affects ecommerce anywhere shoppers interact with podcast ads on brand pages mix narration with loud music beds. and audio care instructions use ambient store noise over spoken content. If those patterns are inaccessible, customers can miss product information, fail forms, or abandon checkout.
How to fix WCAG 1.4.7 violations?
Start by auditing the live storefront, then Reduce or remove background sound under speech-dominant audio content.; Offer a clean spoken track when music or ambience is part of the branded version.; Check compression settings so music does not swell over instructions.. Prioritize templates and apps that repeat the issue across product, cart, checkout, and account pages.
Check if your store passes WCAG 1.4.7 → Free ADA Compliance Scan