Accessible documents, without guesswork
Every PDF has
a route to accessible.
We build from structured source, reconstruct existing PDFs and validate the result. One approach would never fit every document.
0 failed rules
0 warnings
independently checked
Measured, not assumed.
- PDF/UA series
- 13 / 13
- Letters preserved
- 146,393
- veraPDF
- 0 / 0
- Final check
- veraPDF + PAC
The right route for the actual source
Three routes.
One accountable result.
A Word file, a generated statement and a legacy PDF are not the same problem. We first establish what can be preserved and which route can be proven.
01
Structured source
Build it right at the source.
Turn DITA, XML or another structured source into repeatable PDF/UA. The publishing pipeline becomes the fix, so the next document is accessible too.
02
Existing PDFs
Reconstruct, don't patch blindly.
We recover content, reading order and document structure, then generate a new result. The original PDF remains untouched and available for comparison.
03
Independent evidence
Prove what left the pipeline.
Every claim belongs to a specific file hash. veraPDF and PAC test the actual output; visual comparison guards the design and the reading experience.
Evidence attached to the file
A green label is not enough.
Compliance is only meaningful when the checked file, validator version and outcome stay together. A failed run fails closed. No report means no green claim.
- 01 PDF/UA checked with the pinned veraPDF profile
- 02 PAC reviewed across PDF/UA, WCAG and Quality
- 03 Text, links and visual output compared with the source
VALIDATION REPORTPDF/UA-1
artifactpublication-accessible.pdf
profileua1
resultPASSED
failed rules0
failed checks0
sha256
e58d8f0e51af…83c921
Checked artifactEvidence stays with this exact file
Where this pays off
Built for document systems,
not one-off cosmetics.
01
Public information
Reports, decisions, policy documents and recurring publications.
02
Regulated documents
Statements, terms, product information and customer correspondence.
03
Publishing pipelines
DITA, XML, XSL-FO, Apache FOP and migration away from end-of-life renderers.
Start with the document you already have
One real file tells us
which route is honest.
We inspect the source, identify the repeatable route and show what can be proven before a larger engagement starts.
Send the first document