Canonical JSON
Paginate, filter, map, and retain a versioned machine-readable artifact.
Accessibility reporting API with traceable evidence
The accessibility reporting API gives machines a canonical JSON artifact and people a keyboard-accessible HTML report built from the same result. Both retain the technical context needed to understand what ran and what remains unresolved.
For teams exporting accessibility results into dashboards, tickets, clients, and evidence stores
Illustrative report manifest
IllustrativeJSON
/reports/jsoncanonicalHTML
/reports/htmlaccessibleCoverage
/coverage12 manualDiff
/diff?baseline=scn_01H…availableEvidence manifestprofile + engine + source hash + report hash
- Machine
- Versioned JSON schema
- People
- Semantic, keyboard-accessible HTML
- Integrity
- Source · engine · profile · report hashes
Send one evidence record to engineering, review, and audit systems.
Different consumers need different views, but every artifact should resolve to the same scan, profile, and finding identities.
- Scan result
- Finding fingerprints
- Coverage ledger
AccessPreflightEvidence manifest
- Issue tracker
- Specialist review
- Archived report
Choose the technical profile behind this capability.
A report should identify the profile, standard version, coverage, and rule lineage behind its findings. That context makes later review possible.
Serve the same evidence to three different workflows.
Reports are delivery forms for one result, not separate sources of truth with drifting counts or labels.
Accessible HTML
Navigate semantic sections, filters, and finding deep links without losing information.
Manifest and hashes
Preserve source, execution, suppression, and report integrity metadata.
Report the coverage boundary beside the result.
A clear automated result still includes the checks that were partial, not applicable, reduced by missing resources, or reserved for people.
Included in the report
- Machine-detectable findings and evidence
- Resolved profiles and engine versions
- Coverage classifications and reasons
- Suppression and quality-gate records
Not implied by the report
- Accessibility certification
- A complete WCAG or EN 301 549 audit
- A legal applicability decision
- Automatic remediation of the source
Give machines and people the same evidence trail.
Generate a report from a real scan, keep its manifest with the artifact, and use the API when reports need to enter another system.
Check a website freeCreate an account
Automated preflight is not an accessibility certification or legal determination.