- From: Glenn Adams <glenn@skynav.com>
- Date: Tue, 19 Aug 2014 10:27:48 -0600
- To: Nigel Megitt <nigel.megitt@bbc.co.uk>
- Cc: TTWG <public-tt@w3.org>
- Message-ID: <CACQ=j+dBrV+U1y3Ouwb2zCSzoh+UhOvRfDH86HmU9RikOg3FmQ@mail.gmail.com>
On Tue, Aug 19, 2014 at 10:20 AM, Nigel Megitt <nigel.megitt@bbc.co.uk> wrote: > Thanks for the heads-up Glenn. It looks like these bits: > http://www.w3.org/TR/2014/WD-media-accessibility-reqs-20140814/#captioning > and > http://www.w3.org/TR/2014/WD-media-accessibility-reqs-20140814/#enhanced-captions-subtitles are > particularly relevant to us. > > Would anyone object to adopting those requirements as a subset of the > requirements that TTML 2 and IMSC 1 should be measured against when > assessing their conformance when it comes to LC/CR as per the process for > publishing Recommendations (either the old or the new process)? > I read through the requirements that would pertain to TTML, and believe the following need to be addressed: - ruby (CC-18) - hyperlinking (ECC-2) - reading speed modification (ECC-5) I believe tatechuyoko (CC-16) is already covered by tts:textOrientation. Reading speed may already be covered (at least in part) by the playRate parameter of [1]. [1] https://dvcs.w3.org/hg/ttml/raw-file/tip/ttml2/spec/ttml2.html#time-expression-semantics-media > Kind regards, > > Nigel > > From: Glenn Adams <glenn@skynav.com> > Date: Tuesday, 19 August 2014 16:59 > To: TTWG <public-tt@w3.org> > Subject: FYI - Media Accessibility User Requirements WD > Resent-From: <public-tt@w3.org> > Resent-Date: Tuesday, 19 August 2014 17:00 > > Media Accessibility User Requirements Working Draft Updated > > 14 August 2014 | Archive > > http://www.w3.org/blog/news/archives/4024 > > The Protocols and Formats Working Group (PFWG) today published > an updated Working Draft of "Media Accessibility User > Requirements," a planned W3C Working Group Note. This document > describes the accessibility requirements of people with > disabilities with respect to audio and video on the Web, > particularly in the context of HTML5. It explains alternative > content technologies that people use to get audio and video > content, and how these fit in the larger picture of > accessibility, both technically within a web user agent and > from a production process point of view. Learn more about the > Web Accessibility Initiative (WAI). > > http://www.w3.org/WAI/PF/ > http://www.w3.org/TR/2014/WD-media-accessibility-reqs-20140814/ > http://www.w3.org/WAI/ > >
Received on Tuesday, 19 August 2014 16:28:37 UTC