Accessibility

2.1.4 - Character key shortcuts

Benefits users with:

  • Blindness/low vision who use screen reader.
    • It may conflict screen reader’s keyboard shortcut keys.
  • Motor impairments (keyboard-only users).
    • Who may press a shortcut key by mistake and invoke the command without knowing why.
  • Speech input users.
    • To prevent words that are picked up by the microphone from triggering single-key shortcuts.
  • Cognitive disabilities.
    • Who may set up the same shortcuts across different applications.

Intent

The intent of this success crition is to reduce accidental activation of keyboard shortcuts. Character key shortcuts work well for many keyboard users, but are inappropriate and frustrating for speech input users — whose means of input is strings of letters — and for keyboard users who are prone to accidentally hit keys. To rectify this issue, authors need to allow users to turn off or reconfigure shortcuts that are made up of only character keys.

Exception

  • listboxes
  • drop-down

Although these components contain values (words) that may be selected by one or more character keys, the shortcuts are only active when the components have focus.

Other components such as menus may be accessed or opened with a single non-character shortcut (e.g., Alt or Alt+F) before pressing a single character key to select an item. This makes the full path to invoking a menu a two-step shortcut that includes a non-printable key. Accesskeys are also not affected because they include modifier keys.

Ways to meet the criterion

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.

Examples

Not applicable

Alphabet Q activates jumping to a item starting from Q.

Character shortcuts are only active when the dropdown menu has focus.

So that it is not applicable for this success criterion.

Supported general and HTML techniques to meet the criterion:

G17