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

I already +1'ed this.
This is an editorial suggestion. I think it would be cleaner to pull out 
the "unless..." phrase in the preamble and make that wording into a new 
bullet. I do not believe it changes the meaning at all.
If a keyboard shortcut is implemented in content using only letter 
(including upper- and lower-case letters), punctuation, number, or symbol 
characters, then at least one of the following is true:
Turn off
A mechanism is available to turn the shortcut off;
Remap
A mechanism is available to remap the shortcut to use one or more 
non-printable keyboard characters (e.g. Ctrl, Alt, etc).
 Active only on focus
        The keyboard shortcut for a user interface component is only 
active when that component has focus

Michael Gower
IBM Accessibility
Research

1803 Douglas Street, Victoria, BC  V8T 5C3
gowerm@ca.ibm.com
voice: (250) 220-1146 * cel: (250) 661-0098 *  fax: (250) 220-8034



From:   "Michael Gower" <michael.gower@ca.ibm.com>
To:     Andrew Kirkpatrick <akirkpat@adobe.com>
Cc:     WCAG <w3c-wai-gl@w3.org>
Date:   2018-01-18 06:23 PM
Subject:        Re: CFC - Updated Response to issues 386, 659, and 660, 
669, and 688 on   Character Key Shortcuts



+1
Michael Gower
IBM Accessibility
Research

1803 Douglas Street, Victoria, BC  V8T 5C3
gowerm@ca.ibm.com
voice: (250) 220-1146 * cel: (250) 661-0098 *  fax: (250) 220-8034



From:        Andrew Kirkpatrick <akirkpat@adobe.com>
To:        WCAG <w3c-wai-gl@w3.org>
Date:        2018-01-17 04:16 PM
Subject:        CFC - Updated Response to issues 386, 659, and 660, 669, 
and 688 on  Character Key Shortcuts


Call For Consensus — ends Friday January 19th at 7pm 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

 
Since the original CFC, this has been updated to remove the mention of the 
shift key, and to remove the mention of space and enter (see specific 
commit here: 
https://github.com/w3c/wcag21/pull/732/commits/4f7d83ea030329529ede8f0f577abf51a18745a7

)
 
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
http://twitter.com/awkawk