Website accessibility audit
A website accessibility audit is a structured review against WCAG that includes human testing. An automated scan is the machine-testable slice of that work. Complience.app is that slice: axe-core on a Playwright load, then recrawls. It is not a full audit and not a legal certificate.
Start with the machine slice
Paste a public URL. axe-core flags what a machine can see. A person still tests the keyboard and the screen reader. This is not an audit certificate.
What is a website accessibility audit?
An audit samples templates and flows, runs automated rules, then adds keyboard and screen-reader notes, severity, and a retest plan. Many firms also produce an ACR or VPAT. Complience.app does not replace that document. For the machine pass alone, use the website accessibility checker.
What a WCAG audit still needs
A WCAG audit is that same review with the standard named. The WebAIM Million found detectable WCAG 2 failures on 95.9% of the top 1,000,000 home pages in 2026. That sample is automated detection, the same class of pass a scan does. A website accessibility audit still needs a person on the keyboard and a screen reader.
What belongs in an audit
Scope, sample of templates and flows, automated rules, keyboard and screen-reader notes, severity, and a retest plan. The checker finds missing labels so the human review is not spent there. The audit still has to judge meaning, order, and real assistive-technology use.
Where the scanner fits
Run a scan first. Keep the schedule on after the audit so new pages do not undo the work. Cookie pre-consent sits in the same evidence pack if you sell privacy retainers too. Check a public URL.
