Techniques for WCAG 2.0

On this page:

-

# G171: Playing sounds only on user request

## Applicability

All technologies that can play sound.

This technique relates to:

- Success Criterion 1.4.2 (Audio Control)
  - How to Meet 1.4.2 (Audio Control)
  - Understanding Success Criterion 1.4.2 (Audio Control)

## Description

The intent of this technique is to allow a user to control the use of sounds in Web content. Someone that uses a screen reader may find it very distracting and difficult to listen to their screen reader if there are also sounds coming from Web content. Providing a way to play sounds only upon request will give a user the control needed to listen to any sounds or other audio without interfering with the output from a screen reader.

## Examples

### Example 1

A Web page from an grey whale conservation society has a looping background sound of grey whales singing. There are also sounds of water splashing. The sounds do not start automatically. Instead, the Web content provides a link at the top of the page to allow the user to start the sounds manually. The button says "Turn sounds on." After pressing the "turn sounds on" button, the sounds are heard. The user is then presented with an option to "turn sounds off."

### Example 2

A link is provided to a sound file that includes the sounds of the grey whales. The link text says, "Hear the song of the grey whale (mp3)."

## Related Techniques

- G60: Playing a sound that turns off automatically within three seconds
- G170: Providing a control near the beginning of the Web page that turns off sounds that play automatically

## Tests

### Procedure

1. Load a Web page that is known to contain sounds that play for 3 seconds or longer.

2. Check that no sounds play automatically.

3. Check that there is a way for a user to start sounds manually.

### Expected Results

- Check #3 is true.

- Top
- Contents
- Intro
- Previous: Technique G170
- Next: Technique G172