- From: Janina Sajka <janina@rednote.net>
- Date: Wed, 20 Sep 2017 10:33:06 -0400
- To: Thierry MICHEL <tmichel@w3.org>
- Cc: Michael Cooper <cooper@w3.org>, group-apa-chairs@w3.org, public-tt@w3.org, "public-texttracks@w3.org" <public-texttracks@w3.org>
Hi, Thierry, All: My apologies for taking so long to present this fairly straight forward editorial suggestion on the WebVTT draft. You have an alt= that is far too long, in APA's view. We would suggest using Figure/Details (or even a longdesc) instead. The code involved is the following: <div class="note" role="note"> <p>The following diagram illustrates how anchoring of a region to a video viewport works. The black cross is the anchor, orange explains the anchor's offset within the region and green the anchor's offset within the viewport. Think of it as sticking a pin through a note onto a board:</p> <p><img alt="Within the video viewport, there is a WebVTT region. Inside the region, there is an anchor point marked with a black cross. The vertical and horizontal distance from the video viewport's edges to the anchor is marked with green arrows, representing the region viewport anchor X and Y offsets. The vertical and horizontal distance from the region's edges to the anchor is marked with orange arrows, representing the region anchor X and Y offsets. The size of the region is represented by the region width for the horizontal axis, and region lines for the vertical axis." src="webvtt-region-diagram.png"></p> </div> The problem, of course, with long alt= is that the user who relies on alt= is forced to digest the complete text each and every time they source the page. With longish alt= that becomes quite annoying. That's why we have Figure/Details (and longdesc), as you may well recall. We want the textual description. We just don't want to enforce it without the user asking to see the details. WebVTT has done a great job of supporting the requirements we developed in the Media Access User Requirements. This is an editorial nit, so I apologize again for holding you up over it. Janina If any questions, please don't hesitate to ask! Thierry MICHEL writes: > Hi Michael, > > Thank for you review of WebVTT working draft > Looking forward to have Janina 's concrete suggestion to incorporate in the > spec. > > Best, > > Thierry > > > Le 08/09/2017 à 16:21, Michael Cooper a écrit : > > Hi Thierry - we discussed this in APA Wednesday and confirm we have no > > substantive comments on the spec. However, we did a quick accessibility > > check and found a diagram with a super-long alt text. We appreciate the > > effort but long alt text can be hard to use; it would be better to have > > a short alt text and put the longer content into a description (multiple > > approaches are available to do that). Janina is meant to write up a more > > concrete suggestion around that for you. Michael > > > > > > On 08/09/2017 2:51 AM, Thierry MICHEL wrote: > > > This is a reminder for the Call for Review of WebVTT ending 22 Sept > > > 2017 (see previous message bellow). > > > > > > > > > Kind regards, > > > On behalf of Nigel Megitt, co-Chair, W3C Timed Text Working Group > > > Thierry Michel, Staff Contact for TTWG. > > > > > > Le 09/08/2017 à 10:42, Thierry MICHEL a écrit : > > > > Dear Accessible Platform Architectures (APA) Working Group, > > > > > > > > The W3C Timed Text Working Group has recently published a new working > > > > draft of WebVTT: The Web Video Text Tracks Format [1]. > > > > > > > > The main use of WebVTT is for marking up external text track > > > > resources in connection with the HTML <track> element. WebVTT > > > > files provide captions or subtitles for video content, and also > > > > text video descriptions [MAUR], chapters for content navigation, > > > > and more generally any form of metadata that is time-aligned > > > > with audio or video content. > > > > > > > > The TTWG invites you to review this draft, and requests comments to be > > > > received by 22 Sept 2017. These comments will be used to fulfill the > > > > W3C Process [3] requirement for Wide Review of drafts, and Horizontal > > > > Review [4] prior to publication as Candidate Recommendation. > > > > > > > > If you wish to make comments regarding this document, please send them > > > > to public-tt@w3.org <mailto:public-tt@w3.org?subject=%5BWebVTT%5B> with > > > > [WebVTT] at the start of your email's subject. All comments are welcome, > > > > however the scope of review will be mainly focused on the new features > > > > introduced in WebVTT, since the First Public Working Draft [5] > > > > on 13 November 2014 which triggered a first Wide Review . > > > > > > > > A cumulative summary of all changes applied to this version since the > > > > WebVTT First Public Working Draft is available for your convenience [6]. > > > > > > > > > > > > [1] WebVTT Wide Review WD > > > > https://www.w3.org/TR/2017/WD-webvtt1-20170808/ > > > > [2] WebVTT latest version > > > > https://www.w3.org/TR/webvtt1/ > > > > [3] W3C Process > > > > https://www.w3.org/2017/Process-20170301/ > > > > [4] Horizontal Review > > > > https://www.w3.org/Guide/Charter.html#horizontal-review > > > > [5] WebVTT First Public Working Draft. > > > > https://www.w3.org/TR/2014/WD-webvtt1-20141113/ > > > > [6] https://www.w3.org/TR/2017/WD-webvtt1-20170808/changes-FPWD.html > > > > > > > > Kind regards, > > > > > > > > On behalf of David Singer, co-Chair, W3C Timed Text Working Group > > > > Thierry Michel, Staff Contact for TTWG. > > > > > -- Janina Sajka, Phone: +1.443.300.2200 sip:janina@asterisk.rednote.net Email: janina@rednote.net Linux Foundation Fellow Executive Chair, Accessibility Workgroup: http://a11y.org The World Wide Web Consortium (W3C), Web Accessibility Initiative (WAI) Chair, Accessible Platform Architectures http://www.w3.org/wai/apa
Received on Wednesday, 20 September 2017 17:10:21 UTC