PDF/UA-1 path
- ISO 14289-1
- PDF 1.7 document base
- Its own validation profile
- Historical evidence remains pinned
PDF/UA-2 automated validation API
Run PDF/UA-2 machine checks for PDF 2.0 as their own pinned profile. Keep the newer document model distinct from PDF/UA-1 and expose what the validator checked, what it found, and what a person still needs to decide.
Scanning profile
pdfua-2-machinePDF/UA-2Technical preflight
- Input
- PDF 2.0
- Mapping
- ISO 14289-2:2024 · machine-verifiable checks
- Boundary
- Separate profile from PDF/UA-1
Document basePDF 2.0
Accessibility profilePDF/UA-2
Evidence pinValidator and validation-profile versions
Use PDF/UA-2 through the API.
Send pdfua-2-machine with the asset and keep this profile’s evidence boundary in the returned result.
Do not silently treat PDF/UA-2 as PDF/UA-1 with a new label.
The source version and accessibility profile are resolved together so the scan stays technically interpretable.
PDF/UA-2 path
- ISO 14289-2:2024
- PDF 2.0 document base
- Separate rule and validator mapping
- No silent substitution across versions
The validator identity is part of the result.
A machine result is reproducible only when the engine and profile versions travel with it.
Illustrative result
review_required- Document
- PDF 2.0 source hash
- Profile
- pdfua-2-machine · resolved version
- Validator
- Engine + validation-profile version
- Review
- Meaning-dependent checkpoints open
Treat PDF/UA-2 adoption as a controlled profile lifecycle.
A newer document target should enter production deliberately, with comparable scans and an explicit human-review boundary.
- Evaluate
Inspect source output
Confirm the document workflow can produce the required structures.
- Pin
Resolve one profile version
Keep the target stable for repeat scans.
- Compare
Review changed evidence
Separate profile changes from source changes.
- Adopt
Move the publishing gate
Retain manual evaluation alongside machine results.
Adoption stays reversible and evidence-led.
Read the source behind this profile.
The PDF/UA-2 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-2 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.