PDF/UA · ISO 14289 · Section 508 · WCAG 2.1 AA

Documents born accessible. Not remediated.

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

Data stored

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

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.

generate → remediate → re-check → hope
(per document, per revision, forever)

The PDFUA.io way — generation

Born accessible

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.

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.

template quarterly_statement_v3.pdfua.json
→ 3 sections · 1 table · fonts embedded: 2
→ git commit -m "Q3 statement: tagged table"

Bind your data

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.

{{account.holder_name}}
{{transactions[]}} // dynamic rows
{{balance.closing}}

Call the API. Receive compliance.

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 validated, ready to deliver to your end users or store in your archive.

POST /v1/generate
← 200 OK validation: pass
← Content-Type: application/pdf

pdfua.io/designer — modular_mood_invoice.template

PDFUA.io visual template designer — structured element tree on the left, document canvas in the centre, properties panel on the right

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. Built on Rust — a single lightweight executable, no database round-trips, linear horizontal scaling. Every page in a run of 50,000 statements receives the same compliance treatment as the first.

Rust · Tokio async

Zero data storage

Your document data is never stored. Template definitions live in your account. Data payloads are processed in memory and immediately discarded. No document content touches persistent storage at any point.

In-memory processing · 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? Deploy the same generation engine inside your own infrastructure via Docker. No architecture changes, no feature gaps, no data leaves your network.

Docker · air-gapped support

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.

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.

Insurance & Benefits

Monthly statements, explanation of benefits, policy declarations, renewal notices, claims summaries

Banking & Finance

Account statements, loan schedules, mortgage disclosures, investment reports, fee notices

Government & Public Sector

Benefit letters, tax notices, assessment documents, pension statements, public consultations

Municipal & Local Government

Property tax bills, permits, bylaw notices, inspection reports, school board communications

Utilities & Telecom

Bills, usage reports, service agreements, disconnection notices, plan summaries

Post-Secondary Education

Transcripts, financial aid letters, enrolment confirmations, course calendars, degree audits

Healthcare

Lab results, discharge summaries, drug benefit statements, referral letters, provider directories

Retail & Loyalty

Loyalty statements, reward summaries, purchase histories, warranty documents, account notices

Also from PDFUA.io

Already generating PDFs?
Prove they're accessible.

The PDFUA.io Validator checks any PDF — yours or anyone's — against WCAG 2.1 AA or strict PDF/UA-1 (ISO 14289-1), and keeps audit-ready evidence: clause-level ISO citations, SHA-256 fingerprints, bilingual reports, and scheduled monitoring with regression alerts.

PDFUA.io Validator

Free plan · 20 credits a month · reports in EN & FR

Upload files, point at URLs, or scan a whole domain with free PDF discovery. Paid plans from $19/mo USD when you need more.

Explore the Validator →

Pricing

Compliant documents at a
fraction of remediation cost.

Remediation services charge $5–$10 per page. PDFUA.io documents are born accessible — no remediation pipeline, no per-page fixing after the fact. Plans are sized by pages generated per month; start small, scale to nightly statement runs.

Cloud · Starter

$19 /mo USD

For small organizations making their documents accessible.

1,500 pages / month
Visual designer & REST API
PDF/UA-1 compliant output
Email support

Request early access

Your infrastructure. Your data. Your terms.

Deploy the same generation engine inside your own environment via Docker — cloud, air-gapped, or hybrid. Custom SLA, data processing agreement (PIPEDA / GDPR), dedicated onboarding, and direct engineering access. Pricing based on your volume and deployment model.

Request early access

Community edition · Nonprofits & education

Accessibility should be accessible.

Registered nonprofits and educational institutions can apply for the Community edition — free during early access, deeply discounted after, in exchange for feedback that shapes the product. Limited places.

Apply

Prices in USD, billed by invoice. A page is one generated PDF page; allowances reset monthly and overage is billed per page.

Your next audit
should be boring.

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:

1 of 3

What's your industry?

2 of 3

How many pages do you generate per month?

3 of 3

What's your compliance timeline?

✓

You're on the list.

We'll be in touch shortly.