W3C home > Mailing lists > Public > public-apa@w3.org > February 2017

RE: Draft #1 of TV Remote Control API Comments

From: lisa.seeman <lisa.seeman@zoho.com>
Date: Wed, 15 Feb 2017 21:25:17 +0200
To: White <jjwhite@ets.org>
Cc: "Janina Sajka" <janina@rednote.net>, "W3C WAI Accessible Platform Architectures" <public-apa@w3.org>
Message-Id: <15a433a8d60.d65ff0f38686.6835738196125647892@zoho.com>
But does itA, identify what features are critical and 
b, identify standard concepts  such as on/off  higher/lower etc) so that they can be adapted to the user?I assume that there is  data binding so that user inteface can change.

All the best

Lisa Seeman

LinkedIn, Twitter

---- On Wed, 15 Feb 2017 20:57:11 +0200  White&lt;jjwhite@ets.org&gt; wrote ---- 

   From: lisa.seeman [mailto:lisa.seeman@zoho.com] 
 Sent: Wednesday, February 15, 2017 1:49 PM
  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.
 [Jason] One of the advantages of having an API is that you can implement a custom user interface (i.e., a simple Web application) that uses it to make the underlying functionality highly accessible to people with very specific needs. The API does not constrain the user interface.
  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.
Received on Wednesday, 15 February 2017 19:25:47 UTC

This archive was generated by hypermail 2.4.0 : Thursday, 24 March 2022 20:23:02 UTC