DEV 3.1 – Provide alternatives for images, video and audio content
Why is this important?
Users with visual impairments may not be able to see or interpret visual content, such as images and video. As designers you must provide text that accurately describes the nature of all visual content.
Users with hearing or cognitive impairments, and those for whom the language spoken in any video content is not their primary language, may not be able to hear or understand spoken audio in video content.
Image and video content usually requires far higher internet speeds than text, so providing text alternatives also helps users who are looking at your content with a poor internet connection.
You must provide a mechanism for designers and content authors to allow them to associate text alternatives with images and videos.
In this section
- All images must have a text equivalent (“Alt text”)
- Provide text equivalents for audio content
- Provide audio descriptions and text equivalents for video content
References for this section
EN 301 549 v 2.1.2
- 18.104.22.168 Non-text Content
- 22.214.171.124 Audio-only and Video-only (Pre-recorded)
- 126.96.36.199 Captions (Pre-recorded)
- 188.8.131.52 Audio Descriptions or Media Alternative (Pre-recorded)
- 184.108.40.206 Captions (Live)
- 220.127.116.11 Audio Description (Pre-recorded)
- WebAIM’s alternative text page
- WebAIM’s complex image tutorial
- 3 questions to Help Decide If an Image Doesn't Need Alt Text
- WAI Decorative Images
- 5 most annoying website features I face as a blind person every single day
- Deafness and the User Experience
- Accessibility according to actual people with disabilities
- Alternate text for background images
- WAI guidance on images
- WAI Alt text Decision Tree
- Text descriptions and emotion rich images
- Writing great alt text: Emotion matters
- Google – Add subtitles and captions