Technical result
- WCAG 2.1 A and AA mapped findings
- Rendered-page evidence and repair guidance
- New, recurring, and resolved classifications
- Explicit automated and manual coverage
ADA Title II accessibility API
Add the Title II web technical target to state or local government publishing and procurement workflows. The API returns WCAG 2.1 A and AA mapped evidence while entity status, exceptions, deadlines, and complete legal assessment remain outside the scan.
For US state and local government teams and the vendors delivering their web services
API profile
us-ada-title-ii-2026@2026.3Illustrative request
202 AcceptedPOST /v1/scans
Idempotency-Key: county-services
{
"asset": {
"type": "url",
"url": "https://county.example/benefits/apply"
},
"profiles": [
"us-ada-title-ii-2026@2026.3"
],
"metadata": {
"entity": "county-services"
}
}queued
id: scn_01J…profile resolved- Technical target
- WCAG 2.1 Level A + AA mapping
- Workflow
- Government page or vendor release
- Boundary
- Entity context and legal assessment remain manual
Put the technical target into the vendor release gate.
A project can block newly introduced machine failures and still preserve the manual evaluation needed before the government service is accepted.
Illustrative workflow decision
new WCAG 2.1 AA mapped failuresquality_gate_failed- Entity
- county-services · customer declared
- Profile
- us-ada-title-ii-2026@2026.3
- Baseline
- accepted-release-18
- Vendor action
- Repair new blockers before handoff
Put technical preflight into the remediation and release cadence.
Milestones keep the accessibility target, regression gate, and human validation visible as part of delivery rather than a one-time scan.
- Baseline
Record existing technical debt
Pin the starting evidence set.
- Every release
Stop new regressions
Run the configured profile on the candidate.
- Remediation
Verify repaired findings
Preserve resolved fingerprints and proof.
- Service review
Evaluate complete tasks
Keep human testing outside the machine verdict.
Name the legal boundary in the integration itself.
The Title II profile is a technical mapping that can support a compliance program; the response is not a legal determination.
Legal and program review
- Covered entity and content context
- Applicable compliance date and exceptions
- Complete service, document, and mobile scope
- Overall legal and accessibility conclusion
Inspect the policy behind the API profile.
Before ADA Title II becomes a production gate, review its source mapping, supported input, automation boundary, and required human checks.
Put the ADA Title II 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.