Your website may be accessible. Your PDFs may not be.
Reports, statements, invoices, contracts, forms, customer letters: the documents an organisation publishes are usually the part that was skipped.
Make your PDFs accessible.
Prove it with a record.
Normfluss checks a PDF against recognised accessibility standards, fixes what a machine can fix safely, and issues a record of what was tested, what was automated and what still needs a person.
PDF/UA-1 and the parts of WCAG 2.2 AA that apply to PDFs.
Automated remediation · Human review where judgement matters
Up to 25 PDFs at once · Signed evidence · Image descriptions in English, French, German and Dutch
No account · No credit card · Under a minute · EU-resident processing
Or integrate it: check and fix documents through our API, with the same signed evidence record. Read the API docs →
We measured 615 public documents from 126 organisations. Not one met PDF/UA-1.
The sample is not random: these are organisations whose own accessibility statements say some of their documents are not accessible. See the methodology →
Detect
See every failure, rule by rule.
Remediate
Structural fixes are automatic; you confirm the judgement calls.
Prove
A signed record of what was tested and what was fixed.
Don't just make it accessible.
Know what happened to it.
Most accessibility workflows stop at “The PDF passed.” But when someone asks what happened, you need more than a green checkmark. Normfluss records the answers alongside the document.
Your document leaves with its evidence.
Anyone holding a record can check it: enter its identifier to see which document it attests and which key signed it, then check the PDF against it. How to verify a record →
- What was tested?
- Which standard was used?
- What was automated?
- What did a human review?
- When was it validated?
Fixing PDFs by hand doesn't scale.
Making a PDF accessible by hand means tagging its structure, its tables and every image, document by document. The next batch goes out before the last one is finished. And when someone asks what was tested, what changed and who decided, a green checkmark answers none of it.
Three ways to make a PDF accessible
Fixing it yourself, paying an agency, or running it through Normfluss.
| Compared on | Manual tools (e.g. Adobe Acrobat Pro) | Accessibility agency | Normfluss |
|---|---|---|---|
| Cost | From €23.99 per licence per month², plus your staff's time on every page | Published rates from €3.55 to €10.21+ per page, by complexity¹ | €0.50 a page, falling to €0.35 on the largest packs; API allotments from €0.30. Checking is free. |
| How you pay | Per licence, per month | Per page | Per page |
| Workflow per document | Someone opens each file and tags, orders and checks it by hand | Files go out to the agency and come back remediated | Upload in the browser or send through the API. The structural work is automatic; you confirm the judgement calls. |
| Ongoing effort | Every new document is another manual pass | Every new batch is another order | Every new document runs through the same workflow |
| What you have at the end | The fixed file, plus whatever report your tool exports | The remediated file, plus whatever the agency provides | A signed record of what was tested, what passed and who decided each judgement call, verifiable against our published key |
| Who makes the judgement calls | Your own staff | The agency's staff | You make the judgement calls in a guided editor. The record names who decided and when. |
¹ Published per-page PDF remediation rates, checked 28 September 2026, in US dollars and converted at the European Central Bank's euro reference rate of 6 October 2026 (€1 = $1.1269): DigitalA11Y $4 to $8 per page; Accessible.org $4.00 to $11.50+ per page; Accessibility Consulting from $8 per page. Agencies that publish no per-page rate are not listed.
² Adobe Acrobat Pro for teams, annual plan billed monthly, per licence, excluding VAT, as published by Adobe Ireland on 6 October 2026.
Normfluss does the mechanical work and leaves people the judgement calls, then records both.
It's software you run, not a service performed for you.
At a glance
| Capability | Normfluss |
|---|---|
| Criteria checked | 119: 107 PDF/UA-1, 12 WCAG 2.2; 110 checked automatically, 9 need a person's judgement |
| Standards | PDF/UA-1 and the parts of WCAG 2.2 AA that apply to PDFs |
| Automated remediation | Yes: structure tree and tags, metadata, title and document language |
| Human review | In a guided editor: you accept, edit or reject each image description, and record a judgement on reading order; nothing is applied or reordered without you |
| Signed evidence | A signed record for each document: what was tested, what passed and who decided each judgement call, verifiable against our published key |
| API and batch | REST API with scoped keys and signed webhooks; up to 25 files per batch with an account |
| OCR support | Yes, on scanned pages before checking |
| Image descriptions | Drafted in English, French, German and Dutch; non-English drafts are machine translations a person confirms. A document whose images need descriptions in any other language is refused rather than described in English, and nothing is charged |
Every fixed document leaves with its evidence.
The record is signed, and anyone holding it can check it against our published key. It says:
- What was tested, against which standards
- Which rules ran, and which only a person can decide
- What was fixed automatically
- What a person decided, in their words, and who
- What passed
- What is still open, and why
- When it was validated and signed
Two documents we made to show the workflow, run through it for real: the companies, people and figures in them are invented. Each card is read from its signed record, which you can download beside the PDFs.
This document came out conformant within the tested scope, after a person wrote its three image descriptions.
riverbank-proposal.pdf · 2 pages
- What was tested
- Recognised PDF accessibility standards: 119 criteria.PDF/UA-1 and the parts of WCAG 2.2 AA that apply to PDFs.
- Which rules ran
- 110 checked automatically (veraPDF 1.30.2); 9 that only a person can decide.
- Before
- The free check failed 5 rules in 75 places.
- Fixed automatically
- Built the structure tree a screen reader navigates
- Marked the file as tagged
- Added the XMP metadata and told viewers to show the title
- Decided by a person
- Image description: “Annual visits across the four libraries fell from 47,800 in 2023 to 44,100 in 2024 and 41,200 in 2025.”
- Image description: “The study in four steps: baseline, Saturday opening restored, a six-month measure, then a twelve-month measure.”
- Image description: “Riverbank Trust logo: a line drawing of a bridge over water.”
- What passed
- 110 of 110 automated criteria, and every item that needed a person was decided.
- Still open
- Nothing.
- When
- Validated and signed 7 Oct 2026, 11:49 UTC · key nf-prod-2026-09
Record 6cfd0270-6407-47e0-b61e-c934b45cfc92
SHA-256 of the fixed file faf9f7831ec0d5c2146c5ac89d8294f9d0cc381bf0b00fa6c8aa94c5b48d6b0b
This document could not be made fully conformant. The record says so, and says why. Fixing at source →
brackenvale-statement.pdf · 2 pages
- What was tested
- Recognised PDF accessibility standards: 119 criteria.PDF/UA-1 and the parts of WCAG 2.2 AA that apply to PDFs.
- Which rules ran
- 110 checked automatically (veraPDF 1.30.2); 9 that only a person can decide.
- Before
- The free check failed 7 rules in 154 places.
- Fixed automatically
- Built the structure tree a screen reader navigates
- Marked the file as tagged
- Added the XMP metadata and told viewers to show the title
- Declared the language of the text
- Decided by a person
- Content that is neither tagged nor marked as page furniture: accepted the proposed handling
- Image description: “Brackenvale Water & Energy logo: a yellow triangle in a green circle.”
- Image description: “"Electricity used each month from April to September: 512, 487, 459, 448, 441 and 482 kWh.”
- Image description: “Where the money went this quarter: most of it on electricity, then the standing charge, VAT and water.”
- What passed
- 108 of 110 automated criteria.
- Still open
- The file doesn't state its accessibility claim (pdfua_5-1)
- A font isn't embedded in the document (pdfua_7.21.4.1-1)
- When
- Validated and signed 7 Oct 2026, 11:47 UTC · key nf-prod-2026-09
Record 8dbd64fc-a734-49b3-9d33-9a7fd97295bc
SHA-256 of the fixed file 2c996bb042a1926824bc9ba920e6e9dde8546536b024259ce730157a0d3183d7
From inaccessible PDF to validated document.
The same path every document takes, whether you upload it in the browser or send it through the API.
Checked against recognised PDF accessibility standards
PDF/UA-1 and the parts of WCAG 2.2 AA that apply to PDFs. PDF/UA is the ISO standard for accessible PDFs; WCAG is the web accessibility standard EU rules point to.
- 01
Upload
Drop a PDF into Normfluss and start with a free accessibility check. Text-based and scanned PDFs are supported.
- 02
Detect
Normfluss checks the document against the accessibility rules in your selected scope and shows you exactly what failed.
- 03
Remediate
Normfluss automatically handles the machine-detectable remediation work, including tags, tables and other structural issues.
- 04
Review
Some decisions require human judgement. Use the guided editor to accept or edit alt text and decide the other judgement calls. A person records a judgement on reading order; nothing is reordered automatically.
- 05
Validate
The fixed file is checked again, on the exact bytes you download. Anything that still fails is listed, never hidden.
- 06
Get the evidence
Export the remediated document together with a structured evidence record showing what was tested, which standard was used, what passed and what required human review.
One document. One result. One evidence trail.
Start free. Go as far as you need.
The same engine and the same evidence, however you use it.
Free check
In the browser, no account
One PDF without an account, up to 25 at once with a free one. See every failure, rule by rule.
Check your PDFs free →Pay per page
Fix the documents you choose
Confirm the judgement calls in the editor and download each file with its signed record.
See pricing →API and batch
Send from your own systems
Each document comes back with its signed record, and a webhook tells you when it is done. Your first API key comes with 200 free credits to evaluate it.
Read the API docs →
Built for organisations whose documents are records.
- Banking & financial services
A statement to every customer, every month, and every one a PDF.
- Insurance
Policy documents a customer has to read before they can rely on them.
- Public sector
Forms and notices every resident has to be able to use.
- Education
Course materials and forms each student needs in a form they can read.
- Healthcare
Letters and forms where a patient has to read what concerns them.
- Software platforms
Documents your product generates for your customers, at volume.
- Enterprise & legal
Contracts, policies and HR documents across the whole organisation.
- E-commerce
Invoices, receipts and terms that go out with every order.
How it works on a document
- Structure & tagging
- A screen reader cannot navigate an untagged PDF. We build its structure tree, and keep an author's existing tree whenever rebuilding it would lose anything in it.
- Tables
- A table read as loose text is noise. Tables are tagged as tables, rows and cells.
- Alt text
- Every image needs a description only a person can confirm. Our self-hosted model drafts one in the document's language (English, French, German or Dutch), and nothing is applied until someone accepts it.
- Evidence
- When someone asks what was done, you hand them a signed record: what was tested, what passed and who decided each judgement call.
- Signed PDFs
- A digitally signed PDF isn't rewritten — saving it would break the signature. We say so before anything changes, and nothing is charged. Where a file carries only usage rights rather than an author signature, you can choose to go ahead.
- Fix at source
- Some problems can only be fixed in the program that made the PDF. We say which, and how.
EU-resident processing · Self-hosted models, no third-party AI · Your files are never used for training · Free checks deleted within 72 hours · Delete any document yourself, any time. Security →
Free to check. Pay per page to remediate.
One credit remediates one page: €0.50 a page, falling to €0.35 on the largest packs; API allotments from €0.30. Buy a pack of platform credits, or, for programmatic volume, take a monthly API allotment.
Free check
See what's wrong before you pay. Checking is always free.
Platform credit packs
One-time · credits never expire
Starter
€50
100 credits
€0.50 / credit
Buy →Small
€500
1,000 credits
€0.50 / credit
Buy →- Most popular
Growth
€2,250
5,000 credits
€0.45 / credit
Buy → Scale
€8,000
20,000 credits
€0.40 / credit
Buy →Volume
€35,000
100,000 credits
€0.35 / credit
Buy →
Checking is free; you spend one credit to remediate one page. Buying happens in your account; you'll sign in first if you haven't already.
API for pipelines
Remediate from your own systems through the REST API and webhooks. Create a key and get 200 free credits to evaluate it on your own documents. Monthly allotments from €0.30 / credit: 50k to 1M credits a month, topped up each period.
What Normfluss does, and what it doesn't.
- What does Normfluss do?
- Normfluss detects, remediates and validates accessibility issues in PDF documents, then issues a signed evidence record describing exactly what was tested and fixed within a stated scope. You can use it self-serve in the app or integrate the API into your own product.
- Is Normfluss a legal compliance certification?
- No. Normfluss reports technical conformance against a stated testing scope and produces signed evidence of what was checked. It is not a legal certification or legal advice; a compliance determination is a decision for your compliance team or counsel.
- How much does it cost?
- Checking is free. Fixing: €0.50 a page, €0.35 on the largest packs, from €0.30 on API allotments. Prices in euros. See pricing →
- Will Normfluss change my document's appearance?
- No. Before a fixed file is delivered it is compared with your original: the number of pages, how every page renders, and the text. A fix that changes the page count, visibly changes a page, or loses text beyond a small tolerance for extraction noise is not delivered. What can change is the document's structure tree, the tagging a screen reader relies on. If your PDF has none, we build one. If it already has one, from Word or InDesign for example, we build a new one and compare it with yours: if the new one would lose any image description, table header cell, note, contents list or heading your tree had, we keep your tree and fix only what lives outside it. The evidence record says which happened.
- What happens when automation cannot determine the correct answer?
- A person decides, and the record says who. A machine can tell that an image has a description; it cannot tell whether the description is right. So where the answer needs judgement, Normfluss drafts a suggestion. You accept or edit it in the guided editor, or reject it and record why: that it does not apply, or that it is a known exception. The signed evidence record lists every one of those decisions: which criterion, what was decided, by whom and when. A document is never recorded as conformant while a decision like that is still open.
- Which document languages does Normfluss support?
- Image descriptions are drafted in the document's own language (currently English, French, German or Dutch), detected automatically. Every draft in a language other than English is a machine translation that you confirm before it is applied. A document with images in a language we cannot describe yet is refused rather than given English descriptions. The interface itself is in English.
- Where is my data processed?
- In the EU. Documents you check or remediate are processed in the EU. Files from a check made without an account are deleted after 72 hours unless you create an account.
- How long do you keep my documents once I have an account?
- Until you delete them. Nothing in your account expires on its own, so you can come back to a document, download it again or show its evidence later. Deleting a document deletes its files, the original and every fixed version, and keeps its signed evidence record so the proof of what was tested survives. Deleting your account stops access straight away; you have 30 days to change your mind, after which your personal details are erased and every document file is deleted.
- Which accessibility standards does it check against?
- We check against PDF/UA-1 and the parts of WCAG 2.2 AA that apply to PDFs, the current version of WCAG. Every check runs 119 criteria: 107 from PDF/UA-1 and 12 from WCAG 2.2. Every check records precisely which criteria ran, so the evidence is auditable rather than a single pass/fail badge.
- Can I integrate Normfluss with my own systems?
- Yes. Alongside the self-serve app there is an API to check and remediate documents programmatically inside your own product or pipeline, so accessibility becomes part of how documents are produced rather than a manual cleanup afterwards.
Start with your PDFs.
Upload your documents and see exactly where accessibility problems exist. Fix the ones you choose, and keep the signed evidence of what was done.
Check your PDFs free →No credit card · One PDF without an account, 25 at once with one