Why this criterion exists
Auto-playing audio interferes with screen readers, distracts users with cognitive disabilities, and is generally hostile UX.
If you only remember one thing: 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. Everything else on this page is detail.
Who feels it when this fails
Accessibility criteria sometimes feel abstract until you see who pays the cost when a site ignores them. Audio Control affects:
- Screen reader users
- Users with cognitive disabilities
How sites typically fail it
These are the patterns we see week after week. None are intentional — they are accidents of how teams build interfaces under deadline. Knowing the failure modes is the fastest path to writing them out of your component library.
- Hero videos with audio autoplay
- Background music on landing pages
How to test for it
- Land on the page; if audio plays without a one-click control, you fail.
Automated scanners catch this criterion most of the time, but never all of the time. Manual testing with the keyboard and a screen reader closes the gap.
A code fix you can copy
Muted autoplay is permitted. Sound autoplay needs an explicit, immediate control.
The problem
<video autoplay src="/hero.mp4"></video>The fix
<video autoplay muted loop playsinline src="/hero.mp4"></video>Muted autoplay is permitted. Sound autoplay needs an explicit, immediate control.
Frequently asked questions
Why does auto-playing audio specifically affect screen reader users?
Screen readers and audio descriptions are delivered through the same output — speakers or headphones. Auto-playing audio competes directly with screen reader speech, making it impossible to hear page content or navigate. A screen reader user cannot read a page that is also blaring music or video narration. This is why 1.4.2 has a zero-tolerance threshold: three seconds, then there must be a control.
Does a hero video with muted autoplay need a pause control?
Under WCAG 1.4.2, no — muted autoplay is not covered. However, WCAG 2.2.2 (Pause, Stop, Hide) may apply if the video auto-advances more than 5 seconds. The two criteria cover different problems: 1.4.2 targets audio interference with screen readers; 2.2.2 targets moving content that distracts cognitive and vestibular users.