Loading...
Loading content...
Loading content...
Single-key shortcuts must be turn-off-able or remappable.
Why it matters: Prevents accidental activation of shortcuts by speech input users or prone typists.
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: (Level A) 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); Active only on focus: The keyboard shortcut for a user interface component is only active when that component has focus.
What This Means: This success criterion addresses keyboard shortcuts that use only printable characters (letters, numbers, punctuation, symbols). If such shortcuts are implemented, at least one of the following must be true: (1) Users can turn the shortcut off, (2) Users can remap the shortcut to use modifier keys (like Ctrl or Alt), or (3) The shortcut is only active when the component has focus.
Why It's Important: Single-character shortcuts can conflict with speech recognition software, which types characters as users speak. They can also be accidentally activated by users with motor disabilities who may press keys unintentionally. By requiring shortcuts to be turn-off-able, remappable, or only active on focus, we prevent accidental activations while still allowing power users to benefit from shortcuts.
If you implement single-character shortcuts (like 's' for save, 'n' for next), provide a way for users to disable them, allow remapping to include modifier keys (like Ctrl+S), or ensure shortcuts only work when the relevant component has focus. This prevents conflicts with assistive technologies and accidental activations.
This criterion ensures that speech recognition users can access and understand the content, improving their overall experience and ability to use the website effectively.
This criterion ensures that users with motor disabilities can access and understand the content, improving their overall experience and ability to use the website effectively.
Impact: When this criterion is properly implemented, it removes barriers for these user groups and creates a more inclusive web experience for everyone.
This success criterion benefits the following user groups:
Tip: Use this checklist during development and testing to ensure all requirements for 2.1.4 Character Key Shortcuts are met. Check off items as you complete them.
Note: These are official W3C resources for 2.1.4. For the most up-to-date information and detailed technical guidance, always refer to the official W3C documentation.
Implementing 2.1.4 Character Key Shortcuts correctly requires understanding your specific context. Code solutions vary significantly based on multiple factors:
HTML, React, Vue, Angular, PHP, Python, and other frameworks each have different patterns and best practices.
Server-side rendering, client-side rendering, static generation, and hybrid approaches require different solutions.
Your existing components, styling approach, and UI library influence how accessibility must be implemented.
Your specific user base, content type, and interaction patterns determine the most appropriate implementation.
We provide tailored implementation guidance by analyzing your specific technology stack, coding patterns, design system, and project requirements. Our team reviews your codebase and provides custom solutions that integrate seamlessly with your existing architecture.
Get Custom Implementation HelpPart of
Operable PrincipleGuideline
2.1 Keyboard Accessible