RE: CFC - Device Sensors

I prefer Steve’s note. I can live without it, as the entire proposal is about to be revisited anyway.

Thus, I give a +1 to the CfC, on the understanding that it’s merely a procedural device to allow reconsideration of this proposal after August. I would not support the current text later in the WCAG 2.1 process, due to the difficulties pointed out repeatedly in the working group’s discussion of the proposal.

From: Repsher, Stephen J []
Sent: Thursday, August 31, 2017 12:48 PM
To: Andrew Kirkpatrick <>; WCAG <>
Subject: RE: CFC - Device Sensors

The editor’s note change I proposed to more accurately cover the issues is not reflected here.  It was:

Editors´ Note: The Working Group is aware of issues surrounding both the wide scope of device sensors for this SC and confusion over redundancy with SC 2.1.1.  These are expected to be addressed soon, and draft new wording for review focused on motion actuation is available at<>


From: Andrew Kirkpatrick []
Sent: Thursday, August 31, 2017 12:11 PM
To: WCAG <<>>
Subject: CFC - Device Sensors
Importance: High

Call For Consensus — ends Tuesday September 5th at 12:00pm Boston time.

We received an appeal on a previous decision which we have discussed with proponents and objectors and came up with a plan that minimally revises the SC through the addition of an ednote to the SC and are now running a new CFC to seek the approval of the group.

The Working Group has reviewed and approved a new Success Criteria 'Device Sensors' for inclusion in the editor’s draft, with the goal of obtaining additional input external to the working group.

Call minutes:<>

The new SC can be reviewed here, in the context of the full draft:<>

If you have concerns about this proposed consensus position that have not been discussed already and feel that those concerns result in you “not being able to live with” this decision, please let the group know before the CfC deadline.


Andrew Kirkpatrick
Group Product Manager, Accessibility


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 Thursday, 31 August 2017 16:59:18 UTC