An accessibility API for every supported policy profile.
Choose the standard or legal mapping your workflow needs, send its versioned profile ID with the asset, and receive normalized findings, source evidence, coverage, and unresolved human work.
Legal profiles are technical preflights. The API does not decide applicability, exceptions, certification, or complete conformity.
One asynchronous lifecycle, normalized findings, explicit coverage, and unresolved human checks.
Web standards
Rendered-web profiles for engineering gates, platform checks, and technical acceptance.
WCAG 2.1 AA accessibility API
Add versioned WCAG 2.1 AA checks, evidence, manual-review coverage, and new-issue quality gates to web publishing and CI workflows through one API.
wcag-2.1-aa-web@1.2.0WCAG 2.2 AA accessibility API
Scan web pages with a pinned WCAG 2.2 AA API profile and keep 2.2-specific coverage, findings, evidence, and human evaluation in the release record.
wcag-2.2-aa-web@1.2.0EN 301 549 web accessibility API
Use an EN 301 549 V3.2.1 web profile through the AccessPreflight API, with clause mappings, WCAG references, technical evidence, and coverage boundaries.
en-301-549-v3.2.1-web@1.2.0Document standards
Upload-based profiles for PDF, DOCX, document generation, and publishing systems.
EN 301 549 document accessibility API
Preflight PDF and DOCX files through an EN 301 549 V3.2.1 non-web document API profile with format-native evidence and author-ready repair routing.
en-301-549-v3.2.1-nonweb-document@1.2.0PDF/UA-1 validation API
Automate PDF/UA-1 machine validation through an upload API while preserving validator versions, structural evidence, repair guidance, and manual-review requirements.
pdfua-1-machine@1.2.0PDF/UA-2 validation API
Use a dedicated PDF/UA-2 machine-validation API profile for PDF 2.0 documents, with pinned versions, format-aware evidence, and explicit human-review boundaries.
pdfua-2-machine@1.2.0Legal mappings
Effective-dated technical profiles with declared context and explicit legal boundaries.
European Accessibility Act API
Add an EAA technical-preflight API profile to supported web and document workflows, with customer-declared context, versioned mappings, evidence, and legal boundaries.
eu-eaa-preflight@2026.3EU Web Accessibility Directive API
Run a current EU Web Accessibility Directive technical API profile for public-sector web and supported documents, with pinned history and sampling-ready evidence.
eu-wad-current@2026.3Slovenia ZDPSI accessibility API
Use a current Slovenia ZDPSI technical-preflight API profile with declared service context, supported web and document scans, and national mapping lineage.
si-zdpsi-current@2026.3Slovenia ZDSMA accessibility API
Integrate a current Slovenia ZDSMA technical API profile into public-sector web and document publishing, with national mapping, repeat scans, and bounded evidence.
si-zdsma-current@2026.3ADA Title II accessibility API
Use an ADA Title II technical API profile for state and local government web content, with WCAG 2.1 AA mapping, release evidence, and entity-context boundaries.
us-ada-title-ii-2026@2026.3EAA e-commerce accessibility API
Add EAA e-commerce page preflights and complete-journey checkpoints to checkout delivery workflows with a dedicated, versioned accessibility API profile.
eu-eaa-ecommerce-service@2026.2Section 508 compliance testing API
Collect versioned Section 508 evidence for supported website, HTML, PDF, and DOCX assets and route it into product procurement and ACR review workflows.
us-section-508-ict@2026.2UK public-sector accessibility testing API
Run current UK public-sector website and document preflights through an API, with WCAG 2.2 AA evidence, sample metadata, and statement-review boundaries.
uk-psbar-current@2026.2UK Equality Act accessibility API
Collect WCAG 2.2 technical barrier evidence through an API for a customer-declared UK Equality Act digital-service context and route open adjustment review.
uk-equality-act-digital-context@2026.2Change the profile, not the integration.
Every supported profile travels through the same asynchronous scan lifecycle. Format-native evidence stays intact while the workflow receives one stable result contract.
Read the API documentation- Create
- POST /v1/scans with an idempotency key
- Pin
- Requested and resolved profile versions
- Inspect
- Findings, coverage, evidence, and repair
- Compare
- New, recurring, and resolved findings
- Route
- Signed webhook, report, or quality gate
Choose the policy. Keep the API contract stable.
Start with the profile already named in your workflow and keep its exact version with every finding and review task.
Automated preflight is not an accessibility certification or legal determination.