Success Criterion 1.2.5 - Audio Description (Prerecorded) - Level AA

[JJdeGroot]

Discussion:

MATF meeting on June 26, 2024

Source

1.2.5 Audio Description (Prerecorded) - Level AA

JJ: WCAG2ICT does not include a note about closed functionality, but otherwise same interpretation.

ToriClarkA11y: In US, WCAG and ADA are not 1:1. Example, ADA may require extended AD while that would be AAA conformance.

JJ: Highlighting difference between AD and extended AD.

ToriClarkA11y: I've seen some players attempt the pause functionality to support extended AD but haven't seen them work reliably. Player support isn't there yet.

just different tech approach, so I wanted to acknowledge it.

Summary:

1. WCAG 1.2.5 Application:

   • JJ: Mentioned that WCAG2ICT does not include a note about closed functionality for 1.2.5, but the interpretation remains the same as 1.2.3.

2. Audio Description Requirements:

   • Tori: Highlighted that in the US, WCAG and ADA requirements are not always equivalent. For example, ADA may require extended audio descriptions, which would correspond to AAA conformance under WCAG.
   • JJ: Emphasized the difference between standard audio descriptions and extended audio descriptions.

3. Challenges with Player Support:

   • Tori: Shared experiences with players attempting to implement pause functionality to support extended AD but noted that this hasn't been reliable. Current player support is lacking for this feature.
   • Tori: Acknowledged the different technical approaches to supporting extended AD, indicating that player technology is still evolving.

[illai]

I think we should treat this success criterion with caution. Since we know there are technical limitations in fully implementing this requirement (as Tori pointed out at the meeting), adopting the success criterion as worded from WCAG may result in it being ignored (as is the case today in many cases with WCAG 1.2.5). For the success criterion to be practical, it should be formulated and defined in a way that provides users with the closest and equivalent experience but also reduces the technological barriers and friction to a minimum.

[julianmka]

Based on previous task force conversation, this SC can be applied to native mobile apps and mobile web with minimal or no deviation from WCAG2ICT.

Proposal
In MATF's first draft of guidance, this SC's section will read as:

This applies directly as written, and as described in Intent from Understanding Success Criterion 1.2.5.

NOTE 1
The WCAG 2 definition of “audio description” says that audio description is “also called ‘video description’ and ‘descriptive narration’”.

NOTE 2
Secondary or alternate audio tracks are commonly used for this purpose.

Please indicate your agreement with a thumbs up emoji 👍, or if you disagree, use the thumbs down emoji 👎 and elaborate in comments.

[julianmka]

After discussion and voting at the meeting today, the task force members present accepted the proposed language for the first draft of our guidance.