W3C home > Mailing lists > Public > w3c-wai-gl@w3.org > January to March 2018

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

From: Michael Gower <michael.gower@ca.ibm.com>
Date: Mon, 15 Jan 2018 11:56:15 -0800
To: Andrew Kirkpatrick <akirkpat@adobe.com>
Cc: WCAG <w3c-wai-gl@w3.org>
Message-Id: <OF5A4FAFAB.0D585F24-ON88258216.006B98BE-88258216.006D7CCD@notes.na.collabserv.com>
I'm concerned with the rewording of Remap, both the addition of "or the 
Space or Enter keys" and the wording "to use". 

 It is now proposed to read:

<dd>A mechanism is available to remap the shortcut to use one or more 
non-printable keyboard characters (e.g. Ctrl, Alt, Shift, etc.) or the 
Space or Enter keys.</dd> 

In the original wording, Space and Enter were excepted from counting as 
character keys. That has now been altered to state that authors can use 
Space and Enter to replace author-created shortcuts. However, Space and 
Enter tend to be assigned by the user agent for specific activations. We 
should not be encouraging their use for remapping purposes, especially 
without the use of a modifier key. This will potentially lead to exactly 
the same issues with Speech operation that the SC was attempting to 

The concerns that were raised by the definition of character key seem to 
have been addressed by replacing 'character keys' with the phrase "using 
only letter (including upper- and lower-case letters), punctuation, 
number, or symbol characters ", which does not include Space or Enter. So 
it does not seem neccesary to later specify them in the remap definition. 
I would advocate that "or the Space or Enter keys" be removed.

As well, the rewording infers that justa modifier key can now be used. I 
think this can be overcome by changing "use" to "include". The resulting 
Remap's definition would read:

A mechanism is available to remap the shortcut to include use one or more 
non-printable keyboard characters (e.g. Ctrl, Alt, Shift, etc.).

Michael Gower
IBM Accessibility

1803 Douglas Street, Victoria, BC  V8T 5C3
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-14 11:30 PM
Subject:        CFC - Response to issues 386, 659, and 660, 669, and 688 
on Character  Key Shortcuts

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? (
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 (
688: Comment on 2.4.11 (https://github.com/w3c/wcag21/issues/688)
Response to Issue 386: 

Response to Issue 659: 

Response to Issue 660: 

Response to Issue 669: 

Response to Issue 688: 

The changes to the SC are implemented in this pull request: 

The changed SC can be viewed here: 

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.
Andrew Kirkpatrick
Group Product Manager, Accessibility


Received on Monday, 15 January 2018 19:57:04 UTC

This archive was generated by hypermail 2.4.0 : Thursday, 24 March 2022 21:08:21 UTC