User guide

Getting started

1. Run a free check

Enter your homepage address in the box on the home page. In about a minute you get a score out of 100, the checks that passed and failed, and the first three issues. No account is needed. The report says which engine ran it; today hosted scans read your page's HTML, and a real-browser engine is rolling out.

2. Get the full report

Enter your email on the report to receive every finding, grouped by WCAG principle, with the failing elements, how to fix each one and a PDF. You can opt in to a monthly re-scan digest and unsubscribe at any time.

3. Create an account and add your site

Create an account, then add your site in the dashboard. Each site gets a site key, which the visitor panel and the API use.

4. Work the fix queue

Open the fix queue. Each finding has a proposed code change, a label, a contrast value, an accessible name or alt text. Approve or reject each one, then ship approved changes in your own code or hand them to your developer.

5. Rescan and compare

Rescan from the dashboard. Fixed items drop off, regressions show up, and your scan history becomes your record of effort. Free reports can be re-run every few hours.

6. Publish a statement

Generate an accessibility statement from your real results and publish it on your site. Edit the contact details and known limitations before you publish; a statement is your commitment, and it should be true.

What a scan cannot tell you

Automated checks cover part of WCAG. Meaningful alt text, sensible reading order, accurate captions and whether a keyboard user can complete your checkout still need a person. Your report lists these items.