Machine-verifiable failure
The report identifies the rule, object or structure path, page context, and repair direction.
PDF accessibility
PDF accessibility testing beyond the page preview.
Inspect tags, metadata, relationships, annotations, forms, and other machine-testable PDF conditions. Keep reading order, alternative quality, table meaning, and usability in a separate human review queue.
A technical result is evidence for accessibility work. It is not certification of the complete document.
Inside the file
Find structure a page preview cannot show.
PDF accessibility depends on the relationship between visible content, content objects, the tag tree, document properties, and interactive annotations. The scan keeps those layers connected.
- Document
- Title, default language, tagged status, and structural metadata.
- Structure
- Headings, lists, figures, tables, notes, and content associations.
- Interaction
- Links, annotations, form controls, names, roles, and required properties.
- Review
- Reading sequence, alternative meaning, table comprehension, and task use.
Result design
Do not hide uncertainty inside one compliance score.
A useful result distinguishes a proven failure from a suspicious condition and a check that still needs a person.
Evidence that needs interpretation
The file exposes a relevant property, but meaning or suitability cannot be decided from syntax alone.
Review required
The result states the question, suggested procedure, and place in the document without inventing a pass.
Test the version people will download.
Keep the scan tied to the final file identity, engine and profile versions, and review date. If the PDF changes, create a new result and compare it with the earlier evidence.
Put a real PDF through the preflight.
Create a free workspace to scan PDFs and organize technical findings, manual checks, repairs, and retests.
Check a website freeCreate an account
Automated preflight is not an accessibility certification or legal determination.