RE: Draft #1 of TV Remote Control API Comments

Janina, Is someone looking at this from  COGA perspective?

We need 
1.to be able to simplify the interface to 3 - 5 features,
2.change the terms and symbols  to  words and symbols that are familiar to the user and 
3. a input design pattern that the user knows and does not need to learn. 


All the best

Lisa Seeman

LinkedIn, Twitter





---- On Wed, 15 Feb 2017 20:38:49 +0200  White<jjwhite@ets.org> wrote ---- 

 
 
> -----Original Message----- 
> From: Janina Sajka [mailto:janina@rednote.net] 
> The following draft of comments on the TV Remote Control API specification 
> for our consideration previous to a CfC ... 
[Jason] Thank you, Janina, for this draft. I have two questions. 
1. Should we note the potential benefits of this API for enabling accessible Web applications to provide radio and TV services to users with disabilities who may find it difficult or impossible to operate any user interface supplied with the hardware? 
 
2. Has the provision of captions and auditory descriptions been the subject of regulatory interest in the E.U. or elsewhere? I suspect the U.S. may have a lead in this area in so far as it has enacted explicit legislative requirements, which you rightly cite. I nonetheless wonder whether there are corresponding moves elsewhere that should be noted also. I'm not requesting research on the point, but if anyone in APA is aware of other relevant regulatory activities, references would be helpful. 
 
 
________________________________ 
 
This e-mail and any files transmitted with it may contain privileged or confidential information. It is solely for use by the individual for whom it is intended, even if addressed incorrectly. If you received this e-mail in error, please notify the sender; do not disclose, copy, distribute, or take any action in reliance on the contents of this information; and delete it from your system. Any other use of this e-mail is prohibited. 
 
 
Thank you for your compliance. 
 
________________________________