W3C home > Mailing lists > Public > public-html-a11y@w3.org > October 2014

[Bug 27054] Accessibility Concerns

From: <bugzilla@jessica.w3.org>
Date: Fri, 31 Oct 2014 00:16:46 +0000
To: public-html-a11y@w3.org
Message-ID: <bug-27054-3290-flsCZRMXci@http.www.w3.org/Bugs/Public/>
https://www.w3.org/Bugs/Public/show_bug.cgi?id=27054

--- Comment #8 from John Foliot <john@foliot.ca> ---
(In reply to David Dorwin from comment #7)
> > 
> > Note that I'm not claiming that anyone is actually planning to a) let
> > caption tracks [that are actually separate tracks as opposed to being U.S.
> > TV captioning-compatible data inside an MPEG-2 video track] be encrypted and
> > b) not let the decrypted caption track flow into the browser engine.
> 
> Would either of you like to propose text to address these concerns? Maybe we
> should file a separate sub-bug specifically for text track issues.

It appears that advisory text against doing this will likely suffice - there
does not appear to be any actual implementation of this today. In conversation
with David Dorwin at TPAC, I will return to the accessibility Task force and we
will supply draft author advisory text that can be added to the specification.
David if you want to file a bug, I can respond to that, or I can respond via
this bug - your call.

> 
> > (In reply to David Dorwin from comment #5)
> > > EME assumes encryption is on blocks within the media container.
> > 
> > While this may be the assumption and what every implements in practice, is
> > there actually something in the spec that prohibits the encryption being a
> > wrapper around the media container? (Not that it's relevant for this
> > bug--just pointing out how many things EME doesn't actually specify, AFAICT.)
> 
> Good point. What restrictions do we need to place on the media? Maybe open a
> separate bug for this since it's not specifically an accessibility issue.
> Also, if you find other underspecification issues, please file bugs for
> those too. A number of assumptions were not clearly documented, and we've
> been trying to address those.

I believe this is out of scope for accessibility concerns. I will leave it to
others to file a bug and respond

-- 
You are receiving this mail because:
You are on the CC list for the bug.
Received on Friday, 31 October 2014 00:16:47 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 19:56:44 UTC