High-volume statement and document generation with native PDF/UA
compliance. Design your template once. Merge your data. Receive
audit-ready PDFs — every time, at any scale.
Early access · priority to active compliance deadlines — or
see how it works
pdfua.io/templates/quarterly_statement_v3
quarterly_statement_v3
Tagging…
POST /v1/generate · 200 OK · content-type application/pdf · x-generation-ms 48
48ms
Per document
1M+
Pages / hour
0
Document data kept
100%
Tagged output
Generated structure
✓ Heading structure & tag tree ISO 14289-1 · 7.1
✓ Fonts embedded — ToUnicode maps ISO 14289-1 · 7.21
✓ Table headers & scope ISO 14289-1 · 7.5
✓ Language metadata — EN / FR ISO 14289-1 · 7.2
→ Reflow layout attributes WCAG 1.4.10
Tonight's batch · statements
50,000
all born accessible · 0 remediated
Trusted in regulated industriesInsuranceBankingHealthcareGovernmentUtilitiesEducation
The problem
Remediation doesn't scale. It never did.
Every organization generating high-volume documents is facing the same wall. The ADA
Title II deadline is here. Your current output isn't compliant. And the only solutions
you've been offered cost a fortune or break at scale.
The old way — remediation
Fix it after the fact
Take a generated PDF and manually retrofit accessibility tags. At one
document this is painful. At 50,000 statements per night
it's impossible. Every batch is a compliance liability. Every audit is a scramble.
The tag tree, reading order, reflow instructions, font Unicode mapping, table
structure, lists, images, table of contents, footnotes, endnotes, and language
metadata are all generated at document creation time. No post-processing.
No remediation pipeline. Every document that leaves the system is already
compliant.
/Document
├ /H1 "Quarterly Statement" · Lang en-CA
├ /Table — TH scope, 148 rows, splits tagged
└ /Figure — alt text bound from data
How it works
Three steps to compliant output.
Design your template in the browser-based designer. Connect your data. Call the
API. Receive a PDF/UA compliant document.
01
Design your template
Use the visual designer to build your statement layout — sections, elements,
tables, and data bindings. Templates are plain JSON you can export, diff, and
keep in your own source control. Accessibility structure is
defined once, applied to every document generated from that template.
Use {{field_name}} syntax to bind any data field to any element
in the template. Tables expand dynamically based on row count. Pages are added
automatically. Variable-length content is handled natively — no layout overflow,
no clipped text.
POST your template ID and data payload to the generation API. Receive a
PDF/UA compliant document in response — fully tagged, fonts
embedded with correct Unicode mappings, reading order set by the template, ready to
deliver to your end users or store in your archive. JSON or XML in, one record per
call — or up to 500 JSON records per batch.
POST /api/v1/documents/generate
← 200 OK X-Pages: 3
← Content-Type: application/pdf
pdfua.io/designer — modular_mood_invoice.template
The live designer — sections, elements, and data bindings map 1:1 to PDF structure.
Features
Everything compliance requires. Nothing it doesn't.
Built by people who have been inside enterprise document operations for over 20
years. Every feature exists because a real compliance requirement demanded it.
Native PDF tag tree
Complete logical structure — headings, paragraphs, tables, lists, figures — generated at creation time. Not retrofitted. The tag tree reflects the actual document semantics, not guessed structure.
PDF/UA-1 · ISO 14289
Font embedding with ToUnicode
Every font is fully embedded with correct ToUnicode CMap generation — including ligatures, diacritics, and special characters. Accented Latin, and financial symbols handled correctly.
Font subsetting · CID fonts
Accessible tables
Complex statement tables with dynamic row counts, spanning headers, and multi-page breaks — all tagged with proper TH scope attributes, header associations, and correct reading order across pages.
WCAG 2.1 AA · Section 508
Any language. Any script.
The designer is available in English and French; the documents you generate can be any Unicode-supported language. Language metadata is set at the template and span level for correct screen reader behaviour.
ISO 639 · BCP 47 · Unicode
High-volume batch generation
Millions of pages per hour from a single lightweight service that scales horizontally: add workers, get throughput. Every page in a run of 50,000 statements receives the same compliance treatment as the first.
Async batch API · Linear scaling
Document data is not kept
The data you send to generate a document is used for that document only. Single documents are generated in memory and returned in the response. Large and batch jobs encrypt their input (AES-256-GCM) and delete it once the PDF is generated, and generated PDFs expire after a short, configurable time. Template definitions live in your account.
Short-lived by design · PIPEDA
Accessible form fields
Interactive AcroForm fields — text inputs, checkboxes, dropdowns, radio groups, and signature fields — generated with the same tagged structure and labels as the rest of the document.
AcroForm · tagged fields
Compliance by construction
Every element in the designer maps deterministically to a specific PDF structure element. The output is correct because the process is correct — not because it passed a check afterward.
PDF/UA-1 · Born accessible
On-premise deployment
Data residency requirements? Run the same generation engine on your own server with Docker Compose — air-gapped included. Licenses are signed tokens verified offline: no phone-home, ever. On-premises details →
Docker · Air-gapped · Offline license
PDF/A-2a when you need archival
Opt in per organization or per API call, and every document also conforms to PDF/A-2a (ISO 19005-2): an embedded sRGB output intent, fully self-contained, rendering identically decades from now. Same generation call — no conversion step.
ISO 19005-2 · Opt-in
Your data, as it already is
POST JSON or XML to the generation API. In the designer, build data models from JSON, CSV, or XML samples. Or generate one PDF per row straight from a Google Sheet.
JSON · XML · CSV · Google Sheets
Assets and layouts that scale
An organization-wide image and SVG library with alt text managed in one place, SVGs embedded as tagged vector figures, multi-column sections, and tables with merged cells that split cleanly across pages.
Asset library · Columns · Tables
Compliance
Every standard your auditor will ask about.
A single PDFUA.io-generated document simultaneously satisfies six overlapping standards
across Canadian, US, and European jurisdictions — from a single generation pipeline.
The standards
PDF/UA-1
ISO 14289 — Universal Accessibility
The only formal, file-format-specific accessibility standard for PDFs. Required for full screen reader compatibility. Foundation of all other PDF accessibility requirements.
WCAG 2.1 AA
ADA Title II — DOJ Final Rule (2024)
Required for all US state and local government entities. Compliance deadline April 2026. PDFs are explicitly covered. Also satisfies AODA (WCAG 2.0 AA) and ACA requirements.
Section 508
U.S. Federal Accessibility Standard
Required for US federal agencies and their contractors. PDF/UA-1 satisfies the technical requirements for electronic documents under the Revised 508 Standards.
EN 301 549
European Accessibility Act
EU standard for ICT accessibility, enforcement active June 2025. Adopted identically as CAN/ASC-EN 301 549:2024 — one document satisfies both EU and Canadian federal requirements.
AODA
Ontario — Accessibility for Ontarians with Disabilities Act
Mandates WCAG 2.0 AA for digital documents. Applies to every organization with one or more employees in Ontario — roughly 444,000 organizations across all sectors.
ACA
Canada — Accessible Canada Act · CAN/ASC-EN 301 549:2024
Federal standard covering banking, telecoms, transportation, and Crown corporations. Adopted EN 301 549 v3.2.1 in full as a National Standard of Canada in May 2024. Penalties up to $75,000 for non-compliance.
PDF/A-2a
ISO 19005-2 — Long-term archiving (optional)
Opt-in archival conformance for records-retention contexts — legal, government, healthcare. Its "a" level requires the same tagged structure as PDF/UA, so one generation call produces a document that is both accessible and archival.
Where it applies
If your organization generates documents in any of these sectors, you are operating under one or more of the standards — whether you know it or not.
The PDFUA.io Validator checks any PDF — yours or anyone's — against WCAG 2.1 AA or
strict PDF/UA-1 (ISO 14289-1). Our own engine, calibrated against the veraPDF PDF/UA-1
test corpus.
Scan a whole domain
PDF discovery reads robots.txt and sitemaps, crawls pages, and pulls WordPress media libraries to find every document on a site — then groups them by folder.
Sitemaps · Crawl · WordPress
Monitor, don't re-audit
Daily, weekly, or monthly re-validation with a 90-day pass/fail trend and alerts on regressions. Unchanged files are detected and not re-charged.
Schedules · Regression alerts
Evidence, not screenshots
Every finding cites its ISO 14289-1 clause and WCAG criterion; every report carries a SHA-256 fingerprint and renders in English or French at any time.
ISO citations · SHA-256 · EN/FR
PDFUA.io Validator
Free plan · 20 credits a month · reports in EN & FR
Upload files, point at URLs, or scan a whole domain. Paid plans from $19/mo USD;
on-premise editions for air-gapped networks.
Join the early access list. We're onboarding a small number of organizations before
general availability — priority goes to teams with active compliance deadlines.
No spam. No sales calls unless you ask for one.
You're on the list. Three quick questions help us prioritise your access:
