Success Criterion 1.2.2 - Captions (Prerecorded) - Level A

[JJdeGroot]

Discussion:

MATF meeting on June 19, 2024

[Source](https://www.w3.org/2024/06/19-matf-minutes.html#t04) JJ: Already partially discussed Quintin: We should mention to respect the OS user settings Quintin: Do captions need to identify speakers and significant sounds? JJ: Is there a difference or difference in guidance from the Web 1.2.2? JJ: Mostly on Web captions are not being picked up Detlev: Players not picking up captions: Is this an app or browsing context? Quitin: Native players provided out-of-the-box on Android/iOS Detlev: so it's mostly guidance for the videoplayer creators vs developers Agree JJ: Perhaps provide guidance to facilitate understanding

Summary:

1. Respecting OS User Settings:

   • Quintin: Emphasized the importance of mentioning to respect the OS user settings in mobile app development.

2. Identification in Captions:

   • Quintin: Raised the question of whether captions need to identify speakers and significant sounds.

3. Guidance Differences:

   • JJ: Asked if there are differences or specific guidance from Web 1.2.2 regarding caption usage in mobile apps.
   • Detlev: Inquired about issues where players do not pick up captions, clarifying if this is in an app or browsing context.
   • Quintin: Noted that it's about native players which are provided out-of-the-box on Android/iOS platforms.
   • Detlev: Suggested that guidance primarily applies to video player creators rather than developers.
   • JJ: Proposed providing guidance to facilitate better understanding in implementing captions effectively.

[JJdeGroot]

Related issue: https://github.com/w3c/matf/issues/19

[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.2.

NOTE The WCAG 2 definition of “captions” notes that “in some countries, captions are called subtitles”. They are also sometimes referred to as “subtitles for the hearing impaired.” Per the definition in WCAG 2, to meet this success criterion, whether called captions or subtitles, they would have to provide “synchronized visual and / or text alternative for both speech and non-speech audio information needed to understand the media content” where non-speech information includes “sound effects, music, laughter, speaker identification and location”.

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.

[JJdeGroot]

Closing this issue because the draft language has been accepted.