WCAG 2.1.4 — Character Key Shortcuts

Who Is Affected

Users of voice control software (like Dragon NaturallySpeaking), users with mobility impairments who rely on alternative keyboards, and users with motor disabilities who may accidentally press single keys.

What This Means

Single-character keyboard shortcuts (like pressing "s" to search) can conflict with assistive technology. When someone using voice control software says a word containing that letter, it may accidentally trigger the website's shortcut instead of typing the intended text.

For example, if your site uses the "s" key as a search shortcut, a voice control user saying "search" or "submit" might inadvertently activate the search function multiple times instead of dictating those words.

The solution is to either use multi-key combinations (like Ctrl+S) or provide a way for users to turn off single-key shortcuts.

Fix: CMS / Theme

Review your theme and any installed plugins for single-character keyboard shortcuts:

Joomla

1. Go to Extensions → Plugins and search for "keyboard" or "shortcut"
2. Check the configuration of any keyboard-related plugins
3. Look for options to:
   • Require modifier keys (Ctrl, Alt, Shift) with single characters
   • Disable shortcuts entirely
   • Allow users to customize shortcuts
4. In your template's JavaScript files, search for keydown, keypress, or keyup event listeners
5. Modify any single-character shortcuts to require modifier keys

WordPress

1. Go to Plugins → Installed Plugins and review any that mention "keyboard," "shortcut," or "hotkey"
2. Check plugin settings for shortcut configuration options
3. Common plugins with shortcuts: search plugins, accessibility plugins, admin enhancement tools
4. In your theme's functions.php or JavaScript files, look for keyboard event handlers
5. Update single-character shortcuts to use combinations like Ctrl+key

Code Example:

// Instead of this:
document.addEventListener('keydown', function(e) {
  if (e.key === 's') { // Single key - problematic
    openSearch();
  }
});

// Use this:
document.addEventListener('keydown', function(e) {
  if (e.ctrlKey && e.key === 's') { // Ctrl+S - accessible
    e.preventDefault();
    openSearch();
  }
});

Fix: Content Editor

Most content editors don't directly create keyboard shortcuts, but you may encounter them in:

1. Embedded widgets or third-party tools — Check if any embedded content (maps, forms, media players) uses single-key shortcuts
2. Custom HTML/JavaScript blocks — Review any custom code blocks for keyboard event handlers
3. Plugin shortcodes — Some plugins add keyboard functionality through shortcodes

If you find single-character shortcuts in your content, either:

• Remove the problematic code
• Contact your web developer to modify it to use key combinations
• Replace with an accessible alternative

Standard Reference

WCAG 2.1 Success Criterion 2.1.4 — Character Key Shortcuts, Level A

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

• W3C Understanding SC 2.1.4

• WCAG Technique G217 — Providing a mechanism to allow users to remap or turn off character key shortcuts

• WCAG Failure F99 — Failure due to implementing character key shortcuts that cannot be turned off or remapped