RE2: apa-ACTION-2224: Review ttml profiles for internet media subtitles and captions 1.2 https://www.w3.org/tr/ttml-imsc1.2/ from Gottfried Zimmermann $Lists$ on 2020-01-22 (public-apa@w3.org from January 2020)

From: Gottfried Zimmermann $Lists$ <zimmermann@accesstechnologiesgroup.com>
Date: Wed, 22 Jan 2020 19:11:52 +0100
To: "'Accessible Platform Architectures Working Group'" <public-apa@w3.org>
Message-ID: <006d01d5d14f$6c6be6d0$4543b470$@accesstechnologiesgroup.com>

Here is a second version of my draft for feedback, based on our discussion today in the APA call. Thank you for your useful comments, especially to John.

Feel free to provide any comments, and if possible, make suggestions for edits.

<draft-feedback version=“2“>

(1) Reference to WCAG 2.1. We appreciate the addition of section <https://www.w3.org/TR/2019/WD-ttml-imsc1.2-20191128/#wcag-applications> D.1 WCAG Considerations and its content. This is very helpful. We would, though, like to change the words “WCAG 2.1 recommends” into “WCAG 2.1 requires”, since the success criteria are requirements rather than recommendations. In addition to the guidelines and success criteria you already reference, we would like to see references to other WCAG 2.1 success criteria that are applicable to the TTML profiles specification, such as:

a. <https://www.w3.org/TR/2018/REC-WCAG21-20180605/#contrast-minimum> Success Criterion 1.4.3 Contrast (Minimum) (applying to the text-only profile)

b. <https://www.w3.org/TR/2018/REC-WCAG21-20180605/#non-text-contrast> Success Criterion 1.4.11 Non-text Contrast (applying to the image-only profile)

c. <https://www.w3.org/TR/2018/REC-WCAG21-20180605/#language-of-page> Success Criterion 3.1.1 Language of Page (using the xml:lang attribute)

d. <https://www.w3.org/TR/2018/REC-WCAG21-20180605/#language-of-parts> Success Criterion 3.1.2 Language of Parts (using the xml:lang attribute)

(2) Reference to MAUR. We also appreciate the addition of section D.2 MAUR Considerations <https://www.w3.org/TR/2019/WD-ttml-imsc1.2-20191128/#maur-applications> .

(3) <https://www.w3.org/TR/2019/WD-ttml-imsc1.2-20191128/#altText> 7.12.2 altText named metadata item. This is directly related to the accessibility requirement of having an alternate text version for images ( <https://www.w3.org/TR/2018/REC-WCAG21-20180605/#non-text-content> Success Criterion 1.1.1 Non-text Content). Could you add a note here saying something like: “Note: Authors are encouraged to provide text alternatives for every non-decorative image and/or compound image set by using altText named metadata item. This is necessary for making the document accessible to persons with (visual) disabilities, thus complying with <https://www.w3.org/TR/2018/REC-WCAG21-20180605/#non-text-content> WCAG 2.1 success criterion 1.1.1 (Non-text content).”

(4) Introduction for first-time readers. The document would be easier to read for first-time readers if it had an introduction that guides the reader to a better understanding of its content. Such an introduction could respond to the following questions:

a. Why are profiles needed for text-only and image-only captions/subtitles?

b. What are typical use cases for image-only captions/subtitles?

(5) There is a general issue with the way that an author specifies layout characteristics of captions and subtitles, such as font size, font family, line height, background and positioning. It should be made clear that authors can define the viewport and text characteristics, but these may be overridden by the user by setting up their user agent accordingly (cf. MAUR, 3.7 Requirements on the use of the viewport <https://www.w3.org/TR/2015/NOTE-media-accessibility-reqs-20151203/#requirements-on-the-use-of-the-viewport> ). For example, a user with vision impairment may want to have all captions displayed in the lower third of the screen with a big font, disregarding the definition of various viewports and font types by the author. We recommend to add a note to the spec to hint authors to the final rendition of their document may not follow their specified styling and positioning, but follow user-defined styling and positioning instead.

(6) <https://www.w3.org/TR/2019/WD-ttml-imsc1.2-20191128/#forced-content> Section C. Forced content. This seems like a temporary solution. Wouldn’t it be better to define semantic layers of information that each could be made visible and invisible at runtime as appropriate for the user? For example, the user may want to see either speech-only (subtitles), narration speech only (parts of subtitles), foreign-language speech-only (parts of subtitles) or any combination of them.

</draft-feedback>

Von: Gottfried Zimmermann (Lists) [mailto:zimmermann@accesstechnologiesgroup.com]
Gesendet: Mittwoch, 22. Januar 2020 17:50
An: 'Accessible Platform Architectures Working Group' <public-apa@w3.org>
Betreff: RE: apa-ACTION-2224: Review ttml profiles for internet media subtitles and captions 1.2 https://www.w3.org/tr/ttml-imsc1.2/

I have had a look at TTML Profiles for Internet Media Subtitles and Captions 1.2 - W3C First Public Working Draft 28 November 2019 <https://www.w3.org/TR/2019/WD-ttml-imsc1.2-20191128/> , based in my previous review from 2017-11-14 <https://lists.w3.org/Archives/Public/public-apa/2017Nov/0008.html> , and on the summary of substantive changes <https://www.w3.org/TR/2019/WD-ttml-imsc1.2-20191128/#substantive-changes-summary> .

Here is my proposed feedback to the Timed Text Working Group on:

<draft-feedback>

(1) Reference to WCAG 2.1. We appreciate the addition of section D.1 WCAG Considerations <https://www.w3.org/TR/2019/WD-ttml-imsc1.2-20191128/#wcag-applications> and its content. Here, we would like to see references to other WCAG 2.1 success criteria that are applicable to the TTML profiles specification, such as:

a. Success Criterion 1.4.3 Contrast (Minimum) <https://www.w3.org/TR/2018/REC-WCAG21-20180605/#contrast-minimum>

b. Success Criterion 1.4.4 Resize text <https://www.w3.org/TR/2018/REC-WCAG21-20180605/#resize-text>

c. Success Criterion 1.4.11 Non-text Contrast <https://www.w3.org/TR/2018/REC-WCAG21-20180605/#non-text-contrast>

d. Success Criterion 3.1.1 Language of Page <https://www.w3.org/TR/2018/REC-WCAG21-20180605/#language-of-page>

e. Success Criterion 3.1.2 Language of Parts <https://www.w3.org/TR/2018/REC-WCAG21-20180605/#language-of-parts>

(2) 7.12.2 altText named metadata item <https://www.w3.org/TR/2019/WD-ttml-imsc1.2-20191128/#altText> . This is directly related to the accessibility requirement of having an alternate text version for images (Success Criterion 1.1.1 Non-text Content <https://www.w3.org/TR/2018/REC-WCAG21-20180605/#non-text-content> ). Could you add a note here saying something like: “Note: Authors are encouraged to provide text alternatives for every non-decorative image and/or compound image set by using altText named metadata item. This is necessary for making the document accessible to persons with (visual) disabilities, thus complying with WCAG 2.1 success criterion 1.1.1 (Non-text content) <https://www.w3.org/TR/2018/REC-WCAG21-20180605/#non-text-content> .”

(3) Introduction for first-time readers. The document would be easier to read for first-time readers if it had an introduction that guides the reader to a better understanding of its content. Such an introduction could respond to the following questions:

a. Why are profiles needed for text-only and image-only captions/subtitles?

b. What are typical use cases for image-only captions/subtitles?

(4) We are still not happy with the relation between author-specified formatting and user-specified formatting (if possible at all). There is a general issue with the way that an author specifies layout characteristics of captions and subtitles, such as font size, font family, line height, background and positioning. The spec describes the approach of the author specifying a “fixed layout” for captions and subtitles that the user cannot change. However, it must be possible for the user to overwrite the author’s choice of font size, or background color, for example. This is necessary for accessibility reasons, in the same way that browsers allow the user to change font size and background color. We would like to get into a discussion with you on this issue.

(5) Section C. Forced content <https://www.w3.org/TR/2019/WD-ttml-imsc1.2-20191128/#forced-content> . This seems like a temporary solution. Wouldn’t it be better to define semantic layers of information that each could be made visible and invisible at runtime as appropriate for the user? For example, the user may want to see either speech-only (subtitles), narration speech only (parts of subtitles), foreign-language speech-only (parts of subtitles) or any combination of them.

</draft-feedback>

Best regards,

Gottfried

-----Ursprüngliche Nachricht-----
Von: Accessible Platform Architectures Working Group Issue Tracker [mailto:sysbot+tracker@w3.org]
Gesendet: Mittwoch, 4. Dezember 2019 18:45
An: public-apa@w3.org <mailto:public-apa@w3.org>
Betreff: apa-ACTION-2224: Review ttml profiles for internet media subtitles and captions 1.2 https://www.w3.org/tr/ttml-imsc1.2/

apa-ACTION-2224: Review ttml profiles for internet media subtitles and captions 1.2 <https://www.w3.org/tr/ttml-imsc1.2/> https://www.w3.org/tr/ttml-imsc1.2/

<https://www.w3.org/WAI/APA/track/actions/2224> https://www.w3.org/WAI/APA/track/actions/2224

Assigned to: Gottfried Zimmermann

Received on Wednesday, 22 January 2020 18:11:57 UTC