Re: Comments on w3ctag/eme/

Well, the answer is: we need to review entire concept of EME/DRM (not existing implementation) and setup architectural requirements for such systems design. We know that there are many DRM systems which don't care about accessibility, so we need a guarantee.

Browsers don't provide speech-recognition functionality right now, that's true. But if we omit such a requirement for DRM/EME systems, then we will be unable to use speech recognition when it actually appears in browser. If IE11 Netflix plugin allows to display HTML content, that's not a guarantee that other DRM/EME systems will allow to do that. These problems originate in the very concept of protected unreadable stream uncontrolled by user. Since accessibility features need an access to that stream to work, the only way to ensure accessibility functionality is to have an explicit requirement (for overall DRM/EME design, in fact) to allow system accessibility services to have a direct access to the DRM-protected content, and that's a technical architecture problem.

22.02.2014, 17:33, "Jeni Tennison" <jeni@jenitennison.com>:
> Sergey,
>
> Do you have any thoughts about Henri’s comments below on the Accessibility section of the draft at
>
>   https://github.com/w3ctag/eme
>
> ? Please feel free to edit the text directly.
>
> Jeni
>
> ------------------------------------------------------
> From: Henri Sivonen hsivonen@hsivonen.fi
> Reply: Henri Sivonen hsivonen@hsivonen.fi
> Date: 19 February 2014 at 05:55:11
> To: www-tag www-tag@w3.org
> Subject:  Comments on w3ctag/eme/
>
> [snip]
>
>>>  DRM systems usually prohibit any manipulations with content
>>  including
>>>  displaying third-party subtitles,
>>  As far as I can tell, nothing in EME itself or in shipped
>>  implementations prevents compositing HTML/CSS content over
>>  a video
>>  than uses EME-involved DRM. In fact, if you use Netflix with IE11
>>  on
>>  Windows 8.1, you'll find that the service *relies* on being able
>>  to
>>  composite HTML/CSS content over EME-involved video frames.
>>>  or (in case of e-books) reading a book using system voice-over
>>  engine,
>>>  thus making a content less accessible by disabled people.
>>  True, but how is this relevant to EME as long as browsers don't
>>  provide client-side speech recognition or computer vision-based
>>  description for DRMless videos?
>
> [snip]
>
> --
> Jeni Tennison
> http://www.jenitennison.com/

--
Konstantinov Sergey
Yandex Maps API Development Team Lead
http://api.yandex.com/maps/

Received on Monday, 24 February 2014 09:16:04 UTC