European Accessibility Act API

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

API profileeu-eaa-preflight@2026.3
Illustrative request202 Accepted
POST /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"
  }
}
queuedid: scn_01J…profile resolved
Context
Customer-declared jurisdiction and service
Mapping
Directive (EU) 2019/882 technical profile
Boundary
No automatic applicability or conformity decision

Attach an EAA technical preflight to the service architecture.

A route-specific request can identify the digital asset and workflow without asking the API to infer legal scope.

System boundaryCustomer service path
Web

Rendered interaction

Machine findings and browser evidence

Document

Downloadable content

Format-specific preflight

Journey

Complete task

Human evaluation remains required

Context

Service applicability

Declared by the organization

Keep technical preflight separate from the legal conclusion.

The API is designed to preserve this boundary in both the request and the returned evidence.

The API can support

  • Versioned technical requirement mappings
  • Web and document findings with source evidence
  • Corrective-action status and scan history
  • Declared context attached to the record

Qualified review still determines

  • Whether the Act applies to the service
  • Exceptions and disproportionate-burden questions
  • National enforcement and transition details
  • Complete conformity and organizational obligations

Build an evidence record that survives corrective action.

Each rescan can stay connected to the service, profile version, source hash, finding history, and unresolved human work.

Service
Customer-owned external ID and category
Profile
eu-eaa-preflight@2026.3
Mapping
Versioned technical requirement references
History
New, recurring, resolved, or suppressed
Evidence
Source locator, observed state, scan time
Unresolved
Manual and legal-review queue

Inspect the policy behind the API profile.

Before European Accessibility Act becomes a production gate, review its source mapping, supported input, automation boundary, and required human checks.

Put the European Accessibility Act 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.