WCAG 2.1.1: Keyboard

All functionality must be operable through a keyboard interface without requiring specific timings for individual keystrokes.

Operable Level A Critical Impact

Check if your website passes WCAG 2.1.1

Common Failures

Custom dropdowns not keyboard-accessible, click-only interactions, hover-only content reveals, keyboard traps in modals.

How to Fix

Ensure all interactive elements are focusable and operable via keyboard. Use proper HTML elements (button, a) instead of div/span for interactive elements.

How EAAPass Tests WCAG 2.1.1

EAAPass automatically tests WCAG 2.1.1 (Keyboard) using three engines simultaneously:

axe-core — Checks DOM elements against the 2.1.1 rule set
Google Lighthouse — Validates accessibility in the context of overall page quality
Pa11y — HTML_CodeSniffer integration for WCAG-specific testing
AI Validation — Claude AI reviews ambiguous results to eliminate false positives

Results are mapped to the Operable POUR principle and scored based on severity and frequency.

Industries Most Affected by WCAG 2.1.1

Banking & Financial Services Government & Public Sector Travel & Hospitality SaaS & Software Platforms Insurance Real Estate & Property

Other WCAG 2.1 AA Criteria

WCAG 1.1.1 Non-text Content Perceivable WCAG 1.3.1 Info and Relationships Perceivable WCAG 1.4.3 Contrast (Minimum) Perceivable WCAG 2.4.4 Link Purpose (In Context) Operable WCAG 3.1.1 Language of Page Understandable WCAG 3.3.1 Error Identification Understandable WCAG 4.1.2 Name, Role, Value Robust

Test WCAG 2.1.1 on your website

Free WCAG 2.1 AA audit covering all 50 success criteria. No signup required.

Run free audit