PDF/UA-2 validation API

Validate PDF 2.0 documents against the PDF/UA-2 machine profile without treating it as a silent upgrade from PDF/UA-1. The requested standard generation stays visible from upload through evidence export.

For document platforms introducing PDF 2.0 and PDF/UA-2 workflows

API profilepdfua-2-machine@1.2.0

Try it free Book a demo

Illustrative request202 Accepted

POST /v1/scans
Idempotency-Key: reports-service@4.8.2

{
  "asset": {
    "type": "upload",
    "upload_id": "upl_pdf2_accessible_report"
  },
  "profiles": [
    "pdfua-2-machine@1.2.0"
  ],
  "metadata": {
    "generator": "reports-service@4.8.2"
  }
}

queuedid: scn_01J…profile resolved

Input: PDF 2.0 upload
Profile: Dedicated PDF/UA-2 machine target
Adoption: Controlled independently from PDF/UA-1

Choose the PDF standard generation in the request.

Separate profile IDs prevent an engine update from changing which PDF/UA generation a workflow is expected to produce.

PDF/UA-1 workflow

PDF based on PDF 1.7
pdfua-1-machine profile family
Existing production and archive baselines
Independent validator history

PDF/UA-2 workflow

PDF 2.0 input
pdfua-2-machine profile family
Deliberate adoption by generator or project
Separate evidence and comparison lineage

Introduce PDF/UA-2 one generator at a time.

Use generator metadata and project-scoped configuration to make adoption observable before the new profile becomes a wider publishing gate.

Canary
Identify PDF 2.0 output
Send the generator version and requested profile with the source asset.
Compare
Track machine findings by generator release
Use stable fingerprints to distinguish repaired, recurring, and new failures.
Adopt
Promote the profile deliberately
Move the validated generator into the publication path without changing older records.

Make newer-format coverage reviewable before it becomes a gate.

Separate supported PDF/UA-2 checks from incomplete coverage and human evaluation while the profile is adopted.

Supported

Machine checks

Pinned rules
Object evidence
Stable fingerprints

Evaluate

Coverage gaps

Profile delta
Source behavior
Engine changes

Human

Document experience

Reading order
Meaning
Navigation quality

Inspect the policy behind the API profile.

Before PDF/UA-2 becomes a production gate, review its source mapping, supported input, automation boundary, and required human checks.

Read the PDF/UA-2 profile ISO 14289-2:2024 (PDF/UA-2)veraPDF validation documentation

Put the PDF/UA-2 API in the path you already own.

Start with one asset flow, pin the profile, and keep evidence and unresolved human work attached to every result.

Check a website free Create an account

Automated preflight is not an accessibility certification or legal determination.