webtoolshelper
Website Tools

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
Analyse pasted HTML instead

Runs the automated WCAG, ARIA and keyboard checks and builds a report you can download as Markdown or HTML. Automated testing finds only part of the barriers – the report lists what still needs manual testing.

How to use Accessibility Audit Report

  1. Enter a URL or paste HTML.
  2. Click Create audit report.
  3. Review the issues by group.
  4. 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.

Can this report be used as proof of WCAG conformance?

No. It documents automated findings and lists what still needs manual testing. A conformance claim requires a full manual audit of all criteria.

How often should I audit my site?

After every larger release and at least once or twice a year, plus whenever a new template or component is introduced.

Who should fix the findings?

Most findings are code issues for developers; alt text and link wording are content issues for editors. The report notes the type so you can assign them.

Accessibility Statement Generator Publish an honest accessibility statement for your website or app. Choose the… Keyboard Navigation Checker Find keyboard barriers before your users do. The checker lists the tab order with… ARIA Validator Catch ARIA mistakes that break screen-reader output. The validator checks every… Website Quality Audit Generator Get a quick, broad health check of any page. The generator reads the HTML and…

From scan to fix list

A report that names the criterion, shows the code and explains the fix turns findings into tickets developers can close.

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.

An accessibility report is useful when developers can act on it directly. Each finding is grouped by severity and lists the WCAG success criterion, how often it occurs, a code example and how to fix it, so it can be copied into an issue tracker as it is.

The scan combines content and structure rules, ARIA validation and keyboard checks. Because roughly two thirds of WCAG criteria need human judgement – whether alt text is meaningful, whether focus order makes sense – the report adds a manual checklist for those criteria instead of claiming full coverage.

Download the report as Markdown for your tracker or as a standalone HTML page to share with clients or management. Re-run it after fixes to show progress, and date each report so it is clear what state of the site it describes.

Other useful tools