- From: Noble, Stephen <steve.noble@pearson.com>
- Date: Fri, 23 Aug 2019 12:29:14 -0400
- To: Janina Sajka <janina@rednote.net>
- Cc: Accessible Platform Architectures Administration <public-apa-admin@w3.org>
- Message-ID: <CAA6F_xmRpW-Ez_UX=7G_9XWOy_==WreUXUG82iPzCFJRLEf2dg@mail.gmail.com>
+1 On Wed, Aug 21, 2019 at 12:47 PM Janina Sajka <janina@rednote.net> wrote: > Colleagues: > > This is a Call for Consensus (CfC) to the Accessible Platform > Architectures (APA) Working Group on the publication of three First Public > Working Draft (FPWD) documents from our Pronunciation Task Force. > > * User Scenarios< > https://urldefense.proofpoint.com/v2/url?u=https-3A__w3c.github.io_pronunciation_user-2Dscenarios_&d=DwIBAg&c=0YLnzTkWOdJlub_y7qAx8Q&r=e0Vlq1-H9s-GydHZ8dXqhyYdB-jv9NvThaezSlozh9I&m=TFjLK2MTtavXY-QpGfMqx4AqfgRWDx-26NHzY2fkaHc&s=AxLygMoQzYNPMhoNeUpQwH76dSk6YyeVcvwaZBcqPWU&e= > > > > * Use Cases< > https://urldefense.proofpoint.com/v2/url?u=https-3A__w3c.github.io_pronunciation_use-2Dcases_&d=DwIBAg&c=0YLnzTkWOdJlub_y7qAx8Q&r=e0Vlq1-H9s-GydHZ8dXqhyYdB-jv9NvThaezSlozh9I&m=TFjLK2MTtavXY-QpGfMqx4AqfgRWDx-26NHzY2fkaHc&s=ZTpi356OmidlxlmpCit7aEQrJHqKPq8v1nGmNXi5Vjc&e= > > > > * Gap Analysis< > https://urldefense.proofpoint.com/v2/url?u=https-3A__w3c.github.io_pronunciation_gap-2Danalysis_&d=DwIBAg&c=0YLnzTkWOdJlub_y7qAx8Q&r=e0Vlq1-H9s-GydHZ8dXqhyYdB-jv9NvThaezSlozh9I&m=TFjLK2MTtavXY-QpGfMqx4AqfgRWDx-26NHzY2fkaHc&s=BtbhLqFcF0qX6bU4jU3bu70Ckjp-2pzwkZ6q1LdU-t0&e= > > > > Please review the documents noted above. Please note that several > editorial tweaks are expected, but no substantive changes before > publication. > > *** ACTION TO TAKE*** > > This CfC is now open for objection, comment, as well as statements of > support via email. Silence will be interpreted as support, though > messages of support are certainly welcome. > > If you object to this proposed action, or have comments concerning this > proposal, whether with all of these proposed publications or any > particular one, please respond by replying on list to this message no > later than 23:59 (Midnight) Boston Time, Friday 23 August. > > Best, > > Janina > > > ------------------------------------------------------------------------------ > > Janina Sajka > > Linux Foundation Fellow > Executive Chair, Accessibility Workgroup: > https://urldefense.proofpoint.com/v2/url?u=http-3A__a11y.org&d=DwIBAg&c=0YLnzTkWOdJlub_y7qAx8Q&r=e0Vlq1-H9s-GydHZ8dXqhyYdB-jv9NvThaezSlozh9I&m=TFjLK2MTtavXY-QpGfMqx4AqfgRWDx-26NHzY2fkaHc&s=ZvDHdT_mw9XncMWQpwc_yLKA0mlBR_geO-aDo22to88&e= > > The World Wide Web Consortium (W3C), Web Accessibility Initiative (WAI) > Chair, Accessible Platform Architectures > https://urldefense.proofpoint.com/v2/url?u=http-3A__www.w3.org_wai_apa&d=DwIBAg&c=0YLnzTkWOdJlub_y7qAx8Q&r=e0Vlq1-H9s-GydHZ8dXqhyYdB-jv9NvThaezSlozh9I&m=TFjLK2MTtavXY-QpGfMqx4AqfgRWDx-26NHzY2fkaHc&s=qZXN_hXs3EQS14RcR1BT4kOWB7MY8Xfu9_RaXK2KTwc&e= > > Here is my proposed feedback to the Timed Text Working Group: > > > > <draft-feedback> > > > > 1. While we appreciate that TTML Profiles for Internet Media Subtitles > and Captions 1.1 > <https://urldefense.proofpoint.com/v2/url?u=https-3A__www.w3.org_TR_ttml-2Dimsc1.1_&d=DwMFaQ&c=0YLnzTkWOdJlub_y7qAx8Q&r=e0Vlq1-H9s-GydHZ8dXqhyYdB-jv9NvThaezSlozh9I&m=TFjLK2MTtavXY-QpGfMqx4AqfgRWDx-26NHzY2fkaHc&s=iR3fYp8SrXhfQar8msPXDTaseChFJceUbRSLSgO8ol0&e=> > is depending on Timed Text Markup Language 2 (TTML2) > <https://urldefense.proofpoint.com/v2/url?u=https-3A__www.w3.org_TR_ttml2_&d=DwMFaQ&c=0YLnzTkWOdJlub_y7qAx8Q&r=e0Vlq1-H9s-GydHZ8dXqhyYdB-jv9NvThaezSlozh9I&m=TFjLK2MTtavXY-QpGfMqx4AqfgRWDx-26NHzY2fkaHc&s=2kNEzUgImmLvcMQfUoKaDRmiT_EssH0_QqP6m-QEaoE&e=>, > it should still include an introduction that guides the reader to a better > understanding of its content. Such an introduction could respond to the > following questions: > 1. Why are profiles needed for text-only and image-only > captions/subtitles? > 2. What are typical use cases for a image-only captions/subtitles? > 3. What is the purpose of a presentation processor, and a > transformation processor? > > > > 1. 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. How can we find a good solution for these conflicting interests > between author and user? We would like to get into a discussion with you > on this issue. > > > > 1. Section 2 Documentation Conventions (applies also to Timed Text > Markup Language 2 (TTML2) > <https://urldefense.proofpoint.com/v2/url?u=https-3A__www.w3.org_TR_ttml2_&d=DwMFaQ&c=0YLnzTkWOdJlub_y7qAx8Q&r=e0Vlq1-H9s-GydHZ8dXqhyYdB-jv9NvThaezSlozh9I&m=TFjLK2MTtavXY-QpGfMqx4AqfgRWDx-26NHzY2fkaHc&s=2kNEzUgImmLvcMQfUoKaDRmiT_EssH0_QqP6m-QEaoE&e=> > section 2.3). For accessibility of the spec, information such as whether an > element is deprecated or obsoleted should not be indicated by color (or > background color) alone (cf. WCAG 2.0 SC 1.4.1 > <https://urldefense.proofpoint.com/v2/url?u=https-3A__www.w3.org_WAI_WCAG20_quickref_-23visual-2Daudio-2Dcontrast-2Dwithout-2Dcolor&d=DwMFaQ&c=0YLnzTkWOdJlub_y7qAx8Q&r=e0Vlq1-H9s-GydHZ8dXqhyYdB-jv9NvThaezSlozh9I&m=TFjLK2MTtavXY-QpGfMqx4AqfgRWDx-26NHzY2fkaHc&s=XmbmjovbbvM3ln5xy7D3wo4jkNEuSz5xM2Za-DXedBM&e=>). > > > > > 1. Section 5.1 General. The method of associating a text profile > document instance with an image profile document instance should be > specified for interoperability reasons, and not be left open to the > specific implementation. Also, the association should be in both ways, > i.e. also from the image profile document instance to the text profile > document instance. > > > > 1. Section 6 Supported Features and Extensions. All font-related > features are prohibited for the image profile. This seems to be an > unnecessary restriction if the image profile contains images in SVG format > which could be rendered differently based on the author’s choice of font > characteristics. > > > > 1. Section 7.7.3 itts:forcedDisplay. 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. > > > > 1. Section 7.7.4 itts:altText. While we see this feature as useful > for accessibility purposes, it should be mandatory for images rather than > recommended only. As mentioned in the spec, one could take the pertaining > text passage from the text profile document instance – but (1) an > accompanying text profile is not required, and (2) the alternative text for > the image could be different from the textual caption. Therefore, the > itts:altText element should always be specified, but it should be empty for > decorative images (not clear if a “decorative image” used as a caption > makes sense anyway). By requiring an itts:altText for every image, but > allowing for an empty element in case of a decorative image, we would align > it with the alt attribute in HTML5 for images. > > > > </draft-feedback> > > > > Best regards, > > Gottfried > > > > -----Ursprüngliche Nachricht----- > Von: Accessible Platform Architectures Working Group Issue Tracker [mailto: > sysbot+tracker@w3.org] > Gesendet: Mittwoch, 18. Oktober 2017 09:29 > An: public-apa@w3.org > Betreff: apa-ACTION-2152: Review ttml profiles for internet media > subtitles and captions 1.1 https://www.w3.org/tr/ttml-imsc1.1/ > > > > apa-ACTION-2152: Review ttml profiles for internet media subtitles and > captions 1.1 https://www.w3.org/tr/ttml-imsc1.1/ > <https://urldefense.proofpoint.com/v2/url?u=https-3A__www.w3.org_tr_ttml-2Dimsc1.1_&d=DwMFaQ&c=0YLnzTkWOdJlub_y7qAx8Q&r=e0Vlq1-H9s-GydHZ8dXqhyYdB-jv9NvThaezSlozh9I&m=TFjLK2MTtavXY-QpGfMqx4AqfgRWDx-26NHzY2fkaHc&s=_twnAUM5BAMJpVytuWv6ts1wz0zDkzWYyY9uBSPvhQ0&e=> > > > > http://www.w3.org/WAI/APA/track/actions/2152 > <https://urldefense.proofpoint.com/v2/url?u=http-3A__www.w3.org_WAI_APA_track_actions_2152&d=DwMFaQ&c=0YLnzTkWOdJlub_y7qAx8Q&r=e0Vlq1-H9s-GydHZ8dXqhyYdB-jv9NvThaezSlozh9I&m=TFjLK2MTtavXY-QpGfMqx4AqfgRWDx-26NHzY2fkaHc&s=8QEZVhDHzFoz8qNcSpVz9_jSnEV-1BysXKb_LH8IJ2Q&e=> > > > > Assigned to: Gottfried Zimmermann > > > > > > > > > > > > > > > > > -- Steve Noble Instructional Designer, Accessibility Psychometrics & Testing Services *Pearson* 502 969 3088 steve.noble@pearson.com
Received on Friday, 23 August 2019 16:29:54 UTC