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

Re: 48-Hour Call for Consensus (CfC): TV Remote Control API Comments

From: Janina Sajka <janina@rednote.net>
Date: Wed, 22 Feb 2017 11:53:43 -0500
To: "lisa.seeman" <lisa.seeman@zoho.com>
Cc: Accessible Platform Architectures Administration <public-apa-admin@w3.org>
Message-ID: <20170222165343.GB2581@opera.rednote.net>
OK, Lisa. Please come on a call so we can discuss.

Lisa Seeman writes:
> Hi Janinathat is not the use case i want
> 
> 
> I want the API to include a place to say the common role/concept of a control. 
> For example - higher and lower
> 
> 
> I also want for there to be a way to identify the 2 - 5 most critical features 
> 
> 
> then AT THE USER END an application can simplify or adapt the interface to make it understandable to coga usegroups
> 
> 
> I see this as absolutely crucial 
> 
> All the best
> 
> Lisa Seeman
> 
> LinkedIn, Twitter
> 
> 
> 
> 
> 
> ---- On Wed, 22 Feb 2017 16:35:53 +0200 Janina Sajka&lt;janina@rednote.net&gt; wrote ---- 
> 
> Hi, Lisa: 
>  
> I'm befuddled trying to understand your point. Please help me out here. 
>  
> Is the following correct? 
>  
> You want to represent the concept of adjusting audio volume higher or 
> lower using some kind of symbology that doesn't use the very common 
> English remote control term: "Volume Control." I think I can understand 
> how there would be use cases for representing that concept differently. 
> For one thing it would need to be represented in the world's various 
> languages. 
>  
> Assuming the above is correct, I still don't see how that becomes a 
> comment on the API. It's not the role of the API to provide alternative 
> dictionaries of terms and symbols. Rather, it's the role of Volume 
> Control in this API to allow for audio volume to be raised or lowered by 
> some kind of user agent, in our case likely software associated with a 
> browser (or using browser technology) inasmuch as we're talking about 
> the www. 
>  
> If you want to get into how these concepts are standardized across 
> different symbol systems, I should probably point you to ISO where they 
> do exactly those kinds of standards for hardware devices. 
>  
>  
> So, what am I missing here? 
>  
> Janina 
>  
>  
> Lisa Seeman writes: 
> &gt; Hi JaninaI might be missing something but I can not see how we can adapt something like volume control or temperature control and give it a symbol or text that the user understands. 
> &gt; In other words i do not see that COGA's needs are met. Until then people will need assisted living or live in help much earlier then they would otherwise becauseof these gaps. 
> &gt; 
> &gt; 
> &gt; Can you explain that use case if I am missing it? 
> &gt; 
> &gt; 
> &gt; All the best 
> &gt; 
> &gt; Lisa Seeman 
> &gt; 
> &gt; LinkedIn, Twitter 
> &gt; 
> &gt; 
> &gt; 
> &gt; 
> &gt; 
> &gt; ---- On Tue, 21 Feb 2017 16:16:43 +0200 Janina Sajka&amp;lt;janina@rednote.net&amp;gt; wrote ---- 
> &gt; 
> &gt; Colleagues: 
> &gt; 
> &gt; This is a Call for Consensus (CfC) to the Accessible Platform 
> &gt; Architectures (APA) Working Group on our review of the TV Remote Control 
> &gt; API specification as detailed below. 
> &gt; 
> &gt; I have endeavored to incorporate such API related comments as we've 
> &gt; recieved on an earlier draft comment beginning at: 
> &gt; 
> &gt; http://lists.w3.org/Archives/Public/public-apa/2017Feb/0019.html 
> &gt; 
> &gt; &amp;lt;Begin Draft Comment&amp;gt; 
> &gt; 
> &gt; The Accessible Platform Architectures (APA) Working Group makes the 
> &gt; following comments on the draft TV Control API specification at: 
> &gt; 
> &gt; https://www.w3.org/tr/tvcontrol-api/ 
> &gt; 
> &gt; We appreciate that an API for TV remote control could be utilized for 
> &gt; enabling accessible alternative Web applications to provide radio and TV 
> &gt; services to users with disabilities who may find it difficult or 
> &gt; impossible to operate any user interface supplied with a particular 
> &gt; hardware device. This is an inherent accessibility strength for any API 
> &gt; that provides for sufficient feature support. Regretably, we believe the 
> &gt; current TV Remote Control API as currently defined lacks required 
> &gt; accessibility feature support. 
> &gt; 
> &gt; * alternative media support 
> &gt; 
> &gt; We would draw your attention to the multiple alternative media formats 
> &gt; that are used by persons with disabilities as set forth in our W3C Note 
> &gt; publication: "Media Accessibility User Requirements (MAUR)" available 
> &gt; at: 
> &gt; 
> &gt; http://www.w3.org/TR/media-accessibility-reqs 
> &gt; 
> &gt; Our reading of the Tv Control API draft finds no way for users to learn 
> &gt; of the presence of any MAUR identified alternative media with any 
> &gt; particular TV content, nor any means to request display of alternative 
> &gt; content. This is a fundamental accessibility requirement on TV Controls 
> &gt; and we believe it must be factored into this specification. 
> &gt; 
> &gt; * Alternative Media on Second Screen Devices 
> &gt; 
> &gt; APA's predecessor Working Group, Protocols and Formats WG provided use 
> &gt; cases and requirements to the Second Screen Working Group on how 
> &gt; alternative media might be directed to second screen devices. We believe 
> &gt; support for directing alternative video, audio, and/or text to secondary 
> &gt; devices, as described in the MAUR, is a fundamental accessibility 
> &gt; requirement on TV Controls and should be supported in this API. 
> &gt; 
> &gt; * Legal Requirements 
> &gt; 
> &gt; The Federal Communications Commission (FCC) in the U.S. has explicit 
> &gt; requirements on how alternative media are to be exposed to consumers. 
> &gt; Developers should be flagged most especially on the requirement that 
> &gt; captioning must be enableable by top level controls. These FCC 
> &gt; requirements implement provisions of a U.S. law known as the 
> &gt; "Twenty-First Century Communications and Video Accessibility Act" as 
> &gt; explained by the FCC at: 
> &gt; 
> &gt; https://www.fcc.gov/general/twenty-first-century-communications-and-video-accessibility-act-0#block-menu-block-4 
> &gt; 
> &gt; The FCC's regulations pertinent to this specification were published in 
> &gt; December 2016 in the document: "Accessibility Requirements for 
> &gt; Television and Set-Top Box Controls, Menus, and Program Guides" 
> &gt; available at: 
> &gt; 
> &gt; PDF: https://apps.fcc.gov/edocs_public/attachmatch/DA-16-1416A1.pdf 
> &gt; MS-Word: https://apps.fcc.gov/edocs_public/attachmatch/DA-16-1416A1.docx 
> &gt; 
> &gt; Also relevant is the document "Display of Captioning on Equipment Used 
> &gt; to View Video Programming" available at: 
> &gt; 
> &gt; https://www.fcc.gov/consumers/guides/closed-captioning-display-requirements-equipment#block-menu-block-4 
> &gt; 
> &gt; &amp;lt;End Draft Comment&amp;gt; 
> &gt; 
> &gt; * ACTION TO TAKE 
> &gt; 
> &gt; This CfC is now open for objection, comment, as well as statements of 
> &gt; support via email. Silence will be interpreted as support, though 
> &gt; messages of support are certainly welcome. 
> &gt; 
> &gt; If you object to this proposed action, or have comments concerning this 
> &gt; proposal, please respond by replying on list to this message no later 
> &gt; than 23:59 (Midnight) Boston Time, Tuesday 28 February. 
> &gt; 
> &gt; Janina 
> &gt; 
> &gt; 
> &gt; -- 
> &gt; 
> &gt; Janina Sajka, Phone: +1.443.300.2200 
> &gt; sip:janina@asterisk.rednote.net 
> &gt; Email: janina@rednote.net 
> &gt; 
> &gt; Linux Foundation Fellow 
> &gt; Executive Chair, Accessibility Workgroup: http://a11y.org 
> &gt; 
> &gt; The World Wide Web Consortium (W3C), Web Accessibility Initiative (WAI) 
> &gt; Chair, Accessible Platform Architectures http://www.w3.org/wai/apa 
> &gt; 
> &gt; 
> &gt; 
> &gt; 
> &gt; 
> &gt; 
> &gt; 
> &gt; 
>  
> -- 
>  
> Janina Sajka,    Phone:    +1.443.300.2200 
>             sip:janina@asterisk.rednote.net 
>         Email:    janina@rednote.net 
>  
> Linux Foundation Fellow 
> Executive Chair, Accessibility Workgroup:    http://a11y.org 
>  
> The World Wide Web Consortium (W3C), Web Accessibility Initiative (WAI) 
> Chair, Accessible Platform Architectures    http://www.w3.org/wai/apa 
>  
> 
> 
> 
> 
> 
> 

-- 

Janina Sajka,	Phone:	+1.443.300.2200
			sip:janina@asterisk.rednote.net
		Email:	janina@rednote.net

Linux Foundation Fellow
Executive Chair, Accessibility Workgroup:	http://a11y.org

The World Wide Web Consortium (W3C), Web Accessibility Initiative (WAI)
Chair, Accessible Platform Architectures	http://www.w3.org/wai/apa
Received on Wednesday, 22 February 2017 16:54:13 UTC

This archive was generated by hypermail 2.3.1 : Wednesday, 22 February 2017 16:54:13 UTC