- From: Alastair Campbell <acampbell@nomensa.com>
- Date: Wed, 10 Jan 2018 23:19:29 +0000
- To: Andrew Kirkpatrick <akirkpat@adobe.com>, WCAG <w3c-wai-gl@w3.org>
- Message-ID: <VI1PR0901MB092689DD6018B031A91B92B5B9110@VI1PR0901MB0926.eurprd09.prod.outlook.>
+1 Although having missed the call, I’m surprised it wasn’t based on one of the simple ones from WCAG 2.0, e.g: Provide alternatives for device sensor inputs. -Alastair From: Andrew Kirkpatrick Call For Consensus — ends January 12 at 1:30pm Boston time. The Working Group has discussed a change to add a description to the 2.6 Guideline. This was discussed on the call (https://www.w3.org/2018/01/10-ag-minutes.html#item05). The specific changes are detailed in this pull request: https://github.com/w3c/wcag21/pull/633 (see implemented at http://rawgit.com/w3c/wcag21/additional-sensor-inputs-gl/guidelines/index.html#additional-sensor-inputs) 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>
Received on Wednesday, 10 January 2018 23:19:54 UTC