The short answer. Load your homepage, unplug the mouse, and press Tab. You should be able to reach everything, see where you are at every stop, move in the order your eyes follow, escape every popup, work every menu, and finish your site’s main task — a booking, a form, a purchase — without the mouse once. Each place that fails is a real barrier with a WCAG rule behind it, listed test by test below.
Why this check matters. Keyboard travel is the route underneath almost all assistive technology: switch devices, voice control and screen readers all move through a page the way the keyboard does. It is also the part an automated scan honestly cannot walk for you — a scanner proves barriers in the code, but only a person pressing Tab discovers the order focus travels, whether it stays visible, and whether a dialog lets you back out. Twenty minutes, no tools, no expertise: just you, your site, and the keys.
Before you start: a 2-minute setup
- Mouse away. Unplug it or put it in a drawer — habit will reach for it at the first awkward moment, and that moment is exactly a finding.
- One browser, full screen. Test the site as visitors get it, popups, banners and chat widget included — not a stripped preview.
- A note sheet with four columns: page, step, what you expected, what actually happened. Dated notes are what turn this from a feeling into a record your developer can act on.
- The keys: Tab forward, Shift+Tab back, Enter for links and buttons, Space for buttons and checkboxes, arrow keys inside menus and groups, Escape to close.
The seven tests, in order
Reach everything without the mouse
Start at the top of your homepage and press Tab, one stop at a time. Every link, button, field and control a mouse user can click must also be reachable by Tab alone. The stops that fail are usually the pretty ones: clickable images and cards that are not real links, icon buttons built from plain text blocks, and “buttons” a developer made out of a styled paragraph.
Write down any element you can see but can never land on. If a mouse can do it and Tab cannot reach it, a keyboard user cannot do it at all.
See where you are at every stop
At every Tab stop you should be able to answer one question instantly: where am I? A visible outline, underline change or highlight must appear around the focused element. Many sites remove the browser outline in CSS because it “looks untidy” — and with it goes the only map a keyboard visitor has.
If you have to guess where focus is, or it disappears behind a banner or sticky header, record the page and the stop. Invisible focus fails WCAG 2.4.7 even when everything is technically reachable.
The order must match what your eyes see
Focus should travel the way a sighted visitor reads: header, then down the page in visual order, left to right, top to bottom. Jumps that teleport you from the top menu to a footer link, then back into the middle of the page, usually come from popups injected at the end of the code or content rearranged with CSS alone.
Note every jump that surprised you. Surprise is the test: if the order confuses you while you can see the page, it is worse for someone navigating by focus alone.
Get out of every popup, menu and widget
Deliberately Tab into every interactive layer your site opens: the cookie banner, the newsletter popup, the chat widget, dropdown menus, a video player, a search overlay. Then get out using only Escape and Shift+Tab. Every layer must let you leave the way you came in.
The moment you have to reach for the mouse to escape, you have found a keyboard trap — the single most serious finding this check can produce. Stop, write down exactly where it happened, and treat it as fix-first.
Menus and controls must answer their natural keys
Open menus with Enter or Space, move inside them with the arrow keys, and close them with Escape — focus should return to the button that opened the menu. Sliders, tab panels and radio groups answer to arrow keys; checkboxes and buttons to Space. A menu that only opens when a mouse hovers over it is closed to keyboard visitors, however good it looks.
Try the keys a first-time visitor would try. If the control ignores them, that is a finding — visitors are not supposed to guess a secret key combination.
A way past the repeated parts
On any site with a long menu, the first Tab stop should offer a “Skip to content” link — visible when focused — that jumps past the navigation. Without it, a keyboard user must Tab through every menu item on every single page before reaching the page itself. Also check that the skip link actually lands in the main content, not just hides the menu visually.
Count the Tab presses it takes to reach the first real content on a page. If the honest answer is “dozens, on every page”, record it.
Finish one real task, keys only
Finally, do the thing your site exists for, start to finish, without the mouse: book the appointment, send the contact form, or buy the product. Fill every field, correct a deliberate mistake and read how the error is announced and where focus goes, choose delivery or options, and reach the confirmation. Errors must be described in text and reachable — not shown only as a red border you may never land on.
If you cannot finish the flow, a keyboard customer cannot either — and unlike you, they cannot just pick the mouse back up. Record the exact step where the flow broke.
Five failures this check finds again and again
The outline a designer removed
A CSS rule hides the focus outline because it looked untidy in a screenshot. Everything is reachable — and nobody can see where they are. WCAG 2.4.7 fails on the very first page.
The friendly popup that locks the door
A discount or chat popup opens, takes focus, and offers no keyboard way out. The visit ends there, whatever the page behind it contains. That is a WCAG 2.1.2 trap, not a quirk.
The menu that only opens for a mouse
Hover-built menus look complete and do nothing at all for a keyboard. If Enter, Space and the arrows cannot open and close it, the pages behind it may as well not exist.
The error only a colour announced
A form refuses to submit and marks a field in red — but focus never goes there and no text explains it. A keyboard visitor knows something failed and cannot find out what.
The checkout that gives up at the last step
Everything works until the payment or booking widget — a third-party frame nobody tested. The flow breaks at the exact step the site exists for. Test the money flow last, and test it whole.
Your 9-point keyboard checklist
- Everything a mouse can click is reachable with Tab alone.
- Focus is clearly visible at every single stop.
- Focus order follows the visual order of the page.
- Every popup, menu, banner and widget can be escaped with Escape or Shift+Tab.
- Menus open with Enter or Space, answer arrow keys, and close with Escape.
- A skip link (or an equally short route) gets past repeated navigation.
- One full money flow — form, booking or checkout — finishes keys-only.
- Form errors are written in text, reachable, and say what to fix.
- Every finding is written down dated: page, step, expected, actual.
What this check cannot tell you. Keyboard travel is one route through your site. It says nothing about whether your images carry meaningful alt text, whether text contrast passes, whether fields have labels a screen reader can announce, or whether your headings form a map. Those are the barriers an automated scan does prove — roughly 30–40% of accessibility problems are the technical kind a machine can check. The two passes belong together: yours finds how the site travels; a scan finds what the code is missing.
Get the other half of the picture
Run the free 6-check snapshot of your homepage on our home page — no email needed — or order the Full Report: a dated PDF of every provable barrier on your scanned pages, ranked by severity, each tied to its WCAG 2.2 AA rule, with plain-English fixes for your developer. $15 one-time. Prefer a human pass? The Human Key-Flow Check ($495) walks up to 5 money flows keyboard-only and with the NVDA screen reader. Neither is a certification of compliance, and neither is legal advice — they are dated, honest records of where your site stands.
Watch Plan $18/month re-scans monthly so fixed barriers do not quietly come back. 30-day refund policy; full refund if a report fails to generate.
Frequently asked questions
Do I need special software to test keyboard navigation?
No. You need a desktop browser and your keyboard. Unplug the mouse or put it in a drawer so you do not reach for it out of habit. A simple note sheet — page, step, what you expected, what actually happened — is the only other tool. Screen-reader testing is a separate, deeper step; this check is deliberately the one any owner can do today.
Which keys do I actually use?
Tab moves forward through links, buttons and fields; Shift+Tab moves back. Enter activates a link or button, and Space activates buttons and toggles checkboxes. Arrow keys move inside menus, radio groups, tabs and sliders. Escape closes menus, dialogs and popups. If a control does not respond to the keys a visitor would naturally try, that is a finding, not a user error.
What is a keyboard trap?
A keyboard trap is any place where focus goes in by keyboard but cannot come out the same way — a popup, chat widget, video player or form you can enter with Tab but can only leave with a mouse click. It breaks WCAG 2.1.2 (No Keyboard Trap), and for a keyboard user it is a locked door: the visit ends there.
If my site passes this keyboard check, is it ADA compliant?
No. Keyboard travel is one slice of accessibility. A site can tab beautifully and still have images without alt text, weak contrast, unlabelled fields or headings a screen reader cannot follow. Passing this check means one important route works; it is not a certification of compliance with the ADA, WCAG or Section 508, and nobody honest will sell you one.
Can an automated scan test keyboard navigation for me?
Only partly, and that limit is worth knowing. A scanner can prove technical barriers in the code — missing labels, missing alt text, a missing page language — and our free homepage snapshot says plainly that keyboard order is not one of the things it counts. The order focus actually travels, whether you can see it, and whether a dialog traps you are things a person pressing Tab discovers. That is why keyboard testing stays a manual pass, including in our own Human Key-Flow Check.
What should I do with the problems I find?
Write each one down with the page, the step where it happened and what you expected instead — that note is exactly what a developer needs. Fix blockers first: traps, invisible focus and anything that stops a form or checkout from being finished. Then re-run the same route to confirm the fix, and date your notes. A dated record of what you checked and fixed is evidence of good-faith effort.
How often should I repeat the keyboard test?
Repeat it after any redesign, new popup or chat tool, new menu, or checkout change — the changes that most often break keyboard travel — and spot-check your main money flow every few months. Sites change constantly, and barriers that were fixed quietly come back; a dated note from each pass keeps the record honest.
Written by ADA Site Check, Portland, Oregon. Questions: contact@getadasitecheck.com. This guide is practical information, not legal advice, and not a certification of compliance with the ADA, WCAG or Section 508.