Skip to content

Included in Better

Accessibility (PDF/UA)

Accessibility workflows help publishing teams inspect, remediate, and validate PDFs before public delivery.

Problem

Teams need to know whether a PDF is standards-ready, suspicious, malformed, or safe to archive before they mutate it.

Use

Run read-only inspections and standards checks that return findings, verdicts, and exportable evidence.

Evidence plan

What this unlocks

  • Remediate accessibility gaps and validate PDF/UA with veraPDF
  • Inspect without modifying the source document
  • Better package access keeps the path explicit
Simple pathForm W-9

Quick OCR and field check

Turn a scanned form into a searchable PDF and verify the obvious fields before routing it.

  1. 1Upload the W-9
  2. 2Run OCR
  3. 3Inspect detected text and form regions
  4. 4Save a searchable copy
Searchable PDFField review notesClean source metadata
Complex pathAttention Is All You Need

Knowledge and publishing workflow

Extract tables, cluster findings, improve accessibility metadata, convert to archival format, and attach a provenance record.

  1. 1Extract tables and figures
  2. 2Cluster recurring concepts
  3. 3Inspect reading order and metadata
  4. 4Convert to PDF/A
  5. 5Run preflight
  6. 6Export provenance
Table exportFinding clustersAccessibility worklist

Inputs & outputs

Accepted formats
pdf
Produced formats
pdf

Common use cases

  • Prepare PDF/UA deliverables
  • Repair reading order and structure issues
  • Pair OCR with accessibility validation

Workflow steps

  1. 1Inspect the current structure and text layer
  2. 2Apply deterministic remediation where appropriate
  3. 3Validate and export the final report

Outputs

  • Findings report
  • Risk or standards verdict
  • Evidence bundle

Review checks

  • Group findings by severity
  • Route failures into remediation tools
  • Attach reports to audit or review records

API

Endpoint family: /v1/forensics, /v1/preflight, /v1/reports
  • Forensics and validation tools typically return reports and findings instead of mutating source files.
  • Use /v1/forensics and related report endpoints for headless evidence collection.
Integration overview

Limits

Availability
Included in Better
Readiness
beta
Automation
Single-document workflow

Confirm entitlement, input requirements, and deployment fit in the package and API documentation before you automate this capability.

Integration overview

Evidence

Browse proof
Evidence is published with the related workflow and proof artifact when it is available for this capability.

Public example workflows

Integration overview

Roles and use cases