Page and tag evidence
Use validator rules, structure elements, object references, and MCIDs when available.
Document accessibility API for PDF and DOCX
The document accessibility API creates one preflight boundary in front of your CMS, DAM, PIM, or generation service. It routes PDF and DOCX to format-native workers while returning one decision and evidence model.
For content platforms that cannot maintain separate Word and PDF checking stacks
One upload boundary, native document workers
IllustrativePDF
application/pdfPDF/UA + tag/object evidenceDOCX
OOXML packageStyles + parts + relationshipsResultone gate + finding + report contract
- Upload
- Presigned · single-purpose · expiring
- Safety
- Signature, size, parse, and archive limits
- Retention
- Explicit source-retention setting
Place the check before the publish action.
The platform can keep its own document state machine while AccessPreflight handles upload validation, asynchronous workers, and evidence.
- Receive
Hold the candidate document
Create an upload with media type, size, SHA-256, and source-retention choice.
- Preflight
Route by detected format
Run PDF or OOXML-native layers under the selected versioned profiles.
- Publish
Apply the returned decision
Allow, warn, block, or route review with finding and report links.
Keep the native proof each format needs.
Normalization aligns workflow fields and outcomes. It does not pretend that a PDF object and a Word paragraph are the same locator.
OOXML source evidence
Use package parts, paragraphs, styles, relationships, tables, and drawings.
Shared finding contract
Use stable identity, severity, confidence, coverage, repair, and gate fields.
Choose the technical profile behind this capability.
PDF and DOCX inputs can share a workflow while using format-appropriate technical profiles. The returned coverage shows which rules ran for each file.
Compare document versions without losing format-native evidence.
The normalized delta stays useful to publishing systems while PDF and DOCX locators remain attached to the changed finding.
- Baseline
- Asset version 7
- Current
- Asset version 8
New document findings1
Resolved structures3
Recurring evidence4
Human checksopen
Illustrative publishing state: review required
Use one document boundary without flattening native evidence.
Upload a PDF or DOCX in a free project, inspect its native evidence, and plan the API boundary around the document system you already operate.
Check a website freeCreate an account
Automated preflight is not an accessibility certification or legal determination.