RE: CFC - Response to issues 386, 659, and 660, 669, and 688 on Character Key Shortcuts

-1.
The response to Issue 688 is unsatisfactory. The “a mechanism is available” provision only accommodates situations in which a user agent or assistive technology can turn off or remap single character key shortcuts, not a situation in which the underlying concerns about speech recognition systems are addressed by changes elsewhere in the software infrastructure (e.g., as outlined in the issue). Furthermore, this proposal does place short term burdens on application implementers (e.g., by requiring the introduction of a keyboard configuration option where none exists), which are inappropriately downplayed in the proposed response to this issue.

From: Andrew Kirkpatrick [mailto:akirkpat@adobe.com]
Sent: Monday, January 15, 2018 2:29 AM
To: WCAG <w3c-wai-gl@w3.org>
Subject: CFC - Response to issues 386, 659, and 660, 669, and 688 on Character Key Shortcuts
Importance: High

Call For Consensus — ends Wednesday January 17th at 2:30am Boston time.

The Working Group has discussed responses to the following issues:
386: What do 'character key' and 'printable' mean? (https://github.com/w3c/wcag21/issues/386)
659: Ambiguous definition (https://github.com/w3c/wcag21/issues/659)
660: Characters (https://github.com/w3c/wcag21/issues/660)
669: SC 2.4.11 Character Key Shortcuts - Proposal for change of wording (https://github.com/w3c/wcag21/issues/669)
688: Comment on 2.4.11 (https://github.com/w3c/wcag21/issues/688)

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

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

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

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

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


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

The changed SC can be viewed here: http://rawgit.com/w3c/wcag21/character_changes/guidelines/index.html#character-key-shortcuts


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>



________________________________

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.

________________________________