Rendered pages and supplied HTML
Inspect the browser result, preserve selectors and DOM evidence, and compare newly introduced findings against a baseline.
Explore the website accessibility APIOne accessibility testing API for every publishing format.
Send a public URL, HTML, PDF, or DOCX through the same scan lifecycle. AccessPreflight keeps format-specific evidence while normalizing the decisions your workflow needs.
Selected machine-verifiable checks support accessibility work; they do not certify accessibility or legal compliance.
Normalized result contract4 inputs → 1 evidence model
One asynchronous lifecycle, normalized findings, explicit coverage, and unresolved human checks.
The result is designed to be acted on.
A useful preflight result says more than pass or fail. It preserves the tested condition, where it appeared, how certain the outcome is, and which questions software could not answer.
- Outcome
- failed, review_required, or no_detected_failures
- Finding
- Severity, confidence, automation level, and stable identity
- Evidence
- Selector, page, object, relationship, or source location
- Coverage
- Automated, partial, manual, and not-applicable decisions
- Repair
- Source-aware guidance tied to the failed condition
- Lineage
- Profile, rule, engine, hash, and scan timestamp
One contract, source-specific inspection.
Normalization does not flatten the source. Evidence and repair guidance stay native to the format that produced them.
Tagged PDF documents
Pair PDF/UA machine validation with structural locators and a separate queue for reading order, alternatives, and meaning.
Explore the PDF accessibility APIWord source documents
Check OOXML semantics before handoff or conversion and return repair steps that point authors back to the Word source.
Explore the DOCX accessibility APIControls for the workflow around the scan.
Versioned profiles make outcomes interpretable. Baselines, suppressions, gates, signed webhooks, and retention controls make them operational.
PinProfile and rule versions
CompareCurrent scan to a baseline
DecideAllow, warn, or block by policy
RouteSigned webhook or report export
RetainSource content only as configured
Choose the profile your workflow actually needs.
WCAG, EN 301 549, PDF/UA, EU, Slovenian, and ADA Title II profiles remain separate and versioned. Legal mappings are technical preflights, not applicability decisions.
Make accessibility evidence part of the product.
Start with one publishing path, keep the result model stable, and expand without rebuilding the integration.
Check a website freeCreate an account
Automated preflight is not an accessibility certification or legal determination.