Re: CFC - Concurrent Input Mechanisms SC

AGWG’ers,

As we have received only positive feedback leading up to this CfC and no responses indicating that group members could not live this this decision, this CfC is agreed on as a consensus opinion of the working group.

This decision will be recorded at https://www.w3.org/WAI/GL/wiki/Decisions<https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.w3.org%2FWAI%2FGL%2Fwiki%2FDecisions&data=02%7C01%7C%7C1ab6006ec2be48e88f9008d4a210961e%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636311639507586899&sdata=IafGoKjeQf7zBqxVj8m380hh8%2BWgU1VfPa2tZjq0Bx8%3D&reserved=0>

Thanks,
AWK

Andrew Kirkpatrick
Group Product Manager, Accessibility
Adobe

akirkpat@adobe.com<mailto:akirkpat@adobe.com>
http://twitter.com/awkawk



From: Andrew Kirkpatrick <akirkpat@adobe.com>
Date: Tuesday, November 21, 2017 at 09:32
To: WCAG <w3c-wai-gl@w3.org>
Subject: CFC - Concurrent Input Mechanisms SC
Resent-From: WCAG <w3c-wai-gl@w3.org>
Resent-Date: Tuesday, November 21, 2017 at 09:26

Call For Consensus — ends Friday November 24th at 9:30am Boston time.

The Working Group discussed a change to the Concurrent Input Mechanism SC at TPAC.

The current SC text in the Working Draft remains the same, but the discussion at TPAC (https://www.w3.org/2017/11/07-ag-minutes.html#item05)<https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.w3.org%2F2017%2F11%2F07-ag-minutes.html%23item05)&data=02%7C01%7C%7C4b1e4e453727415265ca08d530ecb91d%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636468715646036088&sdata=PXU4pet%2BHRb2XD9ffnHEJ6DH3TyjhRqHrQJv8NaFqP4%3D&reserved=0> led the WG to the conclusion that this SC should be at AAA.

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.

Thanks,
AWK

Andrew Kirkpatrick
Group Product Manager, Accessibility
Adobe

akirkpat@adobe.com<mailto:akirkpat@adobe.com>
http://twitter.com/awkawk<https://na01.safelinks.protection.outlook.com/?url=http%3A%2F%2Ftwitter.com%2Fawkawk&data=02%7C01%7C%7C54093524ef264326424008d51cd66c05%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636446629619786436&sdata=c5UP0xiniJIppvd6Esu1XA%2FbX1ykpABkhgCCmBp%2Fht8%3D&reserved=0>