An accessibility audit report and a compliance report serve different purposes. An audit report is a technical document that identifies specific WCAG issues found across a digital asset, written for the team that will fix them. A compliance report is a higher-level document that states how an asset measures against a standard or regulation, often shared with buyers, regulators, or leadership. Audit reports power remediation work. Compliance reports communicate status. The two are related but not interchangeable.
| Attribute | Audit Report | Compliance Report |
|---|---|---|
| Purpose | Identifies WCAG issues for remediation | Communicates status against a standard or law |
| Audience | Developers, designers, project teams | Buyers, procurement, legal, leadership |
| Content | Issue list, severity, location, recommendation | Conformance claim, scope, methodology |
| Example | Detailed WCAG 2.1 AA audit report | ACR, VPAT, internal status memo |
What is an Accessibility Audit Report?
An accessibility audit report is the deliverable from a manual evaluation of a website, web app, mobile app, or software against the Web Content Accessibility Guidelines. It identifies every WCAG issue an auditor finds, where it occurs, and how to fix it.
The report is built for the people doing the work. Developers, designers, and content owners use it as a working document during remediation.
A strong audit report includes the WCAG version and level (typically 2.1 AA or 2.2 AA), the scope of pages or screens evaluated, the methodology, and a structured issue list. Each issue entry maps to a specific success criterion, includes the affected element or page, and describes the recommended fix.
Audits identify issues. Scans only flag approximately 25% of issues, which is why a manual audit is the only way to determine WCAG conformance.
What is a Compliance Report?
A compliance report communicates how a digital asset measures against a legal or technical standard. It is written for an external or executive audience, not for the engineering team.
The most common compliance report in the accessibility space is the Accessibility Conformance Report (ACR), generated from a VPAT. An ACR states, success criterion by success criterion, whether a product supports, partially supports, or does not support each requirement. Buyers, procurement teams, and government agencies request ACRs during purchasing.
Other compliance reports exist as well. Internal compliance memos document status for leadership. Regulatory reports tied to laws such as ADA Title II or the EAA confirm what has been done to meet obligations. These documents summarize position. They do not list every individual issue or fix.
How Do the Two Documents Connect?
A compliance report is only credible if it sits on top of a real audit. The audit identifies the issues. Remediation addresses them. The compliance report then reflects the current state.
For example, an ACR produced without an underlying audit is a red flag. The conformance claims have no evidence behind them. Accessible.org always pairs ACRs with a full WCAG audit so the report reflects what was actually evaluated, not what was assumed.
VPAT details and the audit relationship are covered further here.
Who Reads Each Report?
Audit reports go to the people who can act on them. That includes front-end developers, designers, content editors, QA, and the project manager tracking remediation across a portfolio.
Compliance reports go to people who need to know the status. Procurement officers reviewing a SaaS purchase. Legal teams confirming ADA or EAA position. Executives making decisions on risk. A buyer asking for an ACR is not asking for the audit. They want the summary document that confirms where the product stands.
Which One Do You Need?
If you are working toward WCAG conformance and need to fix issues, you need an audit report. It is the working document for the entire remediation effort and can be used to track issues inside a project management platform.
If a buyer, agency, or partner is asking for documentation of your product’s accessibility status, you need a compliance report, most often an ACR. The ACR should be backed by a recent audit so the claims hold up under scrutiny.
Many organizations need both. The audit drives the work. The compliance report communicates the result. Accessible.org clients typically start with an audit, complete remediation with validation, and then receive an ACR that reflects the post-remediation state.
Frequently Asked Questions
Can a compliance report replace an audit report?
No. A compliance report summarizes status. It does not contain the issue-level detail developers need to make fixes. An ACR without an audit behind it has no technical foundation.
Is an ACR the same as a compliance report?
An ACR is the most common type of compliance report in digital accessibility. Other compliance documents exist, including internal memos and regulatory submissions, but the ACR is the standard for product accessibility and procurement.
How long is an audit report valid?
An audit report reflects the state of the asset at the time of evaluation. After significant code or content changes, the report loses freshness and a re-audit is recommended. The same applies to an ACR built on top of the audit.
Do you get an audit report and an ACR together?
From Accessible.org VPAT services, yes. The audit report is delivered to the team for remediation, and the ACR is issued as the compliance document. Both reflect the same evaluation work.
For a quote on a WCAG audit, ACR, or both, Contact Accessible.org.
