Rendered interaction
Machine findings and browser evidence
Use the EAA profile to attach a versioned technical mapping and declared service context to supported assets. The API helps route findings and preserve corrective-action evidence; it does not decide scope, exceptions, or legal conformity.
For EU service teams coordinating technical evidence across web and documents
eu-eaa-preflight@2026.3202 AcceptedPOST /v1/scans
Idempotency-Key: service:ecommerce:checkout
{
"asset": {
"type": "url",
"url": "https://shop.example/checkout"
},
"profiles": [
"eu-eaa-preflight@2026.3"
],
"metadata": {
"external_id": "service:ecommerce:checkout"
}
}id: scn_01J…profile resolvedA route-specific request can identify the digital asset and workflow without asking the API to infer legal scope.
Machine findings and browser evidence
Format-specific preflight
Human evaluation remains required
Declared by the organization
The API is designed to preserve this boundary in both the request and the returned evidence.
Each rescan can stay connected to the service, profile version, source hash, finding history, and unresolved human work.
Before European Accessibility Act becomes a production gate, review its source mapping, supported input, automation boundary, and required human checks.
Start with one asset flow, pin the profile, and keep evidence and unresolved human work attached to every result.
Automated preflight is not an accessibility certification or legal determination.