WCAG (Level A) SC 2.1.4 Character Key Shortcuts (w3.org)
Issue description
WCAG 2.1.4, “Character Key Shortcuts” aims to prevent unexpected behavior or changes in context when users type single letters or characters while navigating a web page using the keyboard. This is important because:
- Accidental activation: Users who rely on the keyboard for navigation might accidentally trigger actions or change the context of the page if single keystrokes are used as shortcuts.
- Disruption and confusion: Unexpected changes can be disorienting and interrupt the user’s workflow, especially for people with cognitive disabilities.
- Interference with assistive technologies: Single-letter shortcuts can interfere with assistive technologies, making it difficult for users to interact with the page or enter text.
Some websites use single-letter keystrokes as shortcuts for actions or navigation. For example:
- Jumping to sections: Pressing “J” might jump the user to a different section of the page.
- Triggering actions: Pressing “D” might delete an item or submit a form.
- Changing settings: Pressing “F” might toggle a feature on or off.
WCAG requirements
This guideline requires that if a single-letter keystroke causes an action or change of context, it must meet one of the following conditions:
- Turn off: The user can turn off the shortcut.
- Remap: The user can remap the shortcut to a different key combination.
- Active only during certain states: The shortcut is only active when a component that uses it has focus.
Essentially, this guideline ensures that users have control over how single-letter keystrokes are interpreted by the website. It prevents unexpected behavior and provides a more predictable and accessible experience for keyboard users.
Related requirements
The following WCAG source criteria are often related to this as well. They can provide additional insights into specific challenges you may be encountering.
- WCAG (Level A) SC 2.1.1 Keyboard
- WCAG (Level A) SC 2.1.2 No Keyboard Trap
- WCAG (Level AAA) SC 2.1.3 Keyboard (No Exception)
Who this issue impacts
Follow the links for additional information on user impairments:
Suggestions for remediation
Remediating WCAG 2.1.4, “Character Key Shortcuts” involves ensuring that users have control over any single-letter keystrokes that trigger actions or change context within your website. Here’s how:
Provide mechanisms to turn off or remap shortcuts
- Settings or preferences: Offer users a way to turn off character key shortcuts completely or remap them to different key combinations. This can be done through a dedicated settings page or user preferences section.
- User interface: Provide clear controls within the user interface to disable or remap specific shortcuts.
Limit shortcut activation
- Contextual activation: Ensure that character key shortcuts are only active when the relevant component has focus. For example, a shortcut to delete an item in a list should only be active when an item in the list is selected.
- Focus indicators: Provide clear visual indicators to show when a component has focus, so users are aware of which shortcuts are active.
Use modifier keys
- Combine with modifier keys: Whenever possible, use modifier keys (e.g., Ctrl, Alt, Shift) in combination with character keys for shortcuts. This reduces the risk of accidental activation.
Provide clear instructions
- Documentation: Clearly document all character key shortcuts and how to turn them off or remap them.
- On-screen prompts: Provide on-screen prompts or tooltips to inform users about available shortcuts and how to modify them.
Testing
- Keyboard-only testing: Test the website using only the keyboard to identify any unexpected behavior caused by single-letter keystrokes.
- Assistive technology testing: Test with screen readers to ensure that character key shortcuts do not interfere with the user’s ability to navigate or interact with the content.
Example
If your website uses the “S” key to save a document, you can:
- Provide a setting to disable it: Offer a checkbox in the user preferences to “Disable single-key shortcuts.”
- Use a modifier key: Change the shortcut to Ctrl+S, which is a more common and less error-prone combination.
- Limit activation: Make the “S” key shortcut active only when the document editing area has focus.
By implementing these techniques, you can prevent accidental activation of character key shortcuts, provide users with control over their keyboard interactions, and create a more predictable and accessible experience for everyone.
