For AI agents and LLMs: a machine-readable index is available at llms.txt. A plain-Markdown version of any documentation page is available by appending .md to its URL.
Skip to main content

Keyboard Guided Test

Many users cannot use a mouse. They move through a page with the Tab key. If a control cannot receive focus, or if focus is not visible, these users cannot use the page.

The Keyboard test moves through the page with real Tab key presses, the same way a keyboard user does. It records each element that receives focus, in order, and then checks each one for the most common keyboard issues.

When to use this​

Use this test to check tab order, keyboard traps, and focus visibility on a page or flow, for example a checkout form, a navigation menu, or a page with a sticky header.

Prerequisites​

The TestMu AI Accessibility Toolkit is installed. See Install Toolkit.

What the test checks​

RuleWCAGSeverity
Keyboard focus is trapped2.1.2 (A)Critical
Element not keyboard reachable2.1.1 (A)Critical
Hidden element receives focus2.4.3 (A)Serious
Focus indicator is missing2.4.7 (AA)Critical
Form submitted on focus3.2.1 (A)Serious
New window launched on focus3.2.1 (A)Serious
Focused element is entirely hidden by other content2.4.11 (AA)Serious
Focused element is partly hidden by other content2.4.12 (AAA)Moderate

The report includes only the rules that fall within the WCAG version and level you set in DevTools Settings.

Run the test​

Start the test​

Open Assisted Tests in Accessibility DevTools and select Keyboard. Turn on Verify with AI if you want AI to give the first answers. See Start a guided test.

Record the tab order​

The test presses Tab through the page and follows the real focus in the browser. It does not guess the order from the page code. Each element that receives focus is added to the list in the order it was reached.

Check for keyboard traps​

If focus cannot move away from an element, the test stops and asks you to try to leave it with the keyboard. Your answer decides whether the report shows a keyboard trap. The test then continues from the next element.

Review elements the keyboard cannot reach​

The test lists elements that look interactive but never received focus. Confirm which ones are real controls. If you find a control the test missed, click it on the page to add it.

Review focus visibility​

The test compares each element with and without focus. It flags elements that show no visible change when focused, and elements that a sticky header or banner covers when they receive focus.

Review and finish​

The review screen shows each element with its passed and failed checks. You can mark any result as passed or failed before you finish the test.

How AI helps​

With Verify with AI on:

  • AI compares each element with and without focus and decides whether the focus indicator is visible.
  • AI looks at each element that did not receive focus and decides whether it is a real control.

You can change any AI answer on the review screen.

AI credits

Verify with AI will require AI credits. See Credits Management.

Terminal First Testing With Kane CLI

Natural language browser & mobile app tests right from terminal.

×
Schedule Your Personal Demo
Kane CLI terminal

Help and Support

Related Articles