WCAG 1.2.5: Audio Description (Prerecorded)
WCAG 1.2.5, part of the Web Content Accessibility Guidelines, addresses the need for audio description for prerecorded video content within synchronized media. This criterion is crucial for making video content accessible to individuals who are blind or have low vision, ensuring they receive all critical visual information necessary to understand the full context of the media.
Understanding WCAG 1.2.5: Audio Description (Prerecorded)
At its core, WCAG 1.2.5 requires that a separate narration track is provided to describe important visual details in prerecorded synchronized media. This narration, known as audio description, is typically inserted into pauses in the media’s original soundtrack. It describes actions, body language, scene changes, on-screen text, and other visual information that is not conveyed through the main audio alone.
Why is Audio Description Important?
Audio description plays a vital role in digital accessibility for several reasons:
WCAG 1.2.5 Success Criterion Details
The formal wording for Success Criterion 1.2.5 at Level AA is:
Audio Description (Prerecorded): Audio description is provided for all prerecorded video content in synchronized media.
Key terms to understand:
Practical Guidelines for Compliance
Achieving compliance with WCAG 1.2.5 involves careful planning and implementation:
How to Provide Audio Description
Key Considerations for Creating Audio Descriptions
Examples
Correct Implementation: Video with a Dedicated Audio Description Track
The most common and recommended approach for web content is to provide multiple audio tracks, one of which includes the audio description. Users can then select their preferred track via the video player’s controls.
Scenario: An educational video about a scientific experiment, where visual steps are crucial. The video player offers an option to switch audio tracks.
HTML Structure for Video with Multiple Audio Tracks:
Note: In this setup, video_audio_description.mp4 is a version of the video file where the audio track has been pre-mixed to include the original audio along with the descriptive narration. A JavaScript-enhanced video player would typically manage the switching of these <source> elements or, more robustly, offer an audio track selection UI using a single video source with multiple audio tracks embedded within (e.g., using an HLS or DASH stream with multiple audio renditions).
Alternatively, if a WebVTT 'description’ track is used, it often requires a custom player to read the cues and play synthesized speech, which is generally not what WCAG implies for 'audio description’. However, for screen reader users, such a track could provide text alternatives that the screen reader might read out.
Example of a WebVTT Description Track (less common for full AD, but conceptually relevant for text-based descriptions):
For a true audio description, these text descriptions would be voiced by a narrator and embedded directly into an audio stream, not just provided as text.
Incorrect Implementation: Video without Audio Description
Scenario: A cooking show video where visual steps (e.g., how to chop vegetables, specific cooking techniques) are shown but not verbally described.
HTML Structure for Video Lacking Audio Description:
Reason for Incorrectness: This video provides only the main audio track and visual content. Any user who cannot perceive the visual information will miss crucial cooking steps and techniques demonstrated on screen, making the content inaccessible and incomplete for them.
Best Practices and Common Pitfalls
Best Practices
Common Pitfalls
Conclusion
WCAG 1.2.5 is a fundamental criterion for ensuring that all users, regardless of visual ability, can fully engage with and understand video content. By providing high-quality, well-timed, and easily accessible audio descriptions, you not only comply with accessibility standards but also create a more inclusive and equitable digital experience for everyone.
Related posts
- WCAG 5.2.3: Complete processes
- WCAG 5.2.4: Only Accessibility-Supported Ways of Using Technologies
- WCAG 5.2.5: Non-Interference
- WCAG 5.3.1: Required elements of the conformity declaration
- WCAG 5.3.2: Optional Components of a Conformance Claim
Still looking for answers?
Ask our experts using online chat