A CLEARER PATH TO RELEASE
Check your page.
Know what to fix.
Find accessibility issues, review the evidence, and take a useful report back to your team.
01 / SCAN
Start with a page
Checking shared capacity...
Updates every minute while this page is visible. Capacity is not reserved; personal and network limits still apply.
Ready when you are.
What this scan covers
Automated WCAG 2.1/2.2 A/AA checks on the initially loaded page. Serious and critical findings fail the gate. Other findings and unresolved checks warn.
This does not scan every linked page or test signed-in journeys. People still need to review accessibility.
02 / REVIEW
Your report will appear here
Evidence you can act on.
See the affected elements and fix guidance, then download a professional PDF to share.
Your account and reports
You can scan as a guest without signing in.
Use your work or personal email—Outlook, Gmail or another provider. We’ll send a one-time code. No password needed. Your reports stay private to you.
My reports
Latest 10 reports, saved for up to 30 days. Viewing and downloading do not use scans. A rescan uses your daily page allowance.
Search your latest 10 saved reports. Names are private labels and do not change the original reports.
Compare reports
Choose two completed scans of the same pages. Matching uses rule and element location; page changes can affect the comparison. “No longer detected” needs human verification.
03 / UNDERSTAND
What does my result mean?
These labels describe the selected pages in this automated scan, not your whole website. Even a PASS needs human accessibility testing.
- PASS
- The scan completed without findings that trigger the quality gate and without unresolved automated checks. This does not prove the page is fully accessible.
- WARN
- The scan completed with lower-severity findings or checks a person needs to review. Read each item and verify it on the page.
- FAIL
- The scan completed and found at least one serious or critical issue. Start with those findings, make a fix, and scan the same page again.
- INCOMPLETE
- The scan could not finish reliably, for example because resources could not load. Findings may be missing. Read the limitation, retry when appropriate, or report the problem. This is not a passing result.
Manual review and finding counts
Needs manual review means the scanner could not decide whether a check passes or fails. It is not a confirmed violation. Inspect the element and follow the report guidance.
Rule violations count types of issue; element occurrences count affected elements within each rule. One rule can affect many elements, and an element can appear under more than one rule.
For example, one contrast rule affecting 20 elements means 20 places to inspect, not 20 different types of problem. Keyboard navigation, meaningful text alternatives and other human checks are still needed for every result.
What should I do next?
- Download the PDF for a readable summary. Developers can also use the JSON, Markdown or HTML files.
- Start with critical and serious findings. Expand the evidence to locate the affected elements.
- Complete the manual checks, make changes, and rescan the same page to compare results.
- Tell us which parts of the report helped and which were unclear.
This scanner checks the initial state of each selected public page. It does not crawl the entire site, test signed-in journeys, or certify WCAG or Section 508 compliance.