WCAG 1.4.2 (A)
Media autoplays with sound
What this failure is
A hero video or background music that starts playing sound the moment the page loads causes two problems. First, screen reader users cannot hear their screen reader over the sound — the speech synthesizer is talking at the same time as your video's soundtrack, and the user cannot navigate. Second, users in shared spaces (an office, a library, a train) get an unexpected blast of sound that draws attention and is embarrassing. WCAG 1.4.2 says any audio that plays automatically for more than three seconds must have a way to pause or stop it, or must be muted by default. The safest option is simply to mute autoplaying video: add muted to the tag alongside autoplay.
Reference: WCAG 1.4.2 (A) — the authoritative spec.
Who it affects
- Screen reader users: The screen reader's speech competes with the video's audio; the user cannot hear announcements and often cannot find the pause button because they cannot hear focus feedback.
- Users with cognitive or attention differences: Sudden unexpected sound is intrusive and disorienting; some users will close the tab immediately rather than search for a mute control.
- Users in public spaces: Autoplay audio in a library or open-plan office is embarrassing and often causes users to leave the site rather than dig for the mute.
- Users with anxiety or PTSD: Unexpected sound — especially voices or music — can trigger a genuine stress response; muted-by-default respects that.
How to fix it
Concrete steps for the four platforms most small e-commerce sites run on. If you use a different stack, the underlying HTML change is the same.
Shopify
For a video hero section, open Online Store > Themes > Customize, click the Video section, and confirm the Enable sound checkbox is off (it should be off by default in Dawn). If your theme is custom, open the section's Liquid file and add the muted attribute to the <video> tag: <video autoplay muted loop playsinline>. For YouTube embeds in blog posts, do not use ?autoplay=1 in the URL — leave autoplay off entirely and let the visitor start the video themselves.
WooCommerce
For the WordPress core Video block: click the block, open the sidebar, and turn Autoplay off (or turn Muted on if you must autoplay). For custom hero videos in a theme, edit the template and add muted to the <video> tag. For third-party page builders (Elementor, Divi), each has an Autoplay and a Mute toggle on the video widget — set autoplay off, or set mute on if the video needs to play automatically.
Wix
Click the video, open Settings, and turn off Auto-play. If you must autoplay a background video, use Wix's Video Box element and turn on the Mute option — Wix will automatically mute autoplaying video on mobile too, which mirrors modern browser behaviour. For pasted YouTube embeds, do not include autoplay=1 in the embed URL.
Squarespace
For the Video block: click the block, open Design, and turn off Autoplay. For a background video on a Squarespace section: click the section, open Section Background, click the video, and confirm that Play Button is on (which lets the user start the video themselves) or Mute is on if you want the video to loop silently in the background. Squarespace mutes background videos by default on modern templates, so this rule usually fires on legacy Squarespace 5 sites or on custom embeds.
Notes
Modern versions of Chrome, Safari and Firefox already block autoplay-with-sound in most contexts and require a user gesture, so this finding is often a defensive check — the browser may silence the sound even when your HTML asks for autoplay. Do not rely on that; browsers make exceptions for sites the user has previously interacted with, and the HTML is what the accessibility scanner sees.
Check your own site
Our accessibility statement scan is free and reports findings only — we do not certify sites.