Name what was tested
Record URLs, files, profile versions, viewports, and exclusions. A single page result stays a single page result.
Accessibility audit
Test websites and documents with versioned technical profiles, then route the questions that require a person. Each result keeps scope, evidence, repair guidance, and retest history together.
Technical testing supports an audit. It does not make a legal determination or replace user research.

A reviewable audit
A bare score hides coverage. AccessPreflight records the tested rule, source location, engine, confidence, and automation level so another reviewer can reproduce the finding.
Record URLs, files, profile versions, viewports, and exclusions. A single page result stays a single page result.
Keep DOM selectors, PDF object references, DOCX paths, screenshots, and rule identities with the finding.
Reading order, alternative quality, task completion, and legal scope remain visible until the right reviewer decides them.
Audit report
Normalize the decision while keeping source-specific evidence. A web selector, PDF structure path, and DOCX package location should not be flattened into the same vague instruction.
AccessPreflight reports machine-detected failures and no-detected-failure results without converting untouched success criteria into passes. Manual checks remain part of the work, not a footnote.
Create a free workspace for web, PDF, DOCX, and HTML scans, or book a demo to review a larger audit workflow.
Automated preflight is not an accessibility certification or legal determination.