Your files stay on your device

Keyboard navigation auditor

Paste HTML and get the computed tab order, keyboard barriers like positive tabindex and unreachable controls, a manual check sheet, and a Markdown or CSV report.

Paste a snippet or a whole page and press Audit keyboard access. You get the computed tab order, the barriers the markup itself reveals, and a manual checklist for the parts only a real keyboard pass can prove.
What this can and cannot see

The walk follows the browser rule for sequential focus: positive tabindex values run first in ascending order, then tabindex="0" and natively focusable controls in document order. The hidden attribute, inline display:none and visibility:hidden, inert, the disabled attribute, and disabled fieldsets take controls out of the chain. aria-hidden does not, which is exactly why focusable markup inside it is flagged.

Markup alone cannot show:

- hiding done only in a stylesheet, or an outline removed only in CSS
- focus traps a script creates at runtime, or focus a dialog should return
- whether Shift+Tab retraces the order or skip links actually move focus
- a nested fieldset's escape from a disabled ancestor fieldset

The manual checklist is the other half of the audit. Record it in your own browser; an unrecorded check stays unproven in the verdict.
OptionsAudit keyboard access

More regex & cron tools

- Accessible name debugger (/dev/accessible-name-debugger)
- Keyboard test (/device/keyboard)
All regex & cron tools (/dev)

Was this tool useful?
YesNo

Canonical HTML: https://nutter.tools/dev/keyboard-navigation-auditor
Markdown version: https://nutter.tools/dev/keyboard-navigation-auditor.md
Plain-text version: https://nutter.tools/dev/keyboard-navigation-auditor.txt
Agent index: https://nutter.tools/llms.txt