What this checker looks for

It inspects one public URL or pasted HTML for common issues in page structure, images, headings, links, buttons, forms, iframe titles, duplicate IDs, page language, and detectable colour contrast patterns.

Use the accessibility issue library to understand common findings and fixes from the report. See before-and-after accessibility examples for better patterns, then explore printable checklists and copyable templates for handoff and documentation.

What it cannot prove

It cannot prove WCAG conformance, legal compliance, keyboard usability, screen reader clarity, content quality, PDF accessibility, or whether alt text is meaningful in context.

When to use this

Use it before publishing important pages, before sending work to a client, after template changes, or before a qualified accessibility review so obvious issues are not wasting review time.

Use the report well

How to use your accessibility report Turn findings into tickets, client summaries, and manual review checklists. Open the Canadian checklist Turn automated findings into a broader manual review. Use the issue library Open plain-English fixes for common scanner findings. See examples Compare bad, better, and best patterns before fixing code. Read what automation misses Understand where keyboard, screen reader, content, and document review still matter. Generate a statement draft Draft cautious copy after checking the site and known limitations.