WCAG 1.2.5 Deep Dive: Audio Description – Level AA

Discuss specific WCAG guidelines, accessibility standards, and best practices for compliance.
Post Reply
wcgadmfrm
Site Admin
Posts: 41
Joined: Tue Jun 24, 2025 10:28 am

WCAG 1.2.5 Deep Dive: Audio Description – Level AA

Post by wcgadmfrm »

Dear WCAG Plus Forum community members,

We've already discussed Criterion 1.2.3, which requires audio description or a media alternative for prerecorded synchronized content (Level A). Now, let's move up a level with Success Criterion 1.2.5: Audio Description (Prerecorded), a Level AA requirement. This criterion becomes relevant when visual information is so dense and continuous that natural pauses in the original audio content are insufficient to provide a complete audio description.

What does Criterion 1.2.5 require?

Criterion 1.2.5 states that for all prerecorded synchronized video content (i.e., videos with significant audio), an audio description must be provided. The key difference from 1.2.3 is that, if natural pauses in the audio are not long enough for an adequate description, an extended audio description must be provided.
  • Extended Audio Description: This is an additional audio track that describes the significant visual information of the video, but unlike standard audio description, it can pause the video to allow the description to be complete. This is crucial when visual actions occur rapidly or when there is a lot of on-screen text or complex graphics that require more time to describe.
Why is this so important (Level AA)?

This criterion is fundamental to ensure that blind or low vision individuals can access complex or rapidly changing visual information that cannot be adequately described within the short pauses of the original audio. Without an extended description, these users might miss crucial details necessary to fully understand the video's content.

The move to Level AA reflects the increased complexity and production effort required to create an extended audio description, which often involves altering the timing of the original video.

When is Extended Audio Description Needed?

Extended audio description is necessary when:
  • There are few or no natural pauses in the video's audio.
  • Visual information is dense and complex (e.g., detailed graphs, intricate diagrams, rapid action sequences, technical tutorials with many visual steps).
  • On-screen text is abundant and not read aloud.
  • Standard audio description (which fits into existing pauses) would not be sufficient to convey all essential visual information.
Practical Implementation:

Creating an extended audio description requires a more elaborate process:

1. Content Analysis: Identify sections of the video where visual information is too dense for natural pauses.
2. Script Writing: Create a detailed script for the extended audio description.
3. Recording: Record the narration for the audio description.
4. Editing: Integrate the extended audio track into the video, extending video sections where necessary to accommodate the narration. This often means that a version of the video with extended description is longer than the original version.
5. User Option: Users must have the option to choose between the standard video version and the version with extended audio description.

Key Differences from 1.2.3 (Level A):
  • 1.2.3 (Level A): Requires audio description that fits into existing pauses in the video.
  • 1.2.5 (Level AA): Requires audio description that can extend the video's duration to create artificial pauses, if natural pauses are insufficient.
Criterion 1.2.5 is a significant step forward in ensuring comprehensive accessibility for complex video content, ensuring no one is excluded from crucial visual information.

We invite the community to share their experiences:
  • Have you ever needed to create extended audio descriptions? What tools or services did you use?
  • What were the biggest challenges in determining when an extended description is necessary?
  • Can you share examples of well-implemented extended audio descriptions?
We look forward to your contributions!

Warm regards,

Michele (wcgadmfrm)
WCAG Plus Forum Team
Post Reply