Skip to content We're live on Product Hunt today Upvote
install

diagnostic · one of 36 free, no counter

Keyboard walk

Is anything on this page a keyboard trap?

A keyboard trap is invisible until somebody is stuck in it, and it never shows up in a static reading because it is a fact about what happens when you press Tab. This is a recording rather than a scan: it walks the page, logs each stop with the faults found there, and the whole point is that the log survives the walk.

Reach it Press + K on any tab and type keyboard walk. Ctrl + K on Windows and Linux

Walks the page with Tab and records every stop, trap and skip
reads focus, as it moves
writes nothing beyond moving focus
sends nothing
records yes - a rerun discards the walk
faults a severity table, worst mark per stop
rows twenty at a time; the chips count the whole walk
plan free
section#about

What this actually is

On anything with a modal, a custom widget, or an embedded third-party frame. It is also the check nobody runs before shipping a cookie banner, which is where a large share of real traps live.

section#asked

Asked about this diagnostic

Why does this one not have a Run again button?

Because it is a recording rather than a reading. Re-running would stop the walk and throw away every stop it had logged, which is the opposite of what the button appears to offer.

What counts as a trap?

A stop from which Tab does not move on - focus stays where it is or returns to the same element. Modals and embedded players are where they usually are.

Does it click anything?

No. It moves focus, which is what the keyboard does. Nothing is activated, so a walk cannot submit a form or trigger a purchase.

Why do the chip counts not match the rows on screen?

The rows are paged twenty at a time; the chips count the whole walk. A summary that only described the visible page would be useless for deciding whether to keep reading.

how to use keyboard walk

  1. Open Keyboard walk on a page with a modal, a custom widget or a third-party frame.
  2. Start the walk. It moves focus itself and logs every stop it reaches.
  3. Read the faults per stop, worst first. The chips count the whole walk, not the visible twenty.
  4. Read the log before you rerun: a second walk discards the first, which is what makes it a recording.