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

Guided Tests

Automatic scans find many accessibility issues, but not all of them. Some checks need a person to decide. For example, only a person can say if alt text describes an image correctly, if a heading describes the content that follows it, or if a dialog is really closed.

Guided tests close this gap. Each guided test does the automatic checks first. Then it asks you a small number of clear questions about the results. In most tests, AI can answer many of these questions for you. In the Modals and Responsiveness tests, the extension drives the page itself and fills in the answers from what it observed. You examine the answers and finish the test, and you get a report in the same format as a normal scan.

When to use this​

Use a guided test when you need to check a part of WCAG that a scan cannot decide alone, such as tab order, focus visibility, control names, alt text quality, tooltip behaviour, heading structure, form labels, table headers, modal focus handling, or reflow. Run a Full Page Scan first for the automatic rules, then use guided tests for the rest.

Available tests​

TestWhat it coversWCAG success criteria
KeyboardTab order, keyboard traps, elements the keyboard cannot reach, focus visibility2.1.1, 2.1.2, 2.4.3, 2.4.7, 2.4.11, 2.4.12, 3.2.1
Interactive ElementsName, role, and state of buttons, links, form fields, and custom controls4.1.2
ImagesText alternatives, decorative images, images of text, complex images1.1.1, 1.4.5, 4.1.2
Hover and TooltipsTooltips, popovers, and hover cards: whether they stay visible, close with Escape, and stay open when the pointer moves onto them1.4.13
LayoutHeadings, lists, landmarks, language, page title, application regions, and media1.2.2, 1.2.5, 1.3.1, 2.4.2, 2.4.6, 3.1.1, 3.1.2, 4.1.2
FormsField labels, field groups, required fields, autocomplete, and error handling1.3.1, 1.3.5, 2.4.6, 2.5.3, 3.3.1, 3.3.2, 3.3.3, 3.3.4, 4.1.2
TablesData and layout tables, header cells, and cell associations1.3.1, 2.4.6
ModalsDialog role and name, focus moving in, staying in, and returning, and closing with the keyboard1.3.2, 2.1.2, 2.4.3, 2.4.11, 2.4.12, 4.1.2
Responsiveness200% zoom, reflow at 320 px, and portrait and landscape orientation1.3.4, 1.4.4, 1.4.10
note

More guided tests will be added soon. This page will list them as they become available.

Prerequisites​

  • The TestMu AI Accessibility Toolkit is installed in Chrome. See Install Toolkit.
  • Your WCAG version and level are set in DevTools Settings. The report checks against these values.

Start a guided test​

  1. Open the page you want to test in Chrome.
  2. Open the Inspect panel and switch to the Accessibility DevTools tab.
  3. Open Assisted Tests and select the test you want to run.
  4. To get AI answers in the Keyboard, Interactive Elements, Images, Layout, Forms, or Tables test, turn on Verify with AI before you start.

Features common to all tests​

  • Verify with AI. In the Keyboard, Interactive Elements, Images, Layout, Forms, and Tables tests, AI gives the first answer to each question when this switch is on. You can change any answer before you finish. Verify with AI will require AI credits. See Credits Management. The Hover and Tooltips, Modals, and Responsiveness tests get their answers from automated checks in the browser and do not use AI.
  • Locate elements. Highlight one element or all elements on the page, or open an element in the DevTools Elements panel.
  • Add missed elements. If the test did not find an element, click it on the page to add it to the test. In the Modals test, this is how you pick the modal or the control that opens it. The Responsiveness test has no elements to add, because its states are fixed.
  • Continue later. The extension saves your progress, so you can close the panel and continue later. The Keyboard test does not save progress, because it walks the live page.
  • Report. Results go into the usual accessibility report, and each issue has a How to fix section. The report follows your WCAG version and level from DevTools Settings.

Product boundary​

Guided tests run in the Accessibility DevTools extension only. They are not available in automation runs, scheduled scans, or the App Scanner. A guided test covers the criteria listed for it and is not a full manual audit of the page.

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