How the Walkthrough Works

One check per screen

The walkthrough shows a single accessibility check at a time in a focused, distraction-free layout. Each screen displays:

• The check itself, written as a plain-language question
• A principle chip showing the category of the check: Visual checks, Keyboard & interaction, Content & language, or Page structure. These map to the four WCAG principles (perceivable, operable, understandable, robust)
• Chips for the standards the check belongs to, such as WCAG 2.1 AA 1.1.1 or an EN 301 549 clause
• A progress label showing how much of the audit is complete

Where it helps, the screen also shows device-setting chips (for example, when a check should be tested with VoiceOver or TalkBack) and a thumbnail of the surface's screenshot, which you can click to enlarge.

Guidance on every check

Two sections sit beneath the question:

• Why this matters explains the requirement and who it affects
• How to test gives practical steps for evaluating the check

Some checks add quickstart links for screen readers, and colour contrast checks link to a contrast checker.

Only relevant checks appear

Checks that do not apply to your product are filtered out before the walkthrough starts. The answers you gave during audit setup (for example, whether a surface contains video, audio, or forms) and your product's platform decide which checks appear, so a website audit never asks mobile-only questions.

Time estimates

As you work, the walkthrough estimates how long the remaining questions on the current surface will take, based on your auditing pace. When you revisit an answered question, it shows how long you spent on it.

Some requirements apply to your product as a whole rather than to a single surface. These are handled in a separate, shorter walkthrough; see app-level questions.