Accessibility Audit Report
Turn an automated accessibility scan into a report you can share. The generator runs content and structure checks (language, titles, alt text, labels, autocomplete, link text, headings, landmarks, tables, zoom, media), ARIA validation and keyboard checks, groups the results with severity, WCAG success criterion, occurrences, code examples and how to fix them, and adds a manual checklist for the criteria that need human testing. Download it as Markdown or as a standalone HTML page.
- Encrypted connection
- No sign-up
- Free to use
How to use Accessibility Audit Report
- Enter a URL or paste HTML.
- Click Create audit report.
- Review the issues by group.
- Download and share the report.
Accessibility Audit Report features
Three check groups
WCAG, ARIA and keyboard.
Severity and WCAG
For every issue.
Code examples
The offending elements.
Manual checklist
What tools cannot test.
Markdown and HTML
Download either.
Score
Weighted by severity.
When to use Accessibility Audit Report
- Client audits by agencies.
- Pre-release QA.
- Tickets for development teams.
- Evidence for an accessibility statement.
Accessibility Audit Report FAQ
Is this a full WCAG audit?
No – it covers automated checks and lists the manual tests a full audit needs.
Can I edit the report?
Yes, Markdown and HTML are easy to edit.
Which WCAG version?
WCAG 2.2 level AA.
From scan to action
A report that names the criterion, shows the code and explains the fix turns findings into tickets developers can close.
How it works: a URL is fetched once by our server through a guarded client that only connects to public addresses; the HTML (and, where needed, the stylesheets) is then analysed in your browser as inert text – scripts on the page never run. Pasted HTML is analysed without any request. Nothing is stored.
Automated testing has limits: tools can reliably find missing names, invalid ARIA, broken references, skipped headings and similar code problems, but roughly two thirds of WCAG criteria need human judgement – whether alt text is meaningful, whether focus order makes sense, whether content is understandable. Every result says what still needs manual testing.
The checks follow WCAG 2.2 and WAI-ARIA 1.2, the standards behind the European Accessibility Act, the Americans with Disabilities Act guidance, Section 508 and EN 301 549. Each finding names the success criterion so you can look it up and include it in a report or ticket.
Related tools on this site cover the rest of an accessibility review: the HTML accessibility checker, WCAG contrast checker, accessibility colour analyzer, keyboard navigation checker, ARIA validator, alt text generator, heading structure checker and the accessibility statement generator.
Who it is for: front-end developers checking a release, designers reviewing a component library, content editors, QA testers and agencies preparing accessibility audits for clients. No account, plugin or installation is needed.