PDF Remediation: The Complete 2027 Playbook for Government Teams
Every government website carries hundreds or thousands of PDFs, and under the DOJ ADA Title II web rule most of them are now a compliance liability. This playbook turns that pile into a plan: inventory, triage, and a single decision for every document, tag it, convert it, or delete it.
PDFs are the single largest accessibility exposure on most government websites. The good news: you do not have to fix all of them, and you do not have to fix them by hand. This playbook is the workflow we walk government teams through, built to hit the April 26, 2027 and April 26, 2028 deadlines covered in our complete 2027 ADA Title II guide.
1Why PDFs Are the Hardest Part of Title II
Web pages get audited and fixed. PDFs get uploaded and forgotten. The average agency site hosts 200 to 5,000 documents going back a decade or more: council packets, budgets, permit forms, meeting minutes, public notices. Almost none were built to be accessible, and every untagged one is a WCAG 1.1.1 and 1.3.1 failure that a screen reader user hits like a wall.
200 to 5,000
PDFs on a typical government site
20 to 30 min
to remediate one PDF by hand
80 / 20
of traffic usually hits a small share of files
2The Framework: Tag, Convert, or Delete
Every PDF on your site has exactly one right answer. The whole job is deciding which, then doing it in the right order.
The document must stay a downloadable file (legal records, forms designed for print). Add the tag structure, reading order, and alt text it needs to pass.
People actually read this content on your site. Rebuild it as a real web page, and keep the PDF as a download. This is the highest-value move for high-traffic documents.
Nobody needs it anymore, or it duplicates content that already lives on a page. Remove it or move it to a designated archive. The cheapest fix is the file that no longer exists.
We break the per-document decision down in depth in Tag, Convert, or Delete: a decision tree for every PDF.
3Step 1: Inventory Every PDF
You cannot triage what you have not counted. Start with a crawl that finds every PDF linked anywhere on your site and scores each one for accessibility. Do this before you spend a dollar on remediation, because the inventory tells you how big the job actually is.
4Step 2: Triage by Traffic and Service Criticality
Do not remediate in upload order. Rank every document on two axes: how many people hit it, and whether someone needs it to access a live service. That gives you four buckets and a clear order of operations.
High traffic + service critical
Fix first. A benefits form or tax appeal thousands of residents use is your biggest legal and equity risk.
High traffic + informational
Fix next, and strongly consider converting to a page so it becomes searchable and mobile friendly.
Low traffic + service critical
Fix, but batch it. Still legally required, just less urgent than the high-traffic forms.
Low traffic + informational
Prime delete or archive candidate. Confirm nobody needs it, then remove it and shrink the backlog.
5Step 3: Remediate the Documents That Must Stay Files
For everything in the tag bucket, the work is real but well defined: re-export a tagged PDF from the source file when you still have it, run OCR on scanned image-only documents to create a text layer, then fix reading order, add a document title and language, and write alt text for images. Our step-by-step remediation guide walks through each of these.
At scale, this is where an in-CMS scanner pays for itself. The WPPersona PDF Accessibility product ranks the backlog by risk and tracks remediation status per file, so a small team can work the queue instead of guessing.
6Step 4: Convert the High-Value Documents to Pages
Tagging a PDF makes it compliant. Converting it makes it usable. For the documents residents actually read, rebuild the content as a real web page and keep the original PDF as a download. The page is searchable, mobile friendly, translatable, and easy to update next year.
7Step 5: Govern So the Backlog Never Refills
The worst outcome is clearing 4,000 PDFs and quietly accumulating 4,000 more. Put a gate on new uploads so a document cannot publish until it passes a minimum accessibility score, and scan on a schedule to catch anything that slips in through migrations or the back door.
On WordPress, the PDF Accessibility Remediator plugin does this; on Drupal, the PDF Accessibility Remediator module ties the same gate to your File and Media entities.
8Your 90-Day Remediation Plan
Final Takeaway
PDF remediation feels overwhelming because agencies picture fixing every file by hand. You will not. You will inventory once, triage into four buckets, delete the dead weight, convert the documents people read, tag the ones that must stay files, and put a gate in place so it never happens again. That is a project with an end, not a treadmill.
Start with the number
See exactly how many PDFs on your site are at risk, ranked, in about two minutes. No account, no credit card.
Run a Free PDF Audit