Stable fingerprint
Track the same issue across repeat scans and engine upgrades.
Accessibility testing API for web and documents
The AccessPreflight accessibility testing API creates one asynchronous scan for a rendered page, supplied HTML, PDF, or DOCX. Its stable result contract preserves the evidence each format needs.
For platforms that need one pre-publication integration, not four isolated checkers
One request model, four inputs
IllustrativeURL
asset.type: urlDOM + browser stateHTML
asset.type: htmlMarkup + resourcesPDF
upload: .pdfPage + PDF objectDOCX
upload: .docxOOXML part + nodeResultnormalized finding schema
- Create
- POST /v1/scans
- Inputs
- URL · HTML · PDF · DOCX
- Outputs
- Findings · coverage · reports · diff
Use the same contract at each publishing checkpoint.
The asset changes from preview URL to generated document, but the decision lifecycle remains recognizable to every integration.
- Create
Identify the asset
URL, HTML, PDF, or DOCX
- Resolve
Pin profiles and engines
Stable meaning before work begins
- Inspect
Collect native evidence
Browser, PDF, or OOXML locators
- Route
Return the decision
Webhook, report, or pull response
Normalize decisions without flattening evidence.
A selector is useful for HTML; a PDF object reference is useful for a tagged document. Both belong to one finding contract with format-native locators.
Native locator
Keep DOM, PDF, or OOXML evidence close to the observed condition.
Automation level
Distinguish deterministic checks, heuristics, and required human review.
Choose the technical profile behind this capability.
The request selects a versioned testing profile for the source. That choice controls rule coverage without changing the normalized result contract.
A preflight result is not a certification.
The API narrows technical work and preserves evidence. It does not decide legal scope, meaning, reading-order quality, or complete accessibility.
The API can establish
- Machine-detectable failures
- Configured profile and engine versions
- Observed evidence and repair guidance
- New, recurring, and resolved fingerprints
People still establish
- Whether a law applies to the service
- Whether alternative text is meaningful
- Whether reading order and interaction are usable
- Whether the complete experience conforms
Bring one preflight contract into every publishing path.
Send one public page or document through the free workflow, then use the same asynchronous contract for the next publishing source.
Check a website freeCreate an account
Automated preflight is not an accessibility certification or legal determination.