Government Website PDF Remediation: A Step-by-Step Guide
Most “PDF accessibility projects” in government don't fail because the tools are bad. They fail because the work is treated like a one-off cleanup instead of a disciplined, ongoing service woven into how your agency publishes information.
Below is a practitioner-level guide you can hand to your web, IT, and records teams and actually use. It's written for people who live in the world of grant deadlines, procurement rules, and legislative calendars — not in a vendor slide deck.
Imagine This: A Quiet Audit That Isn't Quiet
Imagine you're a state CIO or a district technology director. It's 4:30 p.m. on a Thursday when legal forwards an email: an advocacy group is requesting all documentation on how your agency ensures digital accessibility — specifically PDFs on your public website.
You know what they'll find:
- Thousands of legacy board minutes and budget books scanned as flat images.
- "Accessible" PDFs generated from Word that were never actually tagged.
- A handful of fixes done after a previous complaint, with no ongoing process behind them.
No one is malicious. You're just buried under priorities: cybersecurity, ERP modernization, student data privacy, constituent portals. But now, PDF accessibility is an immediate legal, political, and human issue. This post is about what to do next — practically, sustainably, and in a way that reduces risk instead of just rearranging it.
The Real Problem: PDFs Are Where Policy Meets Reality
Can people actually read and use the PDFs on your website?
Here's why this is such a stubborn problem in state, local, and education environments:
PDFs are the "final" record.
They're how you post budgets, policies, IEP forms, RFPs, and meeting minutes. Externally, the system of record is often a PDF.
Most legacy content is inaccessible by design.
"Print-first" thinking led to scanned board packets, image-only agendas, and exported documents with no tags, no headings, and broken reading order.
Governance rarely touches documents.
You may have decent web governance for HTML pages, but PDFs are usually created and posted by dozens of departments with no central review.
Funding cycles don't fit the problem.
You can't remediate 15 years of archives with a one-year grant and call it done. New PDFs are uploaded every week.
Compliance is an unfunded mandate.
Legal risk is real, but accessibility often isn't a line item. It's squeezed into existing roles and contracts.
The real question
How do we build a repeatable, accountable PDF remediation service that fits SLED constraints — budget cycles, procurement rules, inter-department politics, and all?
A Pragmatic Framework: The SLED PDF Accessibility Ladder
Here's a simple, opinionated framework you can use in conversations with leadership, vendors, and internal teams. Think of it as a three-rung ladder:
Stabilize
Stop making the problem worse.
Remediate
Fix what matters most, in the right order.
Modernize
Move away from PDFs where they hurt citizens the most.
Stabilize: Stop the Bleeding
Your first job isn't to fix everything. It's to make sure tomorrow's PDFs aren't piling onto the problem.
Set a "no new bad PDFs" policy.
- Start from an accessible source (Word, Google Docs, InDesign) with styles and headings.
- Export with tagging turned on.
- Run a basic accessibility check before publishing.
Limit who can publish PDFs.
On many SLED sites, anyone with CMS access can upload a file. Tighten this so that PDFs go through a trained publisher or web team.
Create a simple pre-publish checklist.
- Meaningful title set.
- Language set (e.g., en-US).
- Logical headings (not "bold and bigger").
- Images with alt text (or marked decorative).
- Reading order passes a spot-check.
Prioritize high-traffic, high-risk areas.
- Forms used by the public (applications, complaints, registrations).
- Legal/rights information (special education, civil rights, public notices).
- Current-year budgets, policies, and meeting materials.
Trade-off: You won't be compliant overnight, and that's uncomfortable. But stabilizing is the only way to ensure each remediation dollar spent isn't undone by tomorrow's uploads.
Remediate: A Step-by-Step Approach That Works in Reality
Once you've stabilized, you can tackle existing content. Broadly, you'll see three PDF types on a typical government site:
Tagged PDFs — Best-Case Scenario
Documents created with some accessibility in mind, often from Word or InDesign with tagging turned on.
Your goal: Validate and correct, not rebuild.
- 1
Verify document properties.
- Confirm the title is meaningful (e.g., "2026 City Budget – Accessible Version," not "Final_Budget_v7.pdf").
- Confirm the document language is set (e.g., en-US).
- 2
Check the tag tree.
- Make sure headings follow a logical order (H1, H2, H3).
- Ensure lists, tables, and paragraphs are tagged correctly.
- 3
Review images and graphics.
- Add alt text that's meaningful in context, or mark purely decorative graphics as artifacts.
- For complex charts, consider linking to an HTML table or providing a separate data file.
- 4
Validate reading order.
- Use a screen reader simulation or reading order tool to ensure the document flows in the same order as a person would reasonably read it.
- 5
Run an accessibility checker and remediate remaining issues.
- Automated tools won't catch everything, but they're useful for missing tags, title, language, and basic structural issues.
Untagged Exported PDFs — The “Accidental” Problem
PDFs that look fine visually and allow text selection, but have no underlying tag structure. Extremely common for school districts and local governments that “Print to PDF” or use default export settings.
You have two choices: go back to the source or fix in the PDF. If you care about long-term sustainability, going back to the source is almost always better.
Preferred path: Re-export from the source
- 1
Locate the source file.
Word, Google Docs, PowerPoint, InDesign — whatever was used. If multiple departments contributed, coordinate across teams.
- 2
Fix accessibility in the source.
Use true headings and styles. Ensure list formatting is correct. Replace text boxes and floating elements with anchored content. Add alt text to images.
- 3
Export to PDF with accessibility turned on.
Use the "Best for electronic distribution" or "Tagged PDF" options. Avoid "Print to PDF," which often strips tags.
- 4
Run a PDF accessibility check and do final touch-ups.
Tidy up any minor issues in the PDF itself.
Fallback path: Tag directly in the PDF
If the source is gone or irretrievable:
- 1
Autotag as a starting point.
Use an autotag function to create an initial structure.
- 2
Manually correct headings, lists, and tables.
These are where autotagging most often fails.
- 3
Fix reading order and link annotations.
Ensure screen reader users encounter content in a meaningful way.
- 4
Validate and document what you did.
For high-risk documents, note your remediation approach in case of future questions.
Trade-off: Fixing in the PDF may be faster for one-off documents, but it locks you into repeated manual work. Rebuilding accessibility in the source takes more upfront effort but pays off every time the document is updated.
Scanned PDFs — The Hardest Nut to Crack
Years of board packets, HR forms, or legacy policies that exist only as scanned images. Here, you must first decide: Is a PDF still the right format at all?
If you truly must keep a PDF:
- 1
Run OCR to add a text layer.
Choose an option that maintains visual layout while creating searchable text.
- 2
Autotag the document.
This gets you a basic structure to build on.
- 3
Manually review and correct.
Fix headings, tables, and lists. Confirm that the reading order follows the logical flow.
- 4
Add alt text or alternative descriptions.
Especially for any embedded images or diagrams.
For forms or dense policy text, consider a different path:
Replace the PDF with an HTML page for the current version.
Keep the original PDF as a non-public archive if required by records laws. Provide clear links to "current policy (HTML)" vs "archived records."
For forms, move to accessible web forms.
Integrate with your existing workflow, even if the backend still uses PDF internally.
Trade-off: Fully remediating large volumes of scanned PDFs is expensive. For many agencies, the smarter move is to remediate a small number of high-value documents and transition current content to HTML or web forms.
Modernize: When PDF Isn't the Best Answer
Many SLED organizations quietly go wrong by treating PDFs as the default format for everything. Consider HTML instead when:
Information changes frequently
Program eligibility, meeting schedules
Content is long and reference-heavy
Policy manuals, parent handbooks
Users need to interact with the content
Applications, registrations, complaints
This doesn't mean “no PDFs.” It means PDFs are a deliberate choice, not the default.
How to Operationalize This in a SLED Environment
Even the best technical plan fails without a workable operational model. The turning point for many agencies is treating PDF accessibility as a service, not a side-task.
Establish a Simple Service Model
- Define which documents qualify for remediation (public-facing, high-traffic, essential services, legal).
- Define how departments request remediation (form, ticketing system) and standard turnaround times.
- Clarify who is responsible for source-level accessibility (content owners), PDF remediation (central team or vendor), and final publishing (web team or records).
Use Your Funding Realities to Your Advantage
PDF remediation often spans multiple fiscal years. Use one-time funds (ARPA, grants, settlements) to clean up high-risk legacy content, stand up tooling and training, and pilot HTML transitions. Use ongoing operating funds to support a small central accessibility team and embed accessibility requirements into contracts and RFPs.
Make Accessibility Part of Procurement
Most SLED organizations unintentionally buy inaccessible PDF-generating machines. In your RFPs and renewals:
- Require vendors to demonstrate accessible PDF output (not just claim it) and provide VPATs and sample documents.
- Include accessibility in evaluation scoring.
- Tie acceptance criteria to document accessibility, not just feature lists.
A Realistic Mini-Case: From Panic to Practice
A mid-sized county realizes, after a complaint, that its health department site hosts hundreds of inaccessible PDFs: clinic schedules, vaccine consent forms, eligibility information, and program flyers. They have no dedicated accessibility staff, a lean IT team, and a fixed budget already spoken for by other projects.
- Stabilize by issuing a directive: all new public health documents must use accessibility templates and go through a central publishing queue.
- Identify the top 50 PDFs used by the public (clinic forms, notices, eligibility info).
- Contract for targeted PDF remediation of the top 50 documents instead of trying to fix everything.
- For three core forms, work with IT to create accessible web forms, leaving PDFs only for archival records.
- Two staff members from communications and IT are trained as internal "PDF stewards."
- Templates for Word and Google Docs are rolled out to content owners.
- A simple intake process and SLA are defined for new remediation requests.
- The county updates CMS publishing guidelines to require an accessibility check before any PDF goes live.
- In a new EHR/case management RFP, they require accessible exports and HTML options, reducing future remediation needs.
By the end of the year, they haven't solved everything — but they've moved from reactive panic to a sustainable, auditable process that any auditor or advocacy group can see and understand.
Closing Thought: Accessibility as a Governance Choice
PDF remediation is not glamorous. It won't earn the same headlines as your new portal or cybersecurity initiative. But it sits at the intersection of equity, compliance, and trust.
The organizations that get this right:
- Stop creating new inaccessible PDFs.
- Focus on the documents that matter most.
- Use accessibility as a lens in procurement and modernization.
- Treat document accessibility as an ongoing service, not a one-time project.
Start with a free PDF audit
Use WPPersona's free tool to scan your agency's PDFs and get a prioritized list of what to fix first.
Run Free PDF Audit