W3C home > Mailing lists > Public > w3c-wai-ig@w3.org > January to March 2013

RE: HTML5 - DRM - accessibility

From: <accessys@smart.net>
Date: Fri, 29 Mar 2013 14:40:20 -0400 (EDT)
To: "Foliot, John" <john.foliot@chase.com>
cc: "w3c-wai-ig@w3.org" <w3c-wai-ig@w3.org>
Message-ID: <Pine.LNX.4.60.1303291439450.24390@cygnus.smart.net>

from what I am hearing it will not work at all on Linux based systems

Bob

On Fri, 29 Mar 2013, Foliot, John wrote:

> Date: Fri, 29 Mar 2013 17:59:19 +0000
> From: "Foliot, John" <john.foliot@chase.com>
> To: "accessys@smart.net" <accessys@smart.net>,
>     "w3c-wai-ig@w3.org" <w3c-wai-ig@w3.org>
> Cc: "w3c-wai-ig@w3.org list" <w3c-wai-ig@w3.org>
> Subject: RE: HTML5 - DRM - accessibility
> Resent-Date: Fri, 29 Mar 2013 17:59:56 +0000
> Resent-From: w3c-wai-ig@w3.org
> 
> accessys@smart.net wrote:
>>
>> I have not been following the HTML5 discussions on the
>> main W3C list and was alerted yesterday by someone that
>> HTML5 is considering adding DRM (digital rights management)
>> restrictions to the acceptable code.  much of DRM locks out
>> access software as it sees this as an attempt to "pirate"
>> the locked software or application.
>> If this is in fact accurate it should be addressed now before
>> it is released.
>
>
> Currently, there is work underway for an API that would allow for Encrypted Media (https://dvcs.w3.org/hg/html-media/raw-file/tip/encrypted-media/encrypted-media.html) that is already being implemented into browsers and devices (such as Chrome/ChromeBook) https://groups.google.com/forum/#!topic/chromebook-central/c4p5DdehuHs
>
> To date, it appears that the EME does not have any UI interactions, and as such will likely have few if any issues with respect to "accessibility". (Note: requires further testing to confirm) I know that the media-subgroup of the HTML Task Force (of which I am a member) is watching this carefully, and will be vigilant that anything added to HTML5 does not introduce new accessibility barriers.
>
> PLEASE NOTE however that the W3C is not developing a new DRM system, nor are they embracing DRM as an organization. At the same time, the W3C does acknowledge that some in industry demand content protection and that DRM use is currently widespread. (http://www.w3.org/QA/2013/03/drm_and_the_open_web.html) For anyone interested in this topic, there is also a Community Group established at the W3C here: http://www.w3.org/community/restrictedmedia/
>
>
>
> In his question, Bob also speaks of "the acceptable code..."
>
> Any code that works in a browser is "acceptable", including non-conformant and at times "harmful" code (i.e. harmful to accessibility) - it is neither the job nor the mandate of the W3C to act as the internet police. The advantage of having the work done around encrypted media happening at the W3C is two-fold: any 'solution' will be patent and royalty free, and "open" for any browser vendor to implement freely, plus, to become a full W3C Recommendation the Proposal will be given an "accessibility review" by the Protocols and Formats Working Group as part of the Recommendation track.
>
> The alternative of course is that interested parties could go off and develop something 'outside of the reach' of the W3C, get it implemented into one or more browsers, and "we" would be left standing on the sidelines watching; the W3C neither owns nor controls what is on the web today - at best it attempts to steer it towards its full potential, while  at the same time ensure that it can be accessible.
>
> Cheers!
>
> JF
> This transmission may contain information that is privileged,
> confidential, legally privileged, and/or exempt from disclosure
> under applicable law.  If you are not the intended recipient, you
> are hereby notified that any disclosure, copying, distribution, or
> use of the information contained herein (including any reliance
> thereon) is STRICTLY PROHIBITED.  Although this transmission and
> any attachments are believed to be free of any virus or other
> defect that might affect any computer system into which it is
> received and opened, it is the responsibility of the recipient to
> ensure that it is virus free and no responsibility is accepted by
> JPMorgan Chase & Co., its subsidiaries and affiliates, as
> applicable, for any loss or damage arising in any way from its use.
> If you received this transmission in error, please immediately
> contact the sender and destroy the material in its entirety,
> whether in electronic or hard copy format. Thank you.
>
>
Received on Friday, 29 March 2013 18:40:55 UTC

This archive was generated by hypermail 2.3.1 : Friday, 29 March 2013 18:40:55 UTC