WCAG 1.4.2 Audio Control

Success criterion 1.4.2 protects screen reader users, whose speech output is drowned out when a page starts playing sound, and people who are easily distracted by audio. It is level A and part of EN 301 549 (clause 9.1.4.2).

What the criterion requires

If any audio on a web page plays automatically for more than 3 seconds, then at least one of these must be available:

• a mechanism to pause or stop the audio; or
• a mechanism to control the audio volume independently from the overall system volume.

The control should be easy to reach, ideally at the start of the page, because a screen reader user has to find it while the sound is playing.

This criterion is one of the non-interference criteria: every piece of content on the page must meet it, even content you do not count towards conformance, because it can block the use of the whole page.

The best way to meet it is not to autoplay sound at all. Audio that plays for 3 seconds or less, or only after the user presses play, is not affected.

Typical failures on an online shop

• a hero video or brand film that starts with sound when the home page loads;
• background music on a fashion or lifestyle site with no visible pause button;
• a product video in an autoplaying carousel that plays sound;
• a chatbot or promo widget that plays a sound for several seconds;
• a pause button that exists but cannot be reached by keyboard.

How to check it

Automated: our checker flags <audio> and <video> elements that autoplay without being muted and without visible controls (rule no autoplay audio). It cannot measure how long sound plays inside third-party players or scripts, so listen to the page as well.

By hand: load each page with sound on. If anything plays for more than 3 seconds without you pressing play, find the pause, stop or volume control — using only the keyboard — and check it works. Repeat with a screen reader running.

How to fix it

• Do not autoplay audio; let the user press play.
• If a video must autoplay, start it muted (autoplay muted) and offer an unmute button.
• Show player controls (controls) or a clear pause button near the top of the page.
• Make sure custom controls are keyboard operable and have accessible names.

Related criteria

• 1.2.2 Captions (Prerecorded) — captions for videos with sound.
• WCAG 2.2 checklist — including 2.2.2 Pause, Stop, Hide for moving content.
• Free check of one page — test your home page.

Frequently asked questions

Is autoplay video allowed under WCAG?

Autoplay video without sound is not covered by 1.4.2 (moving content falls under 2.2.2). Autoplay with sound for more than 3 seconds needs a way to pause or stop it, or a separate volume control.

Is the system volume button enough?

No. The volume control must work independently from the overall system volume, so the user can turn the page audio down while a screen reader stays audible.

Why does 1.4.2 apply to the whole page?

Because sound that cannot be stopped can drown out a screen reader and make the whole page unusable. WCAG lists 1.4.2 under non-interference: all content on the page must meet it.