# Audio Control: Stop Autoplay Sound

Source: https://allyway.ai/glossary/audio-control

Audio control is WCAG success criterion 1.4.2. If audio on a web page plays automatically for more than 3 seconds, there must be a way to pause or stop it, or to control its volume independently of the system volume.

Audio control is the WCAG rule for sound that starts by itself – a background track, an autoplaying video with sound, a spoken welcome message. When it plays for more than three seconds, visitors need a way to stop it or turn it down. Otherwise, people who listen to a screen reader cannot hear their own speech output.

## What it means

[WCAG 1.4.2 Audio Control](https://www.w3.org/WAI/WCAG22/Understanding/audio-control.html) is a Level A criterion in [WCAG 2.2](https://allyway.ai/regulations/wcag-2-2). If any audio on a web page plays automatically for more than 3 seconds, at least one of these must be available:

| Option | What it means in practice |
|---|---|
| Pause or stop | A button that pauses or stops the sound |
| Independent volume | A volume control for this audio alone, separate from the system volume, that can go down to zero |

Muting the computer does not count: W3C says both options must work independently of the system volume. The reason is [screen reader](https://allyway.ai/glossary/screen-reader) users – their speech output often shares the system volume, so turning everything down silences the screen reader too, and they can no longer find the control.

"Plays automatically" means the sound was not started by a direct user action. A clearly labeled "Play" button that starts audio is a user action and is not covered. Conference calls are not intended to fall under 1.4.2.

> **Warning:** > **One autoplay breaks the whole page**
> 1.4.2 is a non-interference criterion: every piece of content on the page must meet it, even content that is not used to meet other criteria. A single background track without a stop button can make a page fail as a whole.

W3C's preferred solution is simple: do not autoplay sound at all, and let people start it themselves. Moving video without sound is a separate topic – see [pause, stop, hide](https://allyway.ai/glossary/pause-stop-hide).

## Examples

```html title="Example"
<!-- Best: nothing plays until the visitor asks for it -->
<video src="/media/tour.mp4" controls muted playsinline>
  <track kind="captions" src="/media/tour.en.vtt" srclang="en" label="English">
</video>

<!-- If sound must autoplay: a stop control first on the page -->
<button type="button" id="stop-music" aria-pressed="false">Stop background music</button>
<audio id="music" src="/media/ambient.mp3" autoplay loop></audio>
```

The stop button is a real `<button>`, so it is reachable with [keyboard navigation](https://allyway.ai/glossary/keyboard-navigation), and it sits at the start of the page, where screen reader users find it quickly. Videos with speech also need [captions](https://allyway.ai/glossary/captions).

**Do:** Do

Start audio only on a user action, mute autoplaying videos by default, put a visible stop or mute button at the beginning of the page, and keep autoplay sounds under three seconds.

**Don't:** Don't

Play background music on page load, hide the only volume slider inside a menu, rely on the visitor's system volume, or restart the sound on every new page.

## How to check audio control



## Questions

Q: Is autoplay audio allowed under WCAG?
A: Yes, if it stops within three seconds, or if people can pause, stop or turn down the audio independently of the system volume. W3C still recommends not to autoplay sound at all.

Q: Why does WCAG use 3 seconds?
A: The criterion sets three seconds as the limit; the Understanding page does not explain the number. Short sounds such as a notification tone stay below it.

Q: Does a muted autoplay video pass 1.4.2?
A: Yes, a video that starts without sound plays no audio, so 1.4.2 does not apply. If it moves for more than five seconds next to other content, 2.2.2 Pause, Stop, Hide applies instead.

Q: Is the browser's tab mute button enough?
A: Do not rely on it. W3C's own example puts the control on the page – a link at the top that silences the sound – and browser features vary from one browser to the next. Many visitors, especially screen reader users who cannot hear their speech output, will not find them in time.

Q: How do I find accessibility issues across my website?
A: Autoplay sound needs a quick manual check with speakers on. For code-level problems such as unnamed buttons, the [free WCAG scanner](https://allyway.ai/free-wcag-accessibility-scanner-for-websites) checks your pages in a few minutes.
