- Success Criterion 1.1.1
- Conformance level A
Audio Clip Published With No Label Identifying It
1.1.1 — Non-text Content
Scenario
Setting
A calendar app's event-creation form
What’s wrong
Audio <audio> used as non-text content (e.g., pronunciation clip) with no descriptive identification.
Example
This shows up on a calendar app's event-creation form: audio <audio> used as non-text content (e.g., pronunciation clip) with no descriptive identification.
Why it matters
Blind and low-vision people using screen readers, and anyone who browses with images disabled, when icons or photos carry meaning. In this case (a calendar app's event-creation form), they are left guessing what the media actually shows.
How to test
Look for a text caption or label identifying an embedded audio clip (e.g., pronunciation sample): if there's no text nearby saying what it is, it fails.
How to fix
Add a text label identifying what the audio clip is before or on the player.
Outcome
Once corrected, a calendar app's event-creation form lets them hear or read what the media conveys.
Who is affected
Blind and low-vision people using screen readers, and anyone who browses with images disabled, when icons or photos carry meaning.
Learn more
- Understanding Understanding document (opens in a new tab)
Related scenarios
- Product Photo Added as a CSS Background With No Alt Text
- Chart Alt Text That Never Explains What Each Color Means
- Outdated Alt Text That No Longer Matches the Image
- Alt Text Left as a Filename Instead of a Real Description
- Decorative Image Not Hidden From Screen Reader Users
- Decorative Image Given Alt Text Instead of Being Marked Silent