Fix · Serious · cited in audits

How to fix: auto-playing video with sound

Video plays sound on page load with no immediate pause control. Background audio competes with screen reader announcements.

WCAG references
1.4.2
Severity
Serious

What it looks like in the wild

Video plays sound on page load with no immediate pause control.

The screen-reader user, keyboard user, or low-vision user encountering this issue does not get an error message. The page just stops working for them. Which is why this kind of bug rarely shows up in your error tracker; it shows up in support tickets, lawsuits, and abandoned conversions.

Why it fails WCAG

Background audio competes with screen reader announcements.

Map this back to 1.4.2 when you log the bug. Auditors and procurement teams expect that mapping; "broken" is not enough context.

The wrong pattern (avoid)

HTML
<video autoplay src="/hero.mp4"></video>

The right pattern (copy this)

HTML
<video src="/hero.mp4" muted controls playsinline></video>

Notes from real audits

  • Muted autoplay is acceptable; sound autoplay is not.

How to verify the fix

Shipping the change is not the same as passing 1.4.2. Re-run these checks against the page you edited before you close the ticket.

  • Land on the page; if audio plays without a one-click control, you fail.

An automated scan confirms the machine-testable half. Keyboard and screen-reader passes cover the half no scanner can judge — do both before claiming conformance.

What 1.4.2 requires

1.4.2 Audio Control (Level A, Perceivable): If audio plays automatically for more than 3 seconds, a way to pause, stop, or control its volume independently of system volume must be provided. Auto-playing audio interferes with screen readers, distracts users with cognitive disabilities, and is generally hostile UX.

  • Hero videos with audio autoplay

    1.4.2
  • Background music on landing pages

    1.4.2

Priority: Serious

This is one of the findings that shows up in demand letters, because the barrier it creates is total rather than inconvenient: the affected user cannot complete the task at all. Treat it as a release blocker, not a backlog item.

Because the cause is almost always a shared component rather than a single page, fix it where the component is defined and re-scan the whole site. Record 1.4.2 on the ticket verbatim: that string is what an auditor, a procurement questionnaire or a regulator will search for.

Related fixes

Find every accessibility issue on your site in 60 seconds.

Free public scan. No card. AI-generated fixes for every issue we find.