Product
The document accessibility platform for public entities
DocoMatic finds the documents on your public websites, remediates them for WCAG 2.1 AA(opens in new tab) and PDF/UA(opens in new tab), and checks every file before you get it back.
From Level 2 up, that check is veraPDF(opens in new tab) validation. Six parts, one credit balance, one verification report per file.
Nothing ships on trust. Every file comes with its evidence, and you are not charged for a file that does not reach its level's threshold.
The scan is free, covers public pages only and needs no account.
- WCAG 2.1 AA
- PDF/UA (ISO 14289)
- veraPDF validation from Level 2
Six parts, one platform
What the platform does
Six parts. Each has its own page with the detail.
PDF remediation
Tag structure, reading order, tables, forms and alt text, for born-digital PDFs, scanned PDFs, and PNG or JPEG page images. We analyze each document and recommend a level: fillable forms go to Level 3; tables, columns, figures or scans to Level 2, with OCR for scans; plain text to Level 1. You choose before any work runs.
How bulk PDF remediation worksDocument monitoring
Scheduled and on-demand scans of the domains you verify. Each scan lists the PDFs and Office documents your pages link to, scores their risk and runs machine checks on the PDFs, within your plan's limits. After the first scan, new, changed and newly failing documents appear as alerts. You cannot plan a backlog you have not counted.
Build a website PDF inventoryVerification and reports
Decides whether the rest worked
Every file is machine-checked and scored, and from Level 2 up it is validated with veraPDF against PDF/UA-1. Each document version gets a report you can download as PDF and JSON, and its version history is kept. At Level 2 and Level 3, a file passes only if veraPDF, an independent open-source validator, reports zero failures.
What a PDF accessibility verification report containsIntegrations
Connect an Amazon S3 or S3-compatible bucket, run a watch-folder agent on a shared drive, or push files to a signed webhook. With remediate-on-ingest turned on, new documents are remediated as they arrive, at the level you chose. You download the verified files and publish them; connections do not write back to the source.
PDF remediation integrations: S3, watch folders and webhooksHuman review
A named reviewer on our team checks the remediated document in our review workbench and signs an attestation before the file is delivered. Use it where automation is least reliable and the stakes are highest: fillable forms, complex tables and legal notices. Turn it on when you request a fix, or arrange it with our team.
When PDF remediation needs human reviewDeveloper access
Public data endpoints for deadlines and entity statistics need no key, and signed webhook ingest pushes documents into your workspace. There is no customer API with keys yet. A full API is on a waitlist, and we would rather say so than imply it ships today.
The PDF accessibility API: what works today, and the waitlist
Every file, checked before you get it
Verification is the spine, not a feature
Five of the six parts find, fix or move documents. The sixth decides whether any of it worked.
From Level 2 up, every file is validated with veraPDF(opens in new tab) against PDF/UA-1 (ISO 14289-1). veraPDF is an independent, open-source validator, developed by a consortium led by the Open Preservation Foundation and the PDF Association. We did not write it, and a Level 2 or Level 3 file passes only when veraPDF reports zero failures.
The same threshold also requires our machine checks to pass and a DocoMatic Score of 95 or higher. Level 1 files are machine-checked and are not validated against PDF/UA.
If a file does not reach its level's threshold, you are not charged for it. Reserved credits are released automatically, and you can re-run the file, choose a higher level or add human review.
A real Level 2 report from our pipeline, made from a synthetic test document, not a customer file.
Scope
What this platform doesn't do
Scope, stated plainly, so you can rule us in or out quickly.
Not website or app accessibility. We remediate the documents you publish, not the pages around them. If your site itself needs work, you need a web accessibility tool alongside this one.
Not braille, large print or tactile formats. Some entities must provide them, and we do not produce them.
Not VPAT authoring, litigation support or legal advice.
Not a certification. No government body certifies documents as accessible, and we do not issue certificates. We remediate to technical standards and hand you the evidence. Whether that meets your legal obligations is a question for your counsel.
Not for one person with one document. If that is you, free tools for individuals are a better fit.
In your workflow
Where it sits in your workflow
Not a list of steps. What changes for your staff on Monday.
Before
Someone exports a PDF from Word and posts it. Nobody checks it, and it joins the other files nobody has counted.
After
Monitoring finds the file on its next scheduled scan and checks it. If it fails, it shows up in your alerts, and you send it to remediation in one click. Or a connection brings it in when it is saved, and remediate-on-ingest runs it at the level you chose. It comes back remediated, with its report, and a replacement list maps the original web address to the new file. You replace the posted file.
What your team actually does
Choose what gets remediated and at which level, then replace the published file. Everything between those two steps runs without you.
What doesn't change
Where documents live, who writes them, and the tools they are made in. Nobody has to learn a new editor.
Standards
What we remediate to
| Standard | What it is | Where it applies |
|---|---|---|
| WCAG 2.1 Level AA | The W3C success criteria for accessible web content, documents included | The standard adopted by the ADA Title II and HHS Section 504 rules, and incorporated in EN 301 549. Section 508 and the AODA cite WCAG 2.0 AA, which 2.1 AA includes. |
| PDF/UA-1 (ISO 14289-1) | The ISO standard for how an accessible PDF is built: tags, reading order, alternative text and metadata | The technical target veraPDF validates against, from Level 2 up |
WCAG describes what people need from content. PDF/UA describes how a PDF must be built to deliver it. A file can pass automated checks and still be hard to use with a screen reader, so each report lists what a machine could not verify.
- WCAG 2.1 AA for documents
- PDF/UA, explained
- Which accessibility law applies to your organization
- The three remediation levels and what each includes
General information, not legal advice. Talk to your counsel about your organization's obligations.
Roles
Who on your team runs this
| Role | What they do here | When |
|---|---|---|
| Clerk or communications staff | Choose which documents to remediate and at which level, then replace the published files | As you publish, or on a weekly routine |
| IT | Verify your domains, and set up an S3, watch-folder or webhook connection if you want one | Once, then as needed |
| ADA coordinator | Download verification reports and the monthly monitoring report for the record | As needed |
| Procurement or finance | Use a purchase order with net-30 to net-60 invoicing for larger orders; card payment opens with our billing launch. Invoices are paid by ACH, and a W-9 is available on request. Review our security documents. | When you buy |
There is no accessibility specialist in this table. That is deliberate. When the Department of Justice extended the Title II dates, it wrote that staff resources and availability continue to pose significant challenges
(91 FR 20902, at 20907)(opens in new tab).
FAQ
Frequently asked questions
General information, not legal advice. Talk to your counsel about your organization's obligations.
Buying for a larger organization?
View PDF accessibility pricingIs DocoMatic software, a service or both?
Do we need an accessibility expert on staff?
What happens to documents automation can't fix?
Can we use this alongside our website accessibility tool?
Does it work on documents that aren't on our website?
How is this different from converting PDFs to HTML?
What file types do you accept?
Can we try it on our own documents before buying?
Start with a count
See it on your own documents
Scan your site to see what you have. Or start a free trial and remediate your first documents this week. Every file comes back with its verification report.