Skip to main content
All WCAG Criteria
2.1.1
A

Keyboard

Operable › 2.1 Keyboard Accessible › WCAG 2.0

Overview

All functionality of the content is operable through a keyboard interface without requiring specific timings for individual keystrokes, except where the underlying function requires input that depends on the path of the user's movement.

Understanding

The W3C Web Accessibility Initiative (WAI) provides detailed guidance on understanding and implementing this criterion. The Understanding document covers the intent, benefits, and supporting techniques in depth.

Read Understanding 2.1.1 on W3C WAI

Techniques

W3C provides documented techniques for meeting this criterion. Each technique links to the full specification with code examples and test procedures.

How to Test

  1. Navigate the entire page using only the keyboard (Tab, Shift+Tab, Enter, Space, Arrow keys).

  2. Confirm all interactive elements receive focus and are operable without a mouse.

  3. Check that no keyboard traps exist — you can always navigate away from any component.

  4. Test dropdown menus, date pickers, modals, and custom widgets for full keyboard support.

  5. Verify any drag-and-drop functionality has a keyboard alternative.

How VPATify tests this

VPATify runs automated WCAG checks against every page you scan and flags violations against individual success criteria. Our deep scan combines axe-core, contrast analysis, and structural checks to catch criterion-level failures that single-tool scans miss. See the full testing methodology and features for what's covered at each level.

Run a deep scan

Want deeper accessibility insights?

Scan your entire website and generate an official VPAT document — free, in minutes.

Scan Your Site — It's Free