Goal
Prevent unexpected audio from interfering with assistive technology and user control.
Success Criterion · WCAG 1.4.2
Audio Control
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.
Level AWCAG 2.0Perceivable1.4 · Distinguishable
Copy button ready
What to do
If audio plays automatically for more than 3 seconds, provide a way to pause/stop it or control its volume independently.
Why it matters
Autoplay audio can mask screen reader speech and disrupt users, especially those with cognitive disabilities or in shared environments.
Success criterion
What WCAG 1.4.2 requires
Summarized directly from the official Understanding document so teams can quote the requirement accurately.
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.
Intent
Why WCAG created this requirement
- Autoplay audio can overlap with screen reader output, making the page unusable.
- Users should be able to stop or control audio without hunting for hidden controls.
- Independent volume control is an alternative when pause/stop isn’t feasible.
Benefits
Who gains when you pass
- Screen reader users can hear assistive technology speech without interference.
- Users with attention-related disabilities avoid distraction and stress from unexpected sound.
- Users in quiet or shared spaces can prevent embarrassing or disruptive audio playback.
- Users with hearing aids or sound sensitivity can control audio safely.
Why it matters
User impact when this criterion fails
Summaries drawn from the Understanding document help you socialize impact statements with product stakeholders.
Screen reader output may be drowned out by music or video audio.
Users may abandon the page because they cannot quickly stop audio.
Users may be unable to focus on reading or completing forms due to background sound.
Overview
Autoplay audio is disruptive. If a page starts playing audio automatically and it lasts longer than 3 seconds, users must be able to stop or pause it (or adjust volume separately from system volume). This ensures screen reader users can hear speech output and everyone retains control.
- The control must be easy to find and operate (keyboard accessible, labeled).
- Muted-by-default autoplay generally avoids this issue, but verify behavior across browsers.
- If offering volume control, it must be independent from system volume.
- If the audio stops automatically within 3 seconds, it meets the requirement.
Reference: All summaries and highlights originate from Understanding WCAG 1.4.2 and the W3C quick reference.
Fast facts
- Conformance level
- Level A
- WCAG version introduced
- WCAG 2.0
- Principle
- Perceivable
- Guideline
- 1.4 · Distinguishable
Examples
Make success tangible for teams
Share pass/fail snapshots to coach designers, engineers, QA, and content authors.
Background music
Pass
Page shows a visible “Pause audio” button that immediately stops the music.
Fail
Music plays on load with no control other than adjusting system volume.
Autoplay video
Pass
Video autoplays muted; user must opt-in to enable sound.
Fail
Video autoplays with sound and no pause/stop control for audio.
Audio teaser
Pass
Audio plays for 2 seconds then stops automatically.
Fail
Audio plays for 10 seconds automatically and cannot be stopped.
Evidence to keep
Document conformance decisions
Capture artifacts for VPATs, procurement reviews, and regression testing.
- Document autoplay policy (generally avoid) and any allowed exceptions.
- Capture evidence of pause/stop controls for any pages with unavoidable autoplay audio.
Official resources
Deep dives and supporting material
Keep these links handy when writing acceptance criteria or responding to audits.
Understanding 1.4.2
Official W3C interpretation, techniques, and intent for Audio Control.
Quick Reference 1.4.2
Filterable list of sufficient techniques and failures.
Technique G60
Playing audio that turns off automatically within three seconds.
Technique G170
Providing a control near the beginning of the Web page that turns off sounds.
Failure F23
Failure due to playing sound automatically without a mechanism to turn it off.
Implementation checklist
Capture progress and blockers
- Audit pages for any autoplay audio (including ads, background music, embedded players).
- Disable autoplay where possible; prefer user-initiated playback.
- If autoplay remains, add prominent pause/stop control near the content that starts audio.
- Ensure controls are keyboard operable and have accessible names.
- If using independent volume, ensure it does not depend on system volume and is discoverable.
- Test behavior across browsers and with reduced-motion / autoplay settings.
Testing ideas
Prove conformance with evidence
- Load the page and check whether any audio starts without user action.
- If audio plays longer than 3 seconds, verify there is a pause/stop control.
- Verify the control is keyboard accessible and labeled for screen readers.
- Confirm volume controls (if provided) change only the media volume, not system volume.
- Test with a screen reader to ensure audio does not prevent hearing speech output.
Related success criteria
More from Distinguishable (1.4)
WCAG 1.4.1Use of ColorLevel AWCAG 1.4.3Contrast (Minimum)Level AAWCAG 1.4.4Resize TextLevel AAWCAG 1.4.5Images of TextLevel AAWCAG 1.4.6Contrast (Enhanced)Level AAAWCAG 1.4.7Low or No Background AudioLevel AAAWCAG 1.4.8Visual PresentationLevel AAAWCAG 1.4.9Images of Text (No Exception)Level AAAWCAG 1.4.10ReflowLevel AAWCAG 1.4.11Non-text ContrastLevel AAWCAG 1.4.12Text SpacingLevel AAWCAG 1.4.13Content on Hover or FocusLevel AA