W3C home > Mailing lists > Public > w3c-wai-gl@w3.org > July to September 2017

RE: CFC - Device Sensors

From: Jonathan Avila <jon.avila@levelaccess.com>
Date: Mon, 28 Aug 2017 16:32:54 +0000
To: "Patrick H. Lauke" <redux@splintered.co.uk>, "w3c-wai-gl@w3.org" <w3c-wai-gl@w3.org>
Message-ID: <CY1PR0301MB2090BEA88D4F96D73CD4A387F19E0@CY1PR0301MB2090.namprd03.prod.outlook.com>
Again the exception for 2.1.1 would also need to be updated -- another reason why we added this newly proposed SC --- from 2.1.1   "except where the underlying function requires input that depends on the path of the user's movement and not just the endpoints." 

This doesn't quite fit the exceptions that might be needed for all of the sensors we have today and the exception might allow things through which could be done other ways like wayfinding -- moving a gps through a virtual map to play a game.  

Additionally, without some sort of note it's not obvious that 2.1.1 does cover device sensors -- and so at the very least an editorial note needs to be made communicating this.


Jonathan Avila
Chief Accessibility Officer
Level Access, inc. (formerly SSB BART Group, inc.)
(703) 637-8957
Visit us online: Website | Twitter | Facebook | LinkedIn | Blog
Looking to boost your accessibility knowledge? Check out our free webinars!

The information contained in this transmission may be attorney privileged and/or confidential information intended for the use of the individual or entity named above. If the reader of this message is not the intended recipient, you are hereby notified that any use, dissemination, distribution or copying of this communication is strictly prohibited.

-----Original Message-----
From: White, Jason J [mailto:jjwhite@ets.org] 
Sent: Monday, August 28, 2017 12:12 PM
To: Patrick H. Lauke <redux@splintered.co.uk>; w3c-wai-gl@w3.org
Subject: RE: CFC - Device Sensors

> -----Original Message-----
> From: Patrick H. Lauke [mailto:redux@splintered.co.uk] Phones/tablets 
> have no keyboard interface - while they offer on-screen keyboards, 
> these appear only in specific situations (generally, when the user is 
> focused on an editable field), so they don't allow the user to 
> arbitrarily press a key. For this reason, something that nominally 
> passes 2.1.1  may still not work on these devices. This is the gap 
> that the proposed SC Pointer was going to try and address
[Jason] And the current proposal doesn't address it. If I remember meeting discussions correctly, we decided to postpone writing a proposal that requires user interface components to be operable by devices other than keyboards until after the completion of WCAG 2.1, due to the complexity of the issue. I would be glad to support such a proposal, but the working group's decisions regarding the WCAG 2.1 process don't appear to allow it until after 2.1.


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 Monday, 28 August 2017 16:33:19 UTC

This archive was generated by hypermail 2.4.0 : Thursday, 24 March 2022 21:08:16 UTC