WCAG 2.2 success criterion 2.1.1, Keyboard, is a Level A requirement. In practice: all functionality is available from a keyboard; and scrollable regions and frames can be reached from the keyboard.
Read the criterion in the W3C Recommendation, WCAG 2.2 (opens in a new tab).
How BearScan checks it
All functionality is available from a keyboard
Checked automatically: clicks through the page. Severity: blocker. Without keyboard access a motor-impairment user cannot complete the task at all. This is the most commonly cited defect in web accessibility litigation.
An approximation: A browser presses Tab through the page and lists every element that looks operable (an ARIA widget role, an inline click handler, or a pointer cursor with nothing focusable inside) that Tab never reaches. It does not press Enter or Space on controls, since that would submit forms and follow links, so a control that takes focus but ignores the keyboard is not found, nor is one wired only by a script listener on a plain element with no role or pointer cursor.
How to fix it. Make every interactive element reachable and operable with Tab, Shift+Tab, Enter, Space, and the arrow keys. Prefer native controls over custom widgets, and where a custom widget is unavoidable, implement the expected keyboard pattern.
Scrollable regions and frames can be reached from the keyboard
Checked automatically: loads the page in a browser. Severity: high. Content inside a scroll box or frame that cannot take focus is unreachable for a keyboard user; it is on the page but cannot be read or operated.
An approximation: Delegated to axe-core's rules tagged for 2.1.1 (scrollable-region-focusable, frame-focusable-content, server-side-image-map). They find structural keyboard barriers; whether every control actually responds to the keyboard stays with the manual 2.1.1 test.
How to fix it. Give a scrollable region tabindex="0" and an accessible name, do not set tabindex="-1" on frames that contain controls, and replace server-side image maps with links.
Legal basis
- 28 CFR § 35.200(b) (opens in a new tab) (US (state and local government)). Incorporates WCAG 2.1 AA by reference. Compliance dates extended to April 26, 2027 (population 50,000+) and April 26, 2028 by the interim final rule at 91 FR 20902.
- 42 U.S.C. § 12182(b)(2)(A)(ii) (opens in a new tab) (US). Title III effective communication and reasonable modification duties. Survives any technical conformance claim.
All WCAG 2.2 criteria · Next: 2.1.2 No Keyboard Trap
Questions
Is WCAG 2.1.1 required by the ADA?
The ADA doesn't name a technical standard for businesses, but the Justice Department's 2022 guidance points businesses to WCAG, and its 2024 rule for state and local governments adopted WCAG 2.1 Level AA, which includes 2.1.1.
Can an automated tool check WCAG 2.1.1?
Mostly. BearScan checks it automatically (clicks through the page, loads the page in a browser). A clean result still isn't proof every page passes, only the pages scanned.
How do I fix a WCAG 2.1.1 failure?
Make every interactive element reachable and operable with Tab, Shift+Tab, Enter, Space, and the arrow keys. Prefer native controls over custom widgets, and where a custom widget is unavoidable, implement the expected keyboard pattern.