1.4.2 Audio Control

1. What is the goal of this criterion?

Imagine visiting a website – and suddenly music or a video starts blaring while you’re still trying to find your way around the page. Annoying for anyone, but for people who use screen readers it can become a real barrier.

People who rely on speech output have to process two audio sources at once: their screen reader and the website’s autoplaying sound. It’s like trying to follow a phone call while a radio is playing loudly in the background – and you still have to find the radio’s off switch.

So the goal of Success Criterion 1.4.2 is clear: users must be in control of audio that starts automatically – either through a pause or stop function or through a separate volume control.

2. What exactly does it require?

The criterion is precise: as soon as audio on a page plays automatically for more than 3 seconds, a control must be available.

Specifically:

• Pause or stop: users can pause or stop the audio.
• Or: independent volume control: the audio’s volume can be adjusted separately from the system volume (including down to zero).
• Short audio is exempt: audio that ends on its own within 3 seconds isn’t covered.

Important: it’s not enough for users to turn down their entire system volume – because that silences their screen reader too.

The criterion applies to any audio that starts automatically – background music, welcome announcements, ads or a video’s soundtrack.

Special feature: 1.4.2 is one of the few criteria subject to “non-interference”. It applies to all content on a page, even content that isn’t meant to be part of the accessible version – because a single blaring player can make the whole page unusable.

3. Why does it matter for accessibility?

Imagine navigating a website without sight, relying on your screen reader’s announcements. Suddenly a video starts with loud music – you can’t hear your speech output, and you can’t find the stop button fast enough.

Autoplaying audio creates barriers because it:

• Gets in the way of screen reader users: speech output is drowned out, and navigating becomes difficult or impossible – including finding the stop button.
• Disrupts people with hearing loss: people who use their residual hearing find it harder to separate different sounds.
• Makes concentration harder: people with attention deficits or cognitive disabilities get distracted.
• Creates situational barriers: in quiet places (libraries, offices, public transport) sudden audio is a problem.

Audio control makes content accessible because it gives users the choice: they decide when and how to listen.

4. How to meet the criterion

The good news: audio control is usually very easy to implement – and it improves usability for everyone.

Ground rules:

• Ideally, no autoplay with sound: it’s best when audio only starts after a user action (a play button). Then the criterion doesn’t apply at all.
• Place the stop button prominently: if audio does start automatically, make the control visible and reachable right away – ideally at the very beginning of the page, so screen reader users find it first.
• Add an independent volume control: users should be able to turn the audio down without changing their system volume.
• Keep short sounds under 3 seconds: confirmation sounds or short jingles are fine if they end quickly on their own.

Technical implementation:

• HTML video and audio: use the controls attribute or build custom controls with JavaScript.
• Tame autoplay: only use autoplay together with muted, or leave it out entirely.
• Clear labels: give stop buttons a clear visible name (“Turn sound off”). For icon-only buttons, provide an accessible name, for example with aria-label.
• Keyboard operation: make sure all audio controls can be reached and operated with a keyboard (see Keyboard).

What to avoid:

• Hidden controls: stop buttons don’t belong in the footer or in hidden menus.
• “Just turn down your system volume”: that doesn’t count as a solution.
• Endless loops without controls: repeating audio is especially disruptive.

5. Why this criterion matters for businesses

Audio control isn’t just a nice service – it pays off for your business, too.

1. Improve usability

People caught off guard by sudden sound often just close the page. When users decide for themselves when to turn sound on, they’re more likely to stay on your website.

2. Strengthen a professional brand image

Websites that ambush visitors with unwanted sound come across as pushy. Clear audio controls show respect for your users’ choices and build trust in your brand.

3. Improve the mobile experience

On the go, autoplaying audio is especially awkward: it can be embarrassing at the wrong moment, and automatically loaded media uses up data. Control over sound makes your website more pleasant on mobile.

Last but not least: legal requirements. The European Accessibility Act (Directive (EU) 2019/882) has applied since 28 June 2025 to many consumer products and services, such as online shops; in Germany it is implemented by the Barrierefreiheitsstärkungsgesetz (BFSG). The technical benchmark is the harmonised standard EN 301 549, which references WCAG 2.1 Level AA for web content – and 1.4.2 is part of that. Public sector bodies are covered by the Web Accessibility Directive (EU) 2016/2102. This section is general information, not legal advice.

6. The success criterion in the W3C’s words

Success Criterion 1.4.2 Audio Control (Level A)

If any audio on a web page 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 audio volume independently from the overall system volume level.

Note: Since any content that does not meet this success criterion can interfere with a user's ability to use the whole page, all content on the web page (whether or not it is used to meet other success criteria) must meet this success criterion. See Conformance Requirement 5: Non-Interference.

In short: if a page plays audio automatically for more than 3 seconds, users must be able to pause it, stop it or turn it down independently of the system volume – and this applies to all content on the page.