Accessibility & archival

PDF/A and PDF/UA, verified — not aspirational

Forme generates the full PDF/A archival ladder and both generations of PDF/UA accessibility, and validates every level with veraPDF as a CI gate on every commit. One document can be both archival and accessible.

archival + accessible
import { renderHtml } from '@formepdf/html';
import { standardFonts } from '@formepdf/fonts-standard'; // embeddable fonts

const fonts = standardFonts().map((f) => ({
  family: f.family, data: f.src, weight: f.fontWeight,
  italic: f.fontStyle === 'italic' }));

const { pdf } = renderHtml(html, {
  pdfA: '2a',   // PDF/A-2a
  pdfUa: true,  // + PDF/UA-1, same file
  lang: 'en',
  fonts });

41/41 documents pass their claimed profiles — 165 veraPDF validations per commit.

0pt layout drift: accessible output is geometry-identical to normal output.

Refuses to render if a font can't be embedded, rather than claim conformance it lacks.

Supported profiles

The full ladder, at both PDF generations

ProfileFormeNotes
PDF/A-2b, 2u, 2aYesPDF 1.7 archival; 2a composes with PDF/UA-1
PDF/A-3b, 3u, 3aYesAllows embedded files
PDF/A-4, A-4fYesPDF 2.0 archival; composes with PDF/UA-2. A-4f (embedded files) on the component API
PDF/UA-1YesTagged structure, alt text, tab order
PDF/UA-2YesPDF 2.0 structure namespace (pdfUa2)
VerificationveraPDF in CIEvery level, every commit

How it works

Built into the engine, not bolted on

Tagged structure, one option away

Structure trees, marked content, alt text, and keyboard tab order. The component API tags by default; on the HTML path it's one option — tagged: true or pdfUa: true. Strict PDF/UA mode is pdfUa on either path.

Metric-compatible fonts

@formepdf/fonts-standard embeds fonts with the same metrics as the defaults, so the accessible document lays out exactly like the one you previewed.

The refusal is the feature

PDF/A needs embeddable fonts. If one can't be embedded, pdfA refuses to render instead of emitting a file whose metadata claims conformance it doesn't have.

From HTML, components, or Python

The conformance options work on the HTML path (pdfA: '2b', pdfUa: true), the component API (<Document pdfa="2b" pdfUa>), and the Python SDK (pdfa="2b", pdf_ua=True). A-4f, which needs an embedded file, is on the component API.

PDF/A and PDF/UA questions

Does Forme produce PDF/A files?
Yes — the full ladder: PDF/A-2 (2b/2u/2a), PDF/A-3 (3b/3u/3a), PDF/A-4 and A-4f, PDF/UA-1, and PDF/UA-2, every level verified with veraPDF in CI. PDF/A-4 and PDF/UA-2 are over PDF 2.0. Archival composes with accessibility at both generations (A-2a + UA-1, A-4 + UA-2).
Is the accessibility support real, or aspirational?
Verified. 41/41 documents — the conformance corpus plus the gallery templates — pass their claimed profiles, across 165 veraPDF validations run as a CI gate on every commit. Accessible output is geometry-identical to normal output.
Can one PDF be both PDF/A and PDF/UA?
Yes. A-2a composes with PDF/UA-1 on PDF 1.7, and A-4 with PDF/UA-2 on PDF 2.0. That combination is what government, education, and healthcare requirements usually ask for.
What do I need for PDF/A?
Embeddable fonts: install @formepdf/fonts-standard or register your own. Without them, rendering stops with an error rather than producing a non-conformant file.