W3C home > Mailing lists > Public > public-html-a11y@w3.org > April 2015

Re: Preliminary WebVTT accessibility review

From: Silvia Pfeiffer <silviapfeiffer1@gmail.com>
Date: Sun, 19 Apr 2015 13:09:22 +1000
Message-ID: <CAHp8n2m5QPJ5Gv6rOYdoAQujC6LJ1ytJyjKHe7h6=Kit8achzw@mail.gmail.com>
To: Thierry MICHEL <tmichel@w3.org>, "wai@w3.org >> WAI Domain" <w3t-wai@w3.org>, judy Brewer <jbrewer@w3.org>, Andrew Kirkpatrick <akirkpat@adobe.com>, Joshue O Connor <joshue.oconnor@cfit.ie>, Michael Cooper <cooper@w3.org>, Nigel Megitt <nigel.megitt@bbc.co.uk>, David Singer <singer@apple.com>, Philippe Le Hegaret <plh@w3.org>, W3C Public TTWG <public-tt@w3.org>, HTML Accessibility Task Force <public-html-a11y@w3.org>, "W3C WAI Protocols & Formats" <public-pfwg@w3.org>
Hi Janina, all,

Many thanks to the HTML A11y Task Force for your review.

I have registered bugs in the bug tracker of the Text Tracks Community
Group as referenced below inline.
We will collect feedback from the CG in the bug tracker discussions as
well as within the TT WG.
Please invite interested people to get involved in the CG discussions
on the bug tracker.

The intention is to aggregate feedback from the CG and the TT-WG on
your identified issues and report back in summarised form.

Best Regards,

On Sun, Apr 19, 2015 at 11:49 AM, Janina Sajka <janina@rednote.net> wrote:
> Dear Thierry, All:
> The HTML-A11Y Task Force has reviewed the WebVTT FPWD specification
> during our face to face meeting this past Friday 17 April. Minutes of
> this session are available at:
> http://www.w3.org/2015/04/17-html-a11y-minutes.html#item01
> Our reference document for accessibility requirements is the note track
> "Media Accessibility User Requirements (MAUR)" available at:
> http://w3c.github.io/pfwg/media-accessibility-reqs/
> Please note that several people took follow up actions to provide
> additional details in the next week or so. Meanwhile, these are the
> concerns we identified:
> Concern:        Users of Magnification
> We have concerns regarding the impact on users of magnification with
> respect to several WebVTT specifications. Has the group considered its
> specification's impact on users of magnification? Items raising this
> concern included:
> *       Snap to flag
> *       Sizing of the captions rendering area
> *       Visibility of captions when text is zoomed

Issue registered in the CG: https://www.w3.org/Bugs/Public/show_bug.cgi?id=28509

> Concern:        The spec should include feature explanations in plain
> language
> We are concerned that too often in this document a feature's function
> can only be understood by parsing the provided algorithms. We would
> prefer plain language explanations be included. A specific case in point
> would be Sec. 6.1.

Issue registered in the CG: https://www.w3.org/Bugs/Public/show_bug.cgi?id=28510

Note that Sec 6.1 has been resolved in the latest editor draft:

> Concern:        Captions on the audio element
> We believe this section misrepresents the situation. It is incorrect to
> tell the user "There is nothing to render." When captions are provided
> for audio content there is indeed something to render, even if the
> available user agent is incapable of rendering it.

Issue registered in the CG: https://www.w3.org/Bugs/Public/show_bug.cgi?id=28511

> Concern:        CSS
> We did not identify specific items of concern, but are committed to
> follow up and may request a joint meeting to better understand the
> implementation of CSS in this specification.

I've not registered a bug for this. If you can identify any concrete
accessibility related issues around CSS and WebVTT, I'll be happy to
register a bug. Note that the CSS WG has also already provided
extensive feedback on WebVTT, which you may want to review.

Note that the WebVTT syntax does not require the use of CSS, however
the specification has sections that only make sense in connection with
a HTML resource, such as the DOM construction, the rendering section
and the api section.

Here is a link to all the open issues on WebVTT in the TT CG:

Hope this helps.

Best Regards,

> Janina
> *
> Thierry MICHEL writes:
>> Judy,
>> The TTWG is holding its F2F and we discussed the WebVTT wide review.
>> We have received feedback from the other WGs we have dependencies with. We
>> are only missing the Acessibility review.
>> When do you plan to send your review. Could you please give us a date so we
>> could organize to process all comments.
>> Best,
>> Thierry
>> On 13/02/2015 17:33, Thierry MICHEL wrote:
>> >Hi,
>> >
>> >The Timed Text WG has published
>> >WebVTT: The Web Video Text Tracks Format
>> >W3C First Public Working Draft 13 November 2014
>> >
>> >  http://www.w3.org/TR/2014/WD-webvtt1-20141113/
>> >
>> >
>> >The TTWG invites the Accessibility people to review this document.
>> >
>> >- WCAG Working Group
>> >- Protocols and Formats Working Group
>> >
>> >Comments are welcome to <public-tt@w3.org>  with [webvtt] at the start
>> >of your email's subject.
>> >
>> >Best,
>> >
>> >Thierry Michel: Team 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,  Protocols & Formats     http://www.w3.org/wai/pf
>         Indie UI                        http://www.w3.org/WAI/IndieUI/
Received on Sunday, 19 April 2015 03:10:11 UTC

This archive was generated by hypermail 2.3.1 : Sunday, 19 April 2015 03:10:11 UTC