Document-level metadata and declarations
Identify machine-verifiable document properties and the object that carries them.
PDF/UA-1 automated validation API
Validate machine-verifiable PDF/UA-1 conditions without turning a validator pass into an accessibility claim. AccessPreflight preserves PDF structure evidence and returns meaning-dependent checks as a separate review queue.
Scanning profile
pdfua-1-machinePDF/UA-1Technical preflight
- Input
- PDF based on PDF 1.7
- Mapping
- ISO 14289-1:2014 · machine-verifiable checks
- Boundary
- Validator outcome is not complete PDF accessibility
Machine layerPDF/UA-1 validation profile
EvidenceRule + object + page + validator version
Human layerMeaning, order, and content quality
Use PDF/UA-1 through the API.
Send pdfua-1-machine with the asset and keep this profile’s evidence boundary in the returned result.
Inspect the PDF as a structured document.
The evidence follows the PDF’s technical anatomy rather than reducing it to a generic error list.
Tagged PDF · PDF 1.7Catalog Structure tree Page content Embedded resources
Tags, roles, and relationships
Preserve the validation rule and the structural object involved.
Content items and associations
Connect a rule failure to the page and object evidence needed for repair.
Fonts, files, and annotations
Keep technical failures separate from questions about the resource’s meaning.
Trace a PDF/UA-1 finding from file condition to repair owner.
The useful path moves from the standard's machine-verifiable requirement toward the exact PDF object and then back to the authoring source.
- ISO 14289-1
Resolve the requirement
Keep the pinned profile and technical reference.
- PDF object
Locate the observed condition
Name the page, tag, annotation, or document property.
- Authoring source
Route the repair
Return work to the system that can produce a better file.
Build validation into the repair loop.
The profile is most useful when the team can return to the source and rerun the same pinned checks.
- 1
Validate
Run the PDF/UA-1 machine profile and preserve validator lineage.
- 2
Repair
Use page and object evidence in the authoring or remediation tool.
- 3
Review
Complete the meaning-dependent checkpoints with a qualified person.
- 4
Rescan
Compare the repaired file under the same profile version.
Read the source behind this profile.
The PDF/UA-1 source and its legal or standards context can change. AccessPreflight pins the profile version used for a scan; your organization should re-review applicability and the source when requirements change.
Run PDF/UA-1 where content enters the workflow.
Keep the profile, coverage boundary, evidence, and human-review queue attached to every result.
Check a website freeCreate an account
Automated preflight is not an accessibility certification or legal determination.