WCAG 1.4.2 — Audio Control

Auto-playing Media

What is this issue?

Auto-playing media refers to audio or video content that begins playing automatically when a page loads, without the user initiating playback. WCAG Success Criterion 1.4.2 (Level A) requires that if any audio plays automatically for more than 3 seconds, either a mechanism is available to pause or stop the audio, or a mechanism is available to control the audio volume independently from the overall system volume.

This issue goes beyond annoyance. For screen reader users, auto-playing audio interferes with the screen reader's speech output, making it impossible to hear announcements and navigate the page. The user is caught in a bind: they need to find the audio controls to stop the playback, but they cannot hear their screen reader to navigate to those controls.

Auto-playing video (even without audio) can also cause problems. Motion on screen can distract users with attention disorders, and animated content can trigger seizures in users with photosensitive epilepsy (though this is covered by a separate criterion, 2.3.1). Many browsers now block auto-playing media with sound by default, but unmuted autoplay is still possible under certain conditions, and muted video autoplay remains common.

Impact on users

For screen reader users, auto-playing audio is one of the most disruptive accessibility barriers. The screen reader's speech output competes with the media audio, creating a cacophony that renders both unintelligible. The user must blindly try to find and activate the pause button -- a task that is nearly impossible when they cannot hear their screen reader. Many users simply leave the site.

Users with cognitive disabilities, ADHD, or anxiety disorders can be severely affected by unexpected audio. Auto-playing content disrupts focus, increases cognitive load, and can cause distress. Users with PTSD may be triggered by unexpected loud sounds.

In shared environments like offices, libraries, and classrooms, auto-playing audio causes social embarrassment and disruption. Users may scramble to mute their device, close the tab, or lower the volume, losing their place on the page in the process.

Code example

Before (non-compliant)
<!-- Auto-playing video with sound -->
<video autoplay>
  <source src="/promo.mp4" type="video/mp4">
</video>

<!-- Background music that plays on load -->
<audio autoplay loop>
  <source src="/background-music.mp3" type="audio/mpeg">
</audio>

<!-- Auto-playing embed -->
<iframe src="https://player.example.com/video?autoplay=1"
  allow="autoplay">
</iframe>
After (compliant)
<!-- Video requires user interaction to play -->
<video controls preload="metadata" poster="/promo-poster.jpg">
  <source src="/promo.mp4" type="video/mp4">
</video>

<!-- If autoplay is essential, mute and provide controls -->
<video autoplay muted controls loop>
  <source src="/ambient-bg.mp4" type="video/mp4">
</video>

<!-- Embed without autoplay -->
<iframe src="https://player.example.com/video"
  title="Product introduction video">
</iframe>

How Scrutia detects this issue

Scrutia detects auto-playing media by inspecting <video> and <audio> elements for the autoplay attribute, checking embedded players for autoplay parameters, and monitoring actual audio playback during page load using the Web Audio API. It flags any media that produces audio within 3 seconds of page load without user interaction, and verifies that pause/mute controls are accessible.

Check your site for this issue

Scrutia audits your site against WCAG criteria in minutes.

Free audit

Frequently Asked Questions

Can I autoplay muted video?
Muted video autoplay is generally acceptable under WCAG 1.4.2 since the criterion specifically addresses audio. However, provide pause controls for users who find motion distracting, and respect the prefers-reduced-motion media query.
What if the audio is less than 3 seconds?
WCAG 1.4.2 allows auto-playing audio that lasts fewer than 3 seconds. However, even short sounds can be disruptive for screen reader users. Best practice is to avoid all auto-playing audio.
Do notification sounds count as auto-playing audio?
If a notification sound plays without user action (e.g., a chat notification), it falls under WCAG 1.4.2. Provide a way to disable notification sounds in your application settings.

Does your site have this issue?

Scrutia scans your pages against WCAG success criteria and delivers actionable fixes. Results in 5 minutes.

Run a free audit