WCAG 2.0 · Level A · Operable

WCAG 2.1.1 — Keyboard

All functionality must be operable with a keyboard alone.

WCAG 2.1.1 at a glance

Level A · Principle: Operable · Added in WCAG 2.0. Level A is the minimum — failing it blocks some users entirely.

What it means

All functionality must be operable with a keyboard alone.

Who it helps

Keyboard-only users, screen-reader users, and people with motor disabilities.

Common failures

  • Custom controls (divs as buttons) that aren’t focusable or operable
  • Drag-only interactions
  • Menus that only respond to mouse

How to meet WCAG 2.1.1

  1. Use native interactive elements
  2. Ensure focusability and key handlers (Enter/Space)
  3. Provide keyboard alternatives to pointer actions

How to test it

Manual — unplug the mouse and operate the page.

Frequently asked questions

Is WCAG 2.1.1 Level A or AA?
WCAG 2.1.1 (Keyboard) is a Level A success criterion, introduced in WCAG 2.0. Level A is the baseline.
How do I test WCAG 2.1.1?
Manual — unplug the mouse and operate the page.

Stay ahead of accessibility rules

Practical WCAG, ADA & EAA updates, new free tools, and plain-English guides — occasional emails, no spam.