FOUND ERROR CHECK IF RESOLVED TABLE SC
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.
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.
SC 1.4.2 Audio Control supports the principle of Perceivable because individuals who use screen reading software can find it hard to hear the speech output if there is other audio playing at the same time. This difficulty is exacerbated when the screen reader’s speech output is software based (as most are today) and is controlled via the same volume control as the sound. Therefore, it is important that the user be able to turn off the background sound.
Note: Having control of the volume includes being able to reduce its volume to zero.
The control to turn off the sounds should be located near the beginning of the page to allow the control to be easily and quickly discovered by users. This is useful for those who utilize assistive technologies (such as screen readers, screen magnifiers, switch mechanisms, etc.) and those who may not (such as those with cognitive, learning and language disabilities).
In this technique, an author includes a control that makes it possible for users to turn off any sounds that are played automatically. The control should be keyboard operable, located early in the tab and reading order, and clearly labeled to indicate that it will turn off the sounds that are playing.
Note: Playing audio automatically when landing on a page may affect a screen reader user’s ability to find the mechanism to stop it because they navigate by listening and automatically started sounds might interfere with that navigation. Therefore, we discourage the practice of automatically starting sounds (especially if they last more than 3 seconds) and encourage that the sound be started by an action initiated by the user after they reach the page, rather than requiring that the sound be stopped by an action of the user after they land on the page.
SC 1.4.2 Audio Control also benefits people who have difficulty focusing on visual content (including text) when audio is playing.
Note: Audio content must play automatically for SC 1.4.2 Audio Control to be applicable.
Impact of Nonconformance with SC 1.4.2 Audio Control
| Type of Disability | Description of Impact |
|---|---|
| 302.1 Without Vision | Users who are blind cannot use a mouse to interact with electronic content and typically use an assistive technology, such as a screen reader, to get audible or other alternative output for the information represented visually. To be able to navigate the content, understand its structure and relationships, and understand the meaning of content the content must provide textual and programmatic cues in addition to the content presented purely visually. Playing audio automatically may affect a screen reader user’s ability to navigate and electronic content as it interferes with what is read aloud by the assistive technology. |
| 302.5 With Limited Hearing | Some users cannot hear sounds below certain volumes or at certain frequencies and may not be able hear certain audio outputs from ICT. Background noise can also be problematic for users with limited hearing. Playing audio automatically may affect the user’s ability to navigate electronic content. Providing modes of operation that give users control over audio settings can help users with limited hearing understand, navigate, and operate the ICT. |
| 302.9 With Limited Language, Cognitive, and Learning Abilities | Some users require more time than average to process information while others may find complicated instructions difficult to follow. Playing audio automatically may distract or overwhelm users, preventing them from being able to interact with or understand the ICT content. Designers and developers of ICT must consider a broad range of cognitive abilities to provide ICT that is simple and easy to use. |
Applicability of Success Criteria 1.4.2 Audio Control
| Technology | Applicability of SC 1.4.2 |
|---|---|
| Web | Applies directly; software developers are discouraged from playing audio automatically when landing on a page as it may affect a screen reader user’s ability to find the mechanism to stop it because they navigate by listening and automatically started sounds might interfere with that navigation. Background noise can also be problematic for people with limited hearing. Furthermore, some ICT content can distract or overwhelm users, preventing them from being able to interact with or understand the ICT content. Therefore, we discourage the practice of automatically starting sounds (especially if they last more than 3 seconds) and encourage that the sound be started by an action initiated by the user after they reach the page, rather than requiring that the sound be stopped by an action of the user after they land on the page. |
| Software | Applies directly; software developers are discouraged from playing audio automatically when using software applications as it may affect a screen reader user’s ability to find the mechanism to stop it because they navigate by listening and automatically started sounds might interfere with that navigation. Background noise can also be problematic for people with limited hearing. Furthermore, some ICT content can distract or overwhelm users, preventing them from being able to interact with or understand the ICT content. Therefore, we discourage the practice of automatically starting sounds (especially if they last more than 3 seconds) and encourage that the sound be started by an action initiated by the user after they reach the page, rather than requiring that the sound be stopped by an action of the user after they land on the page. |
| Office documents | Applies directly; depending on the type of document, authors may embed particular types of media files directly in the document and/or stream media from online sources (e.g., YouTube™), assuming a live internet connection. Media embedded directly within a document may rely on a native player or the default Operating System player. In either case, authors may not be able to predict whether the player will provide the ability to turn off the audio or where the control may be located. Therefore, we discourage the practice of automatically starting sounds (especially if they last more than 3 seconds) and encourage that the sound be started by an action initiated by the user after they reach the page, rather than requiring that the sound be stopped by an action of the user after they land on the page. |
| PDF documents | Applies directly; depending on the PDF authoring tool and/or the end user’s PDF viewer, it may be possible to embed media files directly within a PDF document or stream media from an online source, such as YouTube™. For example, Adobe Reader 9 and later can play media files that are H.264-compliant in a native media player. However, the native player does not provide caption controls at the same menu level as the volume and program selection, which does not conform to the Revised Section 508 Standards. When a PDF author cannot predict whether the end user’s media player can turn off audio, or where the control may be located, authors are encouraged to have sound be started by an action initiated by the user rather than requiring that the sound be stopped by an action of the user. |
| Mobile native | Applies directly; software developers are discouraged from playing audio automatically when using an app as it may affect a screen reader user’s ability to find the mechanism to stop it because users navigate by listening and automatically started sounds might interfere with that navigation. Background noise can also be problematic for people with limited hearing. Furthermore, some ICT content can distract or overwhelm users, preventing them from being able to interact with or understand other ICT content. Therefore, we discourage the practice of automatically starting sounds (especially if they last more than 3 seconds) and encourage that the sound be started by an action initiated by the user after they reach the page, rather than requiring that the sound be stopped by an action of the user. |
| EXCEPTION | Applies to all technologies except those for voice interaction. |