A keyboard accessibility test asks one question: can a person use your whole site without a mouse? Anyone on staff can run it in about 15 minutes with the Tab, Enter, Space, arrow and Escape keys. It finds problems scanners cannot judge, such as an invisible focus outline or a cookie banner you cannot leave.
Our plain guide to web accessibility gives keyboard testing one paragraph. This post turns that paragraph into a timed, step-by-step check. Each step names the keys, what a pass looks like, and the WCAG success criterion behind it.
The short version: put the mouse away and press Tab from the top of the page. You should see a skip link first, then a clear focus outline that moves in reading order. Every menu, pop-up and form should work, and nothing should trap you. Each failure maps to a numbered WCAG rule, so a developer knows what to fix.
Why a keyboard accessibility test matters
The W3C’s Easy Checks page says: "Many people cannot use a mouse and rely on the keyboard to interact with the Web." That includes people with limited hand movement, screen reader users, and people using speech input. The W3C’s Understanding page for 2.1.1 Keyboard notes that many such tools act as "keyboard emulators."
So keyboard accessibility supports most other assistive technology. A donation button that only answers a mouse click may be out of reach for a screen reader user too.
Scanners cannot judge keyboard accessibility the way a person pressing Tab can. The W3C’s evaluation guidance says "no tool alone can determine if a site meets accessibility standards." Tools like Deque’s axe catch missing labels. A person catches a focus order that jumps around the page.
Before you start: pick five pages and learn six keys
Choose pages people use most:
- The home page
- A long content page with a sticky header
- The donation, membership or registration form
- A page with a carousel, video or embedded map
- Any page that shows a cookie banner, newsletter pop-up or modal
Click the address bar, then set the mouse aside. On a Mac, the W3C notes that some browsers need keyboard navigation to all controls turned on first.
| Key | What it does | Where you use it |
|---|---|---|
| Tab | Moves focus to the next link, button or field | Everywhere |
| Shift+Tab | Moves focus back one item | Everywhere |
| Enter | Follows a link or presses a button | Links, buttons |
| Space | Presses a button, ticks a checkbox | Buttons, checkboxes, radio buttons |
| Arrow keys | Moves within a group | Menus, lists, radio groups, tabs |
| Escape | Closes a dialog, menu or tooltip | Pop-ups, menus, cookie banners |
These follow the W3C’s ARIA Authoring Practices Guide: Tab moves between components, and arrow keys move inside one, such as a menu or a set of tabs.
Minutes 0 to 2: the skip link
Press Tab once from the address bar. The first thing to get focus should be a link such as "Skip to main content."
What passes. The link appears when it has focus. Press Enter. Focus should move to the main content, and the next Tab should reach the first link there.
WCAG. 2.4.1 Bypass Blocks, Level A. The W3C’s technique G1 says it is "preferable for links to be visible at all times," but a link that shows only on focus can pass. Landmarks and headings are other ways to meet 2.4.1, so a missing skip link is a note for the developer to confirm.
Common failure. The skip link stays invisible on focus, or focus stays in the header after Enter.
Minutes 2 to 5: visible focus and logical order
Tab through the header, content and footer, then Shift+Tab back up.
Visible focus. At every press, you should see where you are. A ring, underline or color change is fine. The rule is 2.4.7 Focus Visible, Level AA. Its Understanding page lists removing the outline with CSS as failure F78.
Logical order. Focus should move the way you read, without jumping to the footer and back. The rule is 2.4.3 Focus Order, Level A. A common cause is tabindex used to force an order, which the W3C lists as failure F44.
Not hidden. The focused item should never slide completely under a sticky header or a banner pinned to the bottom of the screen. That is 2.4.11 Focus Not Obscured (Minimum), new at Level AA in WCAG 2.2.
No surprises. Nothing should happen just because an item gets focus. A new window opening or a form submitting on focus fails 3.2.1 On Focus, Level A.
Minutes 5 to 7: menus and drop-downs
Tab to the main navigation. Open a drop-down with Enter, Space or the Down arrow, move through it, then press Escape.
What passes. Every menu item you can reach with a mouse, you can reach with the keyboard. Easy Checks warns that "some functionality is available only with mouse hover, and is not available with keyboard focus." That fails 2.1.1 Keyboard, Level A.
Escape. A submenu or tooltip that opens on focus should close without moving focus. The Understanding page for 1.4.13 Content on Hover or Focus gives pressing Esc as an example. That rule is Level AA.
Common failure. A drop-down list that loads a new page the moment you press the Down arrow. Easy Checks flags this because the other options are out of reach.
Minutes 7 to 10: cookie banners, donation pop-ups and modals
Reload a page with a cookie banner or newsletter pop-up. Then open a modal, such as a "Donate now" pop-up.
What passes. The W3C’s modal dialog pattern sets the expected behavior:
- When the dialog opens, focus moves into it.
- Tab and Shift+Tab cycle through the dialog’s controls only.
- Escape closes the dialog.
- When it closes, focus returns to the button that opened it.
WCAG. Focus that stays behind the modal, or lands at the top of the page after closing, is a 2.4.3 Focus Order problem. A banner you can tab into but never leave fails 2.1.2 No Keyboard Trap, Level A. A non-modal banner that fully covers the focused item fails 2.4.11.
Common failure. A cookie banner pinned to the bottom of the screen and last in the tab order. It hides what you focus on until you tab through the whole page to accept it.
Minutes 10 to 12: carousels and embedded media
Tab into a carousel, a video player and any embedded map or form.
Carousels. You should find a pause or stop button. Rotating slides that start on their own and run more than five seconds need a way to pause them under 2.2.2 Pause, Stop, Hide, Level A. The W3C’s carousel pattern also says rotation "stops when any element in the carousel receives keyboard focus."
Media and embeds. Easy Checks names the most common trap: "the keyboard focus gets caught in media controls and you cannot get out." If focus never leaves the player, that fails 2.1.2 No Keyboard Trap. Third-party embeds count: the Understanding page for 2.1.2 says this rule applies to all content on a page, because a trap can block the whole page.
Minutes 12 to 15: forms, errors and custom widgets
Complete your busiest form, such as donation or renewal, with the keyboard only.
Fields. Tab reaches every field in order. Arrow keys move within radio buttons, such as gift amounts, and within drop-down lists. Space ticks checkboxes.
Errors. Leave a required field blank and submit with Enter. The error should name the field and say what is wrong, in text. That is 3.3.1 Error Identification, Level A. WCAG does not require focus to move to the error, but you should be able to Tab to the field and fix it.
Custom widgets. Date pickers, amount sliders, accordions and "Read more" toggles are often custom-built. If one ignores Enter and Space, it fails 2.1.1 Keyboard. The W3C lists faking a link with script as failure F42.
Finish line. Can you reach the payment step and submit? If a third-party payment form traps focus or will not take keyboard input, the whole process fails at that level.
The printable keyboard accessibility checklist
As of October 2026, WCAG 2.2 is the current W3C Recommendation. This keyboard accessibility checklist uses its numbers and levels.
| Check | Keys | WCAG success criterion | Level |
|---|---|---|---|
| First Tab shows a skip link that moves focus to the main content | Tab, Enter | 2.4.1 Bypass Blocks | A |
| Every link, button, field and control can be reached and used | Tab, Enter, Space, arrows | 2.1.1 Keyboard | A |
| Focus can always move away; nothing traps you | Tab, Shift+Tab, Escape | 2.1.2 No Keyboard Trap | A |
| Focus moves in reading order; modals take and return focus | Tab, Shift+Tab | 2.4.3 Focus Order | A |
| Nothing changes just because an item gets focus | Tab | 3.2.1 On Focus | A |
| Auto-rotating carousels can be paused | Tab, Enter | 2.2.2 Pause, Stop, Hide | A |
| Form errors name the field and the problem in text | Enter | 3.3.1 Error Identification | A |
| You can always see which item has focus | Tab | 2.4.7 Focus Visible | AA |
| Focused items are never fully hidden by sticky headers or banners | Tab | 2.4.11 Focus Not Obscured (Minimum) | AA |
| Menus and tooltips that open on focus can be closed without moving focus | Escape | 1.4.13 Content on Hover or Focus | AA |
Print it and mark each row pass or fail for each of your five pages.
What to do with the results
Write each keyboard accessibility failure in one line: page, key pressed, what happened, and the WCAG number. "Donation page: Tab from Amount jumped to footer, 2.4.3" is enough for a developer.
Most keyboard failures live in shared parts: the theme, menu, cookie banner and form components. One fix there covers every page. Re-run the keyboard accessibility test after theme updates, new plugins or modules, and changes to the donation flow.
This keyboard accessibility test does not replace screen reader, zoom or contrast checks. Our breakdown of the nine new WCAG 2.2 success criteria goes deeper on 2.4.11 and focus appearance. Documents need their own pass: our accessible PDF checklist covers files that have to stay PDFs.
Frequently Asked Questions
What is keyboard accessibility?
It means every part of a website works with a keyboard alone, with no mouse. People who cannot use a mouse rely on it, and so do many screen reader and speech input users. WCAG covers it mainly in 2.1.1 Keyboard and 2.1.2 No Keyboard Trap.
Do I need special software to test keyboard accessibility?
No. You need a browser and a keyboard. On a Mac, some browsers need keyboard navigation to all controls turned on first, per the W3C’s Easy Checks.
What is a keyboard trap?
A place where focus goes in and cannot come out using the keyboard. Media players, embedded forms and pop-ups are common causes. It fails 2.1.2 No Keyboard Trap at Level A.
Does a skip link have to be visible all the time?
No. The W3C’s technique G1 says always visible is preferable, but a link that appears when it gets keyboard focus can meet 2.4.1 Bypass Blocks.
Is it a failure if our focus outline is faint?
At Level AA, 2.4.7 Focus Visible asks only that focus be visible. Size and contrast rules sit in 2.4.13 Focus Appearance, Level AAA. A faint outline is still worth fixing.
Should the Escape key close every pop-up?
The W3C’s modal dialog pattern says Escape closes a dialog. For tooltips and submenus that open on focus, 1.4.13 requires a way to dismiss them, and Escape is the W3C’s example.
Can an automated scanner check keyboard accessibility?
Only in part. A scanner can flag some code problems. It cannot tell whether focus is visible, whether the order makes sense or whether a pop-up traps you. That takes a person.
Do third-party widgets like donation forms count?
Yes. A widget on your page is part of the page, and 2.1.2 applies to all content. Ask the vendor to fix what you find.