Device Sensors SC

All,

I am the manager for the Device Sensors SC
https://github.com/w3c/wcag21/issues/67

We have had some discussion on github regarding whether this issue can be merged into SC 2.1.1 Keyboard Operability or not.  It is my opinion that this be separate from SC 2.1.1.  While in theory it is possible to merge into SC 2.1.1 in my opinion that would complicate SC 2.1.1 and make both user needs more complicated to sort out.   For example, the test to determine whether something is an exception is different for both.  A keyboard equivalent to geolocation or pedometer sensor could invalidate the activity depending on the content - but the text "path of the users input and not just the endpoints" doesn't really fit.  Changes to SC 2.1.1 for WCAG 2.1 would raise suspicion and confusion and a major change which I believe is needed would ideally be in the next major version of WCAG - not a minor version.  Having this SC is important enough to be in WCAG 2.1 - so in my opinion should be a separate SC.

Feel free to comment on github or on the list and I can make any specific changes or additions as appropriate so that we can get this on the survey list.

Jonathan

Jonathan Avila
Chief Accessibility Officer
SSB BART Group
jon.avila@ssbbartgroup.com<mailto:jon.avila@ssbbartgroup.com>
703.637.8957 (Office)

Visit us online: Website<http://www.ssbbartgroup.com/> | Twitter<https://twitter.com/SSBBARTGroup> | Facebook<https://www.facebook.com/ssbbartgroup> | LinkedIn<https://www.linkedin.com/company/355266?trk=tyah> | Blog<http://www.ssbbartgroup.com/blog/>
See you at CSUN in March!<http://info.ssbbartgroup.com/CSUN-2017_Sessions.html>

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.