WCAG (Level A) SC 1.4.2 Audio Control (w3.org)
Issue description
WCAG 1.4.2, “Audio Control” aims to prevent web pages from disrupting users with unexpected or uncontrollable audio. This is important because:
- Startling users: Sudden, unexpected sounds can be jarring and disorienting, especially for people with anxiety or sensory sensitivities.
- Interfering with assistive technologies: Audio playing automatically can interfere with screen readers, making it difficult for users to hear the screen reader’s output.
- Creating distractions: Uncontrollable audio can be distracting and make it difficult for users to focus on the content.
Many websites have audio that plays automatically, often for more than 3 seconds, without providing users with a way to control it. This can include:
- Background music: Music that plays automatically in the background.
- Video or audio content: Videos or audio files that start playing as soon as the page loads.
- Sound effects: Sounds that play in response to user interactions or events.
When users cannot control the audio, it can create a negative and inaccessible experience.
Essentially, this guideline ensures that users have control over any audio that plays automatically on a web page. It requires that if audio plays for more than 3 seconds, the user must be able to pause, stop, or control the volume of that audio independently from the overall system volume. This gives users the ability to manage their auditory experience and avoid disruptions.
Related requirements
The following WCAG source criteria are often related to this as well. They can provide additional insights into specific challenges you may be encountering.
Who this issue impacts
Follow the links for additional information on user impairments:
Suggestions for remediation
Remediating WCAG 1.4.2, “Audio Control” involves ensuring that users have control over any audio that plays automatically on your web page. Here’s how:
Provide controls
- Visible and accessible: Provide clear and accessible controls for pausing, stopping, and adjusting the volume of the audio. These controls should be easy to find and use, regardless of the user’s input method (mouse, keyboard, touch).
- Separate volume control: Ensure the user can control the audio’s volume independently from the overall system volume.
Limit audio duration
- Keep it short: If possible, keep any automatically playing audio clips to 3 seconds or less. This eliminates the need for explicit controls.
User-initiated audio
- Play on demand: Configure audio to play only when initiated by the user, such as when they click a button or interact with a specific element.
Consider context
- Background music: If using background music, provide a clear and easy-to-find control to turn it off completely.
- Essential audio: If the audio is essential to understanding the content, provide captions or a transcript as an alternative.
Testing
- Keyboard accessibility: Ensure the audio controls can be operated using the keyboard alone.
- Assistive technology testing: Test with screen readers to ensure the controls are identified and usable.
Example
If you have a video that auto-plays on your page, you can:
- Add controls to the video player: Most video players have built-in controls for play/pause, stop, and volume.
- Provide a separate mute button: Include a dedicated button to mute the audio completely.
- Set the video to not autoplay: Configure the video to play only when the user clicks a play button.
By implementing these techniques, you give users control over their auditory experience and prevent unexpected disruptions.
