Web Accessibility Audit

Find accessibility problems in a page before your users do.

Private by design

Your inputs stay on your device and are not sent to our servers. Optional usage analytics does not receive your files or tool inputs.

Web Accessibility Audit

axe-core checks on pasted HTML

HTML

Accessibility report

The result appears here.

Options

WCAG levelAA is what most laws and procurement rules ask for.

Include best-practice rules

Extra advice such as landmarks and heading order, beyond WCAG.

Mention checks that need a person

This runs axe-core, the open-source accessibility engine from Deque, on the HTML you paste. It checks colour contrast, ARIA attributes, form labels, image text, page language, landmarks and more, and links each problem to the WCAG success criterion it relates to.

Include your CSS in a style tag, because linked stylesheets and images are not loaded.
Fix critical and serious problems first.
Automated checks catch only part of the issues: also tab through the page and try a screen reader.

Your HTML is placed in a hidden sandboxed iframe with no access to this site and a policy that blocks every network request and any script in your page. Only axe-core 4.10 (MPL-2.0, used unmodified) runs inside it. Rules are chosen by WCAG 2.0, 2.1 and 2.2 level. Nothing is uploaded.

Preparing tool

How to use Web Accessibility Audit

Paste your page's HTML, or open an .html file.
Pick the WCAG level and which rules to include.
Read each problem with its WCAG reference, the element and how to fix it, then copy the report.

Read the detailed guide →

What are the limits of Web Accessibility Audit?

Only the HTML you paste is checked: nothing is fetched, and scripts in it do not run. Automated tools find roughly a third of accessibility problems, so also test with a keyboard and a screen reader. Styles must be inside the HTML (style tags or inline). Your HTML stays on your device.