How to read a report and what to fix first

Open the report

Open Sites, choose a site and click Open the latest report. Download the PDF with Download PDF, or send the report to a client with a link (see "Links for your client" in the white-label article).

What is in it

• Summary on the first page. The number of problems found, compared with the previous check, and the three most important ones in plain words.
• What to fix first. The problems that block your customers most, with the pages where they occur.
• One section per problem. Each one comes from a rule card: what is wrong, why it matters for the people who use your site, how to fix it and, where we have it, the instruction for your platform. Up to three examples are shown, with the element on the page and, usually, a screenshot.
• Before and after. If an earlier check exists, you see which problems are new and which are gone.
• Appendix for the developer. Selectors and technical details you can pass on as they are.
• Advice beyond the requirements. Findings of level AAA and best practices are shown separately. They are not counted in the problems above.

Severity

Problems are marked critical, serious, moderate or minor. Start with critical and serious: they usually stop a person from finishing a task such as choosing a product or paying.

How to work with it

1. Hand the What to fix first section to your developer, or use the export described in the article on exports.
2. Fix, then press Check now on the site page, or wait for the weekly check.
3. Compare the new check with the old one to confirm the problems are gone.

Every page of the report says that it is an automated check, not a full audit, and not legal advice. A short list of problems does not mean that the site is accessible: automated tools see only part of what a person with a disability meets.