Practical digital skills

Interpret an automated accessibility report

Define tested pages and states, inspect warnings and add keyboard journeys and a content review.

Step-by-step guideUpdated
Follow the method ↓
Editorial illustration of a review of digital tasks
Generic illustration of a content review.

The answer in 30 seconds

An automated report describes what a tool could inspect in a particular state. It can identify barriers, but it does not automatically observe every journey or judge every piece of content.

Retain tool, date, pages and tested states. For each warning, find the element and rule. Add manual checks of keyboard use, meaningful labels, text alternatives and understandable errors.

Examples to adapt

An image has an alt

Attribute presence does not establish that the text communicates useful information. Review it in the page’s context.

A form has no initial errors

A loading-time report can miss invalid-input states. Use fictional data without sending a real request.

Follow the method

  1. 1
    Define scope

    List representative pages and useful states: open menu, invalid form or expanded content. A homepage check does not describe the whole site.

  2. 2
    Read a specific warning

    Record selector, rule and explanation. Distinguish confirmed errors from points requiring human review. Keep a screenshot when it helps reproduction.

  3. 3
    Try a journey

    Without a mouse, find navigation, open a section and use a test form. Check focus order, labels and the ability to return.

  4. 4
    Correct and repeat

    Fix the shared component when multiple pages are affected. Repeat the same check and the affected journey. Record remaining human checks.

A checklist to keep

Use these checks to record your observations. They are a reading aid, not an automatic assessment.

Interpret an automated accessibility report: checklist
CheckWhat to examineAction
ScopePages, states and deviceRecord
WarningElement and ruleInspect
KeyboardFocus, order and actionsTry
MeaningLabels, alt and errorsReview
RepeatSame check after correctionCompare

Download the CSV checklist

Free, no sign-up. UTF-8 text with semicolon-separated columns.

What to check

A high score is not a conformance statement.

No automated warning does not guarantee no barrier.

Zoom and keyboard checks add observations without replacing a full evaluation.

Common questions

Can I announce accessibility after one test?

Describe the performed check and its limits. A conformance statement requires appropriate scope and methodology.

Must I install several tools?

Choose a tool for the task and add checks it does not cover. More scores alone do not broaden scope.

Sources and documentation

Documentation consulted on . Examples are illustrative; interfaces and results may change.

Reference record for this resource

Identify the publisher, official destination and practical checks before using the service.

Read the W3C Web Accessibility Initiative record →

Continue exploring

All English guides →