EAA e-commerce accessibility API
Scan stable states across an online consumer-contract journey with the dedicated EAA e-commerce profile. The API returns page evidence and a bounded review record; your service team still evaluates payment providers, authentication, confirmation, cancellation, support, and the complete customer path.
For EU commerce platforms and service teams owning the path from offer to contract
eu-eaa-ecommerce-service@2026.2202 AcceptedPOST /v1/scans
Idempotency-Key: checkout:delivery-details
{
"asset": {
"type": "url",
"url": "https://shop.example/checkout/delivery"
},
"profiles": [
"eu-eaa-ecommerce-service@2026.2"
],
"metadata": {
"journey_step": "checkout:delivery-details"
}
}id: scn_01J…profile resolved- Profile
- Dedicated EAA e-commerce service mapping
- Unit
- Rendered page state plus journey metadata
- Decision
- Technical gate with open service review
Join page scans into one commerce journey record.
The API receives stable page states from delivery systems and returns comparable evidence to engineering and complete-journey review.
- Product preview
- Checkout state
- Payment handoff
- Release gate
- Journey ledger
- Manual review queue
Give every checkout state a durable identity.
The useful API contract connects a scan to the service path and release that produced it, rather than leaving disconnected page reports.
- Profile
- eu-eaa-ecommerce-service@2026.2
- Journey
- consumer-contract:standard-checkout
- Checkpoint
- checkout:delivery-details
- Variant
- en-EU · desktop · guest
- Baseline
- release-2026.08.2
- Open review
- Payment → confirmation → cancellation
Fail the page regression without passing the whole service.
The delivery system can make a deterministic engineering decision while the result still communicates the remaining journey boundary.
review_required- New blockers
- 0 deterministic findings
- Recurring work
- 2 assigned findings
- Completed steps
- Offer · basket · delivery
- Required review
- Payment · confirmation · support
Inspect the policy behind the API profile.
Before EAA e-commerce becomes a production gate, review its source mapping, supported input, automation boundary, and required human checks.
Put the EAA e-commerce 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.
Automated preflight is not an accessibility certification or legal determination.