All Functions Accessible via Keyboard Only
What this criterion checks
This criterion maps to 2.1.1 Keyboard. A detailed plain-language description is maintained in the WebLens criteria catalogue; the WCAG sub-test breakdown below describes exactly what the agent checks and what it does not.
How it's assessed
WebLens walks each user journey, captures a screenshot at every step, and an agent reasons over that evidence. See the how WebLens works for the full pipeline and the deterministic checks layered in for accessibility.
Sub-test coverage
2.1.1 Keyboard is broken into 3 sub-tests. Coverage is honest about where the agent is reliable, where it only partially checks the requirement, and where a human reviewer is still needed.
1 partial2 not covered
- All interactive elements are keyboard operablePartial
Our tool detects three specific keyboard accessibility issues: iframes with tabindex="-1" that block keyboard access to focusable content inside them, scrollable regions without keyboard-focusable elements (preventing keyboard scrolling), and server-side image maps that require mouse clicks. However, it does not comprehensively verify that all interactive elements (custom widgets, JavaScript-powered controls, drag-and-drop interfaces) are keyboard operable.
- No specific timing required for keystrokesNot covered
Detecting whether interactive elements require specific keystroke timing (e.g., double-tap within a time window) requires manual testing of each control. Not automatable.
- Path-dependent exception verificationNot covered
Determining whether non-keyboard-operable functionality genuinely requires path-dependent input (e.g., freehand drawing vs. reorderable drag-and-drop) requires human judgment. Not automatable.
How reliable it is
This criterion is currently scoring below its expected accuracy range, so confirm each finding before acting on it. See Accuracy & confidence for how the confidence tags are set.