CFC - Responses to issues 620, 621, and 676 on user motion

Call For Consensus — ends Tuesday January 16th at 11:59pm Boston time.

The Working Group has discussed responses to the following issues:
620: Success Criterion 2.6.1 Motion Actuation - SC includes user motion, but understanding document does not (https://github.com/w3c/wcag21/issues/620)
621: Success Criterion 2.6.1 Motion Actuation: Consider separating device motion and user motion into two SC to make guidance easier to understand and to prepare for future SC under 2.6 (https://github.com/w3c/wcag21/issues/621)
676: "Accessibility Supported" - SC 2.6.1 Motion Actuation (https://github.com/w3c/wcag21/issues/676)

Response to Issue 620: https://www.w3.org/WAI/GL/wiki/Draft_Responses_to_Dec_WD_Issues#620

Response to Issue 621: https://www.w3.org/WAI/GL/wiki/Draft_Responses_to_Dec_WD_Issues#621

Response to Issue 676: https://www.w3.org/WAI/GL/wiki/Draft_Responses_to_Dec_WD_Issues#676


The changes to the SC are implemented in this pull request: https://github.com/w3c/wcag21/pull/681

The changed SC can be viewed here: http://rawgit.com/w3c/wcag21/motionimprovements/guidelines/index.html#motion-actuation


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>