Keyboard accessibility testing: a quick check
Keyboard accessibility testing starts with a few simple keys. Putting the mouse away is a practical way to check if a website works for people who use a keyboard.
Why keyboard access matters
When a website loads, many people reach for a mouse or tap a trackpad without thinking. For many people with disability, those tools are not an option. Some people use only a keyboard to move around a website. If a website is not built to handle these inputs, it becomes a barrier. A button that cannot be reached with a keyboard cannot be used.
A quick check can show these barriers. When a team ignores this step, they may leave barriers in place. The check tests the basic pathways that let a person move through a page from top to bottom. Regular testing helps keep digital services open to people who use a keyboard.
The physical steps of the check
To run this check, a person puts the mouse away entirely. The test uses the Tab key on its own, then Shift and Tab together, then Enter, Space and the arrow keys. Moving forward with the Tab key should move the focus through every interactive element on the page. This includes links, buttons, form fields and dropdown menus. Moving backward with Shift and Tab should move the focus through those same elements in the exact reverse order. Enter should open a link or press a button, Space should press a button, and the arrow keys should move through menus.
As the tester moves through the page, they must watch the screen closely. Every link, button and form field on the page must be reached and used without a mouse. The focus indicator, which is usually a coloured border around the active element, must always be visible. If the focus indicator disappears, a keyboard user has no way of knowing where they are on the page. The order of the elements must make sense as you move through them, and there must be no keyboard traps where a user gets stuck.
The administrative burden of manual tracking
While the keyboard check itself is simple, documenting the results is slow. When a tester finds a problem, they have to write down exactly what went wrong and where it happened.
This means noting each problem with the page and the step that caused it. The tester must record the page address, the element that failed, the key that was pressed, and what happened instead of the expected action. If a keyboard trap occurs, where the focus gets stuck inside a menu and cannot get out, that must be documented too. Writing each problem down by hand takes time. It turns a quick practical check into a repetitive writing task.
How an AI tool can help write the report
An AI tool can help with the writing. A tester still sits at the desk, puts the mouse aside, and presses the keys to find the barriers. But instead of stopping to write a detailed report for every broken link, they can speak or type a quick note about what they see.
An AI tool can take those raw observations and structure them into a clear, professional report. It can format the output for web developers. The machine handles the repetitive writing and the formatting. This allows the tester to focus on the actual experience of navigating the site.
The decisions left to people
Even with these tools, the actual testing remains a human task. A person feels the frustration of a keyboard trap and judges whether the reading order of a page makes logical sense. A person must decide if the layout feels natural and intuitive. Human judgment decides how to present information clearly.
People keep the part of the work that requires judgment and empathy. A human tester decides which pages are most important to check first, such as the checkout page or the contact form. They make the final call on whether a focus indicator is clear enough for someone with low vision to see. The person signs off on the final report and decides how to explain the necessary changes to the development team.
Related: how to set your AI's rules once with custom instructions.
Making digital spaces open to all
When a team learns to run a quick keyboard check, they build a better understanding of digital barriers. Using simple keyboard commands is a practical way to check any website.
If you want your own website, app or documents to work for everyone, see digital accessibility at aXai: testing and fixes to WCAG, and Easy Read versions of what you already publish.
Easy Read version
Testing websites with a keyboard
You can test a website with a few keys on your keyboard.
Some people cannot use a computer mouse.
They use the keyboard to move around websites.
How to do the check
Put your computer mouse away.
You will use the Tab key, Shift and Tab, Enter, Space and the arrow keys.
Press the Tab key to move forward.
Press the Shift and Tab keys to go back.
Press the Enter key to use a link or button.
You can also use the Space key to use a button.
Use the arrow keys in menus.
Check every link, button and form field on the page.
You must always see which item is selected.
You must never get stuck.
The order must make sense.
Write down each problem with the page and the step.
What the machine does
Writing down every website error takes a long time.
AI can write the reports for you.
It takes your quick notes and makes them neat.
What people do
Only a person can test if a website makes sense.
People decide which pages are most important to check.
People make the final decisions.
aXai helps make websites, apps and documents work for everyone.
