How it works Features Compliance Pricing Docs Get early access
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.

Request early access → See how it works
M+
pages / hour
/UA
PDF standard
0
data stored
invoice_batch_47291.pdf
Tagging…
✓Heading structure
✓Bookmarks
✓Tag tree
✓Embedding fonts
…Reflow
POST /v1/generate
"template_id": "invoice_v3",
"data": { "account_number": "****4821", … },
"reference_id": "INV-2026-001",
"language": "en"
HTTP/1.1 200 OK
Content-Type: application/pdf
Content-Disposition: attachment; filename="invoice-2026-001.pdf"
X-Generation-Ms: 48
Trusted in regulated industries
Insurance Banking Healthcare Government Utilities Education
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 PDFUA 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.

How it works

Three steps to
compliant output.

Design your template in the browser-based designer or import your existing DOCX. 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 — or import an existing DOCX file directly. Fonts are embedded at the template level. Accessibility structure is defined once, applied to every document generated from that template.

Import quarterly_statement.docx
→ Fonts detected: Helvetica Neue, Arial
→ Structure mapped: 3 sections, 1 table
🔗
02

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}}
⚡
03

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
Live designer PDFUA visual template designer — structured element tree on the left, document canvas in the centre, properties panel on the right
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 interface is available in English and French. The documents you generate can be any language — French, English, Arabic, Japanese, or any Unicode-supported script. Language metadata is set at the template and span level for correct screen reader behaviour regardless of the document language.

ISO 639 · BCP 47 · Unicode
⚡

High-volume batch generation

Millions of pages per hour. Built on Rust — a single lightweight executable, no remote storage, no database round-trips. Linear horizontal scaling with no architectural bottlenecks. 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 the pipeline.

In-memory processing · PIPEDA
📄

DOCX import

Import your existing Word documents directly into the template designer. Fonts are detected and mapped, layout is preserved, and data binding fields are added to your existing document structure.

OOXML · font substitution
✅

Compliance by construction

The tag tree, reading order, font Unicode mapping, table structure, and language metadata are generated deterministically from your template definition. Every element in the designer maps 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 · ISO 14289 · 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-generated document simultaneously satisfies six overlapping standards across Canadian, US, and European jurisdictions — from a single generation pipeline.

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.

If your organization generates documents in any of these sectors, you are operating under one or more of the standards above — whether you know it or not.

Insurance
Insurance & Benefits
Monthly statements, explanation of benefits, policy declarations, renewal notices, claims summaries
Banking
Banking & Finance
Account statements, loan schedules, mortgage disclosures, investment reports, fee notices
Government
Government & Public Sector
Benefit letters, tax notices, assessment documents, pension statements, public consultations
Municipal
Municipal & Local Government
Property tax bills, permits, bylaw notices, inspection reports, school board communications
Utilities
Utilities & Telecom
Bills, usage reports, service agreements, disconnection notices, plan summaries
Education
Post-Secondary Education
Transcripts, financial aid letters, enrolment confirmations, course calendars, degree audits
Healthcare
Healthcare
Lab results, discharge summaries, drug benefit statements, referral letters, provider directories
Retail
Retail & Loyalty
Loyalty statements, reward summaries, purchase histories, warranty documents, account notices
Pricing

Compliant documents at a
fraction of remediation cost.

Remediation services charge up to $20 per page. PDFUA generates documents that are born accessible — no remediation pipeline, no per-page fixing after the fact. Contact us and we'll size a plan to your volume.

Cloud · Starter

Starter

For teams beginning their compliance journey. Full API access and visual designer included from day one.

  • PDF/UA-1 compliant generation
  • Visual template designer (EN / FR)
  • DOCX import
  • REST API — synchronous generation
  • Generate documents in any language
  • Compliance by construction
  • Email support
Request early access
Cloud · Growth

Growth

For organizations running regular high-volume batches. Higher throughput, priority support, and support hour packages available.

  • Everything in Starter
  • Higher rate limits
  • Priority email support
  • Support/Services hour packages available
Request early access
Enterprise · On-premise

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

Support & services packages available as add-ons on any plan. Ask us about pricing.

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.