Automated accessibility governance platforms are marketed as full compliance systems, but nearly all of them skip the one step that determines WCAG conformance: a manual audit conducted by trained auditors. Scans flag approximately 25% of issues. The remaining 75% require human evaluation against WCAG success criteria. A governance platform without a manual audit component is monitoring surface signals, not measuring conformance. Organizations relying on these platforms to prove compliance are working from incomplete data.
| Activity | Coverage Reality |
|---|---|
| Automated scanning | Detects approximately 25% of WCAG issues on scanned pages |
| Dashboards and reporting | Displays scan data, not conformance status |
| Manual audit | Rarely included; required to determine WCAG conformance |
| Remediation tracking | Only as useful as the audit data feeding it |
| ACR or VPAT generation | Requires manual audit findings, not scan output |
What a Governance Platform Actually Does
Governance platforms centralize accessibility activity across an organization. They pull scan data, assign issues to owners, produce reports for leadership, and give teams a place to manage work.
That is useful. It is also incomplete. The data feeding the dashboard comes from automated scans, which identify approximately 25% of WCAG issues on a given page. The other 75% are visible only through human evaluation against each success criterion.
A dashboard filled with scan output looks thorough. It is not the same as conformance.
Why Manual Audits Are Required for Conformance
WCAG 2.1 AA and WCAG 2.2 AA include success criteria that scans cannot evaluate. Meaningful alt text, correct heading structure in context, keyboard operability across custom widgets, focus order, form error messaging, and screen reader announcements all require a person to work through the interface.
A manual audit produces a report that identifies each issue, maps it to the relevant success criterion, and provides remediation guidance. This is the document that supports an ACR, informs a remediation plan, and stands up as evidence of due diligence.
An accessibility audit against WCAG is the only way to determine conformance. No scan output substitutes for it.
What Happens When the Audit Is Missing?
Organizations working from scan-only governance platforms often believe they are further along than they are. Dashboards show green. Issue counts trend down. Leadership sees progress.
Then a demand letter arrives, or a procurement team requests an ACR, or a screen reader user reports issues that never appeared in any report. The scan never identified those issues. They were never on the dashboard.
Legal risk does not decrease because a scan looks clean. It decreases when the actual WCAG issues, including the 75% scans cannot detect, are identified and remediated.
How Should Governance and Audits Work Together?
Governance and auditing are not competing activities. They belong together in a well-designed program.
The audit produces the ground-truth data. The governance layer organizes and tracks the work of remediating that data. Scans can supplement between audits to catch regressions on well-understood patterns, but they never replace the audit itself.
Accessibility Tracker Platform is built around audit data, not scan data. Issues come from a manual audit report, get prioritized using Risk Factor or User Impact prioritization formulas, and move through remediation with team visibility. Scanning exists inside the platform as a separate monitoring feature, not as a substitute for evaluation.
What to Look for in a Real Governance Approach
When evaluating a governance platform, the first question is where the underlying issue data comes from. If the answer is scans, the platform is measuring a fraction of what matters.
Audit-based issue data: The platform accepts or integrates manual audit findings, not only scan output.
Prioritization logic: Issues can be ranked by risk or user impact, not by scan severity labels.
Documentation output: The platform supports producing an ACR, progress reports, and audit-anchored records.
Separation of scan and audit: Scans are a monitoring layer, not a conformance claim.
Accessible.org has consistently taken the position that conformance is a manual determination. Governance platforms that treat it as an automated one are marketing a feature the technology cannot deliver.
FAQs
Can a governance platform prove WCAG conformance without a manual audit?
No. Conformance is determined by evaluating every applicable success criterion, and scans cover approximately 25% of them. A governance platform without manual audit data cannot support a credible conformance claim or a defensible ACR.
Do automated scans have any role in an accessibility program?
Yes, as a monitoring layer between audits. Scans can catch known-pattern regressions quickly, which is valuable. They are not a remediation program and cannot verify that fixes meet WCAG requirements.
How often should a manual audit be conducted alongside governance tooling?
Most organizations benefit from an annual audit, with additional audits after significant redesigns or new feature launches. Between audits, governance tooling tracks remediation and monitors for regressions. More on this is covered in the accessibility services overview.
What does an audit report include that a scan report does not?
An audit report identifies each issue with its WCAG success criterion, location, description, and remediation guidance, written by an auditor who evaluated the interface directly. Scan reports list detected patterns without context, mapping, or the 75% of issues scans miss entirely.
Governance without an audit is organization without measurement. The tooling can be excellent, but the data has to be real.
Contact Accessible.org to request an audit quote.
