POST/v1/scansIllustrative- profile
- wcag-2.1-aa-web@1.2.0
- metadata.release
- 2026.08.14
- gate.mode
- new_findings
202 Accepted · stable scan identity returned
WCAG 2.1 AA accessibility API
Run a stable WCAG 2.1 Level A and AA profile from your release pipeline. The API returns criterion-linked findings, rendered evidence, and the evaluation work automation cannot complete.
For teams maintaining WCAG 2.1 contracts and release baselines
API profile
wcag-2.1-aa-web@1.2.0Illustrative request
202 AcceptedPOST /v1/scans
Idempotency-Key: 2026.08.14
{
"asset": {
"type": "url",
"url": "https://app.example/release-candidate"
},
"profiles": [
"wcag-2.1-aa-web@1.2.0"
],
"metadata": {
"release": "2026.08.14"
}
}queued
id: scn_01J…profile resolved- Input
- Public URL or supplied HTML
- Gate
- New findings only
- Evidence
- Criterion + selector + rendered state
Build a WCAG 2.1 request around the release context you already have.
Tenant-safe metadata and a pinned baseline make the returned finding set immediately routable from CI or a publishing service.
A criterion reference is only the start of the finding.
The normalized result keeps the browser location and automation boundary next to the standards mapping, ready for an issue tracker or code review.
- Identity
- Stable finding ID and fingerprint
- WCAG
- Success criterion and resolved profile
- Browser proof
- URL, selector, observed state
- Confidence
- Deterministic or heuristic
- Coverage
- Automated, partial, or manual
- Repair
- Source-oriented remediation steps
Use one profile from pull request to production check.
The integration changes environment and metadata while the profile meaning and result shape stay stable.
- Pull request
Scan the rendered preview
Create an idempotent scan after the preview URL is ready.
- Release
Apply the baseline gate
Fail only when configured new findings cross the threshold.
- Production
Retain a comparable record
Keep profile, engine versions, source hash, and unresolved review work.
Inspect the policy behind the API profile.
Before WCAG 2.1 AA becomes a production gate, review its source mapping, supported input, automation boundary, and required human checks.
Put the WCAG 2.1 AA API in the path you already own.
Start with one asset flow, pin the profile, and keep evidence and unresolved human work attached to every result.
Check a website freeCreate an account
Automated preflight is not an accessibility certification or legal determination.