Glossary · Accessibility term
Keyboard accessibility
Keyboard accessibility means every piece of functionality on the page can be operated through a keyboard interface. That is the actual wording of the rule and it is worth reading twice, because it is about functionality rather than about Tab reaching everything. Without a mouse is the everyday shorthand for it and the two are not the same, since a keyboard-driven mouse emulator does not satisfy the rule. Tab moves between controls, Enter and Space activate them, and arrow keys move inside a menu or a radio group. A menu that Tab enters once and arrow keys navigate through is the correct pattern, not a gap. The reason this serves so many people is a definition most readers never meet. What the standard asks for is operability through a keyboard interface, which is the software channel a program uses to receive keystrokes. Speech-to-text software, on-screen keyboards and switch devices all send keystrokes down it. So blind people, people with tremor or limited dexterity, and people who never touch a keyboard at all are served by one rule. Two things it does not cover. The rule carves out functions that depend on the path the user's movement takes rather than only where it starts and ends, such as free-hand drawing. And being fully keyboard operable does not on its own satisfy the rules about pointer gestures, because some people use a pointing device and cannot be precise with it.
In practice
The failures cluster in custom controls, and the pattern is always the same. Native buttons, links and form fields are keyboard operable for free. Anything built from a div starts with nothing, and adding tabindex only buys focusability. Enter and Space still do nothing until somebody writes the key handling, which is the half that ships missing.
Reaching a control is not the same as being able to use it. A page where focus lands somewhere invisible, or behind a sticky header, is keyboard operable on paper and unusable in practice, and both of those have rules of their own. Test for where focus is, not only for whether it moved.
The Escape convention is worth placing accurately. WCAG never says Escape closes things, and deliberately declines to define what counts as a standard way out. Escape comes from the authoring practices for dialogs, which is where the expectation was set. So it is a strong convention rather than a rule, and a component using something else conforms as long as it says so.
One correction to the mental model. Screen reader users mostly do not tab through pages. They navigate by heading, and 71.6% say so. Keyboard operability still matters just as much, because activating anything goes through it. The picture of somebody pressing Tab 40 times to reach your menu is not how the journey usually starts.
Why it matters
It is the single most revealing test you can run on your own site, it takes about ten minutes, and most owners find something in the first 30 seconds. Put the mouse out of reach and complete one real task end to end, the one that makes you money. Anything you cannot reach, cannot operate, or cannot escape from is a defect, and you will have found it yourself without buying anything. It costs you nothing.
The whole test
Unplug the mouse and buy something from your own shop. Tab is your only key, plus Enter, Space and the arrows. Time yourself, and note every place you had to guess where you were, because that is a second finding sitting on top of the first.
Where this shows up on the site
Related terms
- FocusFocus is the one place on a page that is currently taking keyboard input.
- Focus trapA focus trap is somewhere on a page that keyboard focus can get into and not out of.
- Focus orderFocus order is the sequence focus travels in as you press Tab, and by default it follows the order elements appear in the code rather than the order they appear on screen.
- TabindexTabindex is an HTML attribute that decides whether an element can take keyboard focus and where it sits in the tab order.
- Switch deviceA switch device is an input for people with severely limited movement, and the picture most people have is a single large button pressed with a hand, head or knee.
- OperableOperable is the second WCAG principle, and its one-line statement is that user interface components and navigation must be operable.
Knowing the word is the easy part.
Find out where your own site stands. The free scan checks 10 pages in a real browser against all 90 supported automated rules, separates 27 best-practice checks from its WCAG findings, and names the rule behind every result.