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

Preliminary WebVTT accessibility review

From: Janina Sajka <janina@rednote.net>
Date: Sat, 18 Apr 2015 21:49:20 -0400
To: Thierry MICHEL <tmichel@w3.org>
Cc: "wai@w3.org >> WAI Domain" <w3t-wai@w3.org>, judy Brewer <jbrewer@w3.org>, Andrew Kirkpatrick <akirkpat@adobe.com>, joshue.oconnor@cfit.ie, 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>
Message-ID: <20150419014920.GA17177@opera.rednote.net>
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:

Our reference document for accessibility requirements is the note track
"Media Accessibility User Requirements (MAUR)" available at:

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

Concern:	The spec should include feature explanations in plain

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.

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.

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.



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
		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 01:50:12 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 17:43:47 UTC