Level
A
Since
WCAG 2.0
Entries
0 / 193
/ WCAG criterion

1.4.2 Audio Control

If audio starts by itself and plays for more than three seconds, the page must offer a way to pause or stop it, or to turn it down separately from the system volume.

/ What it requires

Sound that starts by itself is the hardest interruption for a person who uses a screen reader. The speech that describes the page comes out of the same speakers, often through the same volume control, so a background track or an autoplaying video can drown it out at exactly the moment the person is trying to find the stop button. The criterion also helps people who find it hard to concentrate on text while something is playing, and people who are hard of hearing and cannot simply turn the speech up over the music.

It applies when audio plays automatically for more than three seconds. Automatically means it was not started by a deliberate action of the user, and pressing a clearly labelled play button is such an action. The page then needs a mechanism to pause or stop that audio, or a volume control for it that works independently of the system volume and goes down to zero. Muting the whole computer does not count. Because sound affects the whole page, this is one of four criteria that apply to all content on it, including content not relied upon for conformance. W3C does not treat two-way voice, such as a conference call, as audio that plays automatically.

/ How pages fail it

  • A hero video with sound starts on page load, loops, and has no visible controls.
  • Background music begins on the homepage, and the speaker icon that stops it is a div with a click handler that the keyboard cannot reach or operate.
  • A chat or promotion widget plays a spoken greeting longer than three seconds when the page opens and offers no way to silence it.
  • An embedded player is set to autoplay with sound and its controls are hidden by the site's own CSS.
  • A product video with narration starts when it scrolls into view, and the only control it shows is a fullscreen button.

/ How to check it yourself

  1. Open the page with the sound on and wait. Note anything that starts playing without a click and how long it lasts.
  2. If it lasts longer than three seconds, look for a pause, stop or mute control, or a volume control, on the player itself or near the top of the page.
  3. Reach that control with Tab and operate it with Enter or Space. The audio must stop, or go down to silence, without touching the system volume.
  4. In the DevTools console run document.querySelectorAll('audio, video') and check each element's autoplay, muted and controls properties to find players that start with sound.
  5. Turn on a screen reader such as NVDA or VoiceOver, reload the page, and check that you can still hear it and find the control while the audio plays.

/ How to fix it

  • Remove the autoplay attribute and let the user start the audio with a real button element whose name says what will play.
  • If a video has to start by itself, start it muted (autoplay muted playsinline) and offer a clearly named unmute button.
  • Keep the controls attribute on audio and video elements, or build a custom player whose pause button is a button element with an accessible name.
  • Place a control that turns the sound off at the very beginning of the page, before the main content, so a screen reader user meets it first.
  • Keep incidental sounds short. A notification or effect that ends within three seconds needs no control under this criterion.

/ What our scanner checks

The autoplay-media check looks at every audio and video element once, after the page has settled. It reports one that is playing at that moment, is not muted, has no controls attribute, and either reports no duration or runs longer than three seconds. A custom pause button is not recognised, sound from an iframe embed or from script is not seen, and if the browser blocked autoplay nothing is playing and nothing is reported.

/ Who fails it, in our own measurements

No measured body currently fails this criterion in our automated checks. That is not a clean bill of health: automated checks cannot see everything this criterion asks for.

One page per body, measured by automated checks on a weekly schedule. Any body that has fixed something since the last sweep will show it at the next one, and every entity page carries a right of reply.

/ Questions about this criterion

Is autoplay with sound against WCAG?

Autoplay alone is not a failure. It fails 1.4.2 when the audio plays for more than three seconds and the page gives no way to pause or stop it, or to set its volume separately from the system. W3C still discourages starting sound automatically at all, because a screen reader user may struggle to find the control while the sound is playing over their speech.

Does a muted autoplaying video fail 1.4.2?

No. The criterion is about audio, and a muted video plays none. The movement is a separate matter: 2.2.2 Pause, Stop, Hide asks for a way to pause content that starts by itself, moves for more than five seconds and is shown alongside other content.

Why does 1.4.2 apply even to parts of a page that are not in scope?

WCAG names four criteria that apply to all content on a page, because failing them can stop someone using the page at all: 1.4.2 Audio Control, 2.1.2 No Keyboard Trap, 2.2.2 Pause, Stop, Hide and 2.3.1 Three Flashes or Below Threshold. Audio from an advert, an embed or a widget therefore counts, even when that content is not relied upon to meet the other criteria.