Perspective

Keyboard testing without just pressing Tab

Test whether real tasks can be completed from the keyboard, with sensible focus and expected control behaviour.

Keyboard testing is more than checking whether focus eventually reaches every link.

Start with a task

Choose a real flow and put the pointer aside. Know what successful completion requires before testing individual controls.

Test reachability

Use Tab and Shift+Tab where appropriate. Confirm interactive elements can be reached and focus is visible. Check that focus order follows a meaningful sequence.

Test operation

Activate controls using their expected keyboard interaction. Native controls do not all use Tab plus Enter: radio groups, select controls, menus and other widgets have established patterns.

Test entry and escape

Dialogs, menus and composite components need sensible entry, internal navigation and a way out. Confirm there is no keyboard trap.

Watch what happens after actions

When content opens, closes, disappears or updates, check where focus goes and whether continuing the task makes sense.

What to record

Record the task, browser/platform, input method, failure point, expected behaviour and evidence. A video can help with focus-management failures, but written reproduction steps still matter.

What a pass establishes

The tested flow was operable with the keyboard in the tested environment.

What it does not establish

It does not prove screen-reader usability, speech-input access, good touch targets, cognitive usability or keyboard access to flows you did not test.

Follow the evidence trail

Start with the keyboard barrier → try the keyboard Lab → compare findings with WCAG 2.2 Keyboard Accessible.