What WCAG 2.1.1 Requires
Every interactive element and all functionality must be operable using only a keyboard, with no requirement for a specific timing of individual keystrokes.
Can AccessBell Test This Automatically?
Yes. AccessBell's scanner runs axe-core, which includes 3 rules that catch code-level failures of this criterion:
frame-focusable-content— Ensure <frame> and <iframe> elements with focusable content do not have tabindex=-1 (details (opens in a new tab))scrollable-region-focusable— Ensure elements that have scrollable content are accessible by keyboard in Safari (details (opens in a new tab))server-side-image-map— Ensure that server-side image maps are not used (details (opens in a new tab))
This criterion is included in: WCAG 2.2 AA Checker, WCAG 2.1 AA Checker, ADA Compliance Checker, Section 508 Checker, EN 301 549 Checker.
How to Test It by Hand
Unplug the mouse and navigate the entire page and every interaction using only Tab, Shift+Tab, Enter, Space and arrow keys.
Common Failures
- A custom dropdown or date picker built with <div> elements has no keyboard handling at all.
- A "click" handler is attached to a non-interactive element with no keyboard equivalent.
Related Criteria in Keyboard Accessible
WCAG 2.1.1 Questions
What does WCAG 2.1.1 require?
Every interactive element and all functionality must be operable using only a keyboard, with no requirement for a specific timing of individual keystrokes.
Can AccessBell test WCAG 2.1.1 automatically?
Yes. AccessBell runs 3 automated rules that can catch failures of this criterion, including in our WCAG 2.2 AA Checker, WCAG 2.1 AA Checker, ADA Compliance Checker, Section 508 Checker, EN 301 549 Checker.
What level is WCAG 2.1.1?
Level A, added in WCAG 2.0.
Sources
- W3C: Understanding 2.1.1 Keyboard (opens in a new tab)
- W3C: Web Content Accessibility Guidelines (WCAG) 2.2 (opens in a new tab)
This page explains a technical standard and is not legal advice. See our disclaimer.