Scan web pages, PDF, and DOCX through one API. Catch machine-detectable failures, route human-review items, and preserve traceable evidence before content goes live.
Automated preflight does not replace a complete accessibility audit or legal assessment. See how an accessibility audit is scoped.
Keep one integration while each source receives format-specific checks, locators, and repair guidance. The result stays explicit about which decisions software reached and which still need a person.
Check public URLs, supplied HTML, and static exports before a release reaches production.
Check a websiteBring machine validation, structural extraction, and evidence locators into the upload path.
Explore PDF accessibilityInspect Word semantics before files enter a DAM, client handoff, or publishing queue.
Explore document accessibilityAccessPreflight is designed for the handoff points teams already own: an upload, a pull request, or an evidence request.
Scan a document at upload time, then allow, warn, or block according to the project’s severity policy. Keep the explanation beside the editor instead of in a separate spreadsheet.
block_on: blocker, criticaleditor_review_requiredCompare against a pinned baseline and fail only for new issues that cross the quality gate. Suppressions retain an owner and reason, with optional expiry, instead of becoming invisible exceptions.
quality_gate: failed · 2 new critical findingsKeep the source hash, scan time, selected profile, rule versions, evidence locators, and outstanding human checks in a signed manifest that can be verified independently.
The scan lifecycle is asynchronous and built for retries. Create a scan with an idempotency key, receive 202 Accepted, then retrieve the result or consume a signed webhook.
URL, HTML, PDF, or DOCX.
Finding, evidence, coverage, and repair guidance.
Webhook, baseline diff, report, or quality gate.
POST /v1/scans
Authorization: Bearer ap_live_…
Idempotency-Key: cms-doc-93812-v7
{
"project_id": "prj_…",
"environment": "production",
"asset": {
"type": "upload",
"upload_id": "upl_…"
},
"profiles": ["pdfua-1-machine@1.2.0"],
"options": {
"compare_to_baseline": "scn_…"
}
}id: scn_01J…status: queuedEvery result states how the conclusion was reached. A heuristic never quietly becomes a deterministic failure, and a manual requirement never quietly becomes a pass.
| State | What it means | Example | Result |
|---|---|---|---|
| Deterministic | The tested condition is directly observable and reproducible. | A form control has no accessible name. | A machine-detectable finding with evidence and repair guidance. |
| Heuristic | The signal is useful, but context can change the conclusion. | Alternative text looks suspiciously empty or repetitive. | A risk to review, kept separate from deterministic failure counts. |
| Human review | Software cannot make a responsible outcome decision. | The reading order communicates the intended meaning. | An explicit checklist item that remains open until review. |
Results keep the selected profile version, rule and engine versions, source hash, timestamp, evidence location, and unresolved manual checks together in an Ed25519-signed manifest. Historical results do not silently change when a profile evolves.
Raw source retention defaults to 24 hours after a completed or failed scan. Shorter and zero-retention modes are available where the plan permits, and evidence stores reports and hashes by default. Source files remain inside the configured retention boundary.
review_requiredsha256:c0a4…91e2The short version: AccessPreflight is an integration-ready first pass, not a certificate and not a substitute for people.
No. It runs selected technical checks, reports their coverage, and routes the questions that still need a person. A complete accessibility assessment also considers full services, user journeys, content, applicable law, assistive technology, and human evaluation.
No. The result state is no_detected_failures, not “compliant.” The report still shows which checks ran, reduced coverage, and every outstanding manual requirement.
Public URLs, supplied or uploaded HTML, PDF, and DOCX use the same asynchronous scan lifecycle and normalized finding model. Each format retains evidence locators and repair guidance appropriate to its source.
No. It moves repeatable machine checks earlier so specialists can spend more time on judgment, assistive-technology testing, complex content, and real user experience.
No. AccessPreflight provides evidence and repair guidance. Automatic document remediation and a visual remediation editor are outside the current product scope.
Projects control source retention. The default is 24 hours after a completed or failed scan, with shorter and zero-retention modes available where the plan permits. Evidence archives store reports and hashes by default, not the raw source.
Start with a real workflow, keep human judgment visible, and fix issues before publication.
Automated preflight is not an accessibility certification or legal determination.