Keyboard

This skill puts the mouse away and walks a running page with keys alone. It records every focus stop in order and returns a numbered report of what the keyboard cannot reach, see or operate.

Every stop pressed, never read from the code

Focus order, reach and operation are judged from keys pressed in the running page. A stop the walk did not press is Not verified, never assumed. One unreachable control is a finding however minor the control.

How the focus ring looks, dialog focus traps and accessible names belong to defaults, and a failure there cites its id. Opening the running result belongs to verify. Forcing hidden states open belongs to lab.

1. Load the recorder

Open the page at the state the user named and click nothing. Run tabstops.js through the browser's evaluate call. It returns pointer targets with no keyboard way in, then records each stop as keys are pressed. Judging order or reach from the markup is keyboard-press-the-keys.

Send keys through trusted input, such as Playwright's keyboard.press or the operating system. A dispatched DOM KeyboardEvent never moves focus, so a walk with no stops means the keys never arrived.

2. Walk forward, then back

Press Tab from the top of the page until focus leaves it, then Shift+Tab back to the start. Read window.__keyboard.stops and call window.__keyboard.highlight().