- From: Andrew Kirkpatrick <akirkpat@adobe.com>
- Date: Thu, 4 Jan 2018 23:11:34 +0000
- To: WCAG <w3c-wai-gl@w3.org>
- Message-ID: <36487303-BD4F-45BB-9224-29514E3EB1F9@adobe.com>
Thinking about changing this SC (2.4.11) in response to three comments. I have the current and proposed versions below, and a key question: 1. Do we need to have the space and enter keys work as “non-character” keys for any particular reason? My proposal assumes not, but we can change it if needed. CURRENT: Success Criterion 2.4.11 Character Key Shortcuts If a keyboard shortcut consisting entirely of one or more character keys is implemented in content, then a mechanism is available to turn it off or to remap it to a shortcut that can use at least one non-character key, unless the keyboard shortcut for a user interface component is only active when that component has focus. Character key is defined as: single printable Unicode code point, any keyboard character that is printable, i.e. letters of the alphabet including capitals, punctuation, numbers, and symbols Note: that the Space and Enter keys, which return empty spaces rather than characters, are not character keys. PROPOSED: Success Criterion 2.4.11 Character Key Shortcuts If a keyboard shortcut does not include a modifier key is implemented in content, then a mechanism is available to turn it off or to remap it to a shortcut that can use at least one modifier key, unless the keyboard shortcut for a user interface component is only active when that component has focus. Control key is defined as: single non-printable Unicode code point or any keyboard character that is not printable, i.e. including alt, control, home, and end, and excluding printable characters including letters, punctuation, numbers, and symbols. Thoughts? Thanks, AWK Andrew Kirkpatrick Group Product Manager, Accessibility Adobe akirkpat@adobe.com http://twitter.com/awkawk
Received on Thursday, 4 January 2018 23:12:02 UTC