renamed EME accessibility

PS… of course these would need to be exposed after authentication (not
before). And the authentication process should also not inhibit exposure of
form fields etc… to the accessibility API

---------

 

Last week Paul asked our group to review the EME from an accessibility
perspective…  

 

I‘ve skimmed through it… nothing jumps out at me. However, I know nothing
about the internal workings of DRM. As an API, I think the important issues
are to ensure the EME API plays nice with Accessibility APIs.

 

-not preventing players from exposing the AccName and AccDescription of the
play, rewind, etc. buttons to the accessibility API. 

-We want to ensure that closed captioned text is exposed, and 

-that there is no encumbrance to the addition of textual audio description.

 

Is there anything else I missed that we should ensure?

 

Cheers,

David MacDonald

 

CanAdapt Solutions Inc.

Tel:  613.235.4902

 <http://ca.linkedin.com/in/davidmacdonald100>
http://ca.linkedin.com/in/davidmacdonald100

 <http://www.can-adapt.com/> www.Can-Adapt.com

   

  Adapting the web to all users

            Including those with disabilities

nocc

This e-mail originates from CanAdapt Solutions Inc. Any distribution, use or
copying of this e-mail or the information it contains by other than the
intended recipient(s) is unauthorized. If you are not the intended
recipient, please notify me at the telephone number shown above or by return
e-mail and delete this communication and any copy immediately. Thank you.

 

Le présent courriel a été expédié par CanAdapt Solutions Inc. Toute
distribution, utilisation ou reproduction du courriel ou des renseignements
qui s'y trouvent par une personne autre que son destinataire prévu est
interdite. Si vous avez reçu le message par erreur, veuillez m'en aviser par
téléphone (au numéro précité) ou par courriel, puis supprimer sans délai la
version originale de la communication ainsi que toutes ses copies. Je vous
remercie de votre collaboration.

 

From: Steve Faulkner [mailto:faulkner.steve@gmail.com] 
Sent: October 8, 2013 6:29 AM
To: Charles McCathie Nevile
Cc: public-html-a11y@w3.org
Subject: Re: Call for Consensus - decision procedures.

 

+1




--

Regards

SteveF

HTML 5.1 <http://www.w3.org/html/wg/drafts/html/master/> 

 

On 8 October 2013 00:38, Charles McCathie Nevile <chaals@yandex-team.ru>
wrote:

Hi,

We had a call for consensus on this which passed some time ago, but was
rejected by the Protocols and Formats Group.

We therefore have a new proposal for a process to determine consensus, at
<http://www.w3.org/2013/10/07-consensus-procedures.html>

The main changes are
- A CfC should be on the agenda of a teleconference while it is running
- Clarifying that comments in the teleconference are not automatically
taken into account in a CfC, and to ensure they are considered have to be
made in the direct context of the CfC (e.g. email thread)

This is a call for consensus on the proposition

The HTML Accessibility Task Force should adopt the proposed
Decision-making process outlined at
<http://www.w3.org/2013/10/07-consensus-procedures.html>

Replies received before the end of business on Wednesday October 16 will
be considered. Positive response is preferred, but silence is considered
assent.

For the facilitators

Chaals

-- 
Charles McCathie Nevile - Consultant (web standards) CTO Office, Yandex
        chaals@yandex-team.ru         Find more at http://yandex.com