How to Audit Your Government Website's PDF Accessibility (Free Method)
A practical, free method to create visibility, document due diligence, and build a prioritized remediation plan — written for SLED environments.
A Familiar SLED Moment: The “PDF Problem” No One Owns
Picture this. It's late in the budget year and you're a city CIO, state web manager, or district communications lead. A disability advocacy group has just emailed your agency citing concerns about inaccessible PDFs — board agendas, program applications, policies, maybe even IEP forms. Legal forwards it with a subject line that makes your stomach sink: “Are we compliant with Section 508 / WCAG?”
You don't have money encumbered for a full accessibility audit this quarter. Your web team is already drowning. Your content owners are scattered across departments and your “CMS governance” is mostly tribal knowledge.
But you also know two things:
- If you ignore this, it will come back as an audit finding, media story, or complaint.
- You can't fix 10–20 years of PDFs overnight.
This is the reality in most SLED environments. The trick is not perfection; it's building a defensible, repeatable method to (1) find the worst issues, (2) document your due diligence, and (3) lay the groundwork for a more formal audit and remediation plan. That's what this guide is about: a practical, free method to audit the accessibility of PDFs on your government website.
Why Most SLED Orgs Approach PDF Accessibility the Wrong Way
In many state agencies, PDF accessibility is either treated as a one-time “project” or as a vague compliance requirement that no one owns. Typical failure patterns:
"We fixed the website, so we're compliant."
The HTML shell is accessible, but the actual content — forms, handbooks, policies — lives inside untagged PDFs that screen readers can't navigate.
"We'll just ask every department to fix their PDFs."
Without inventory, training, or guardrails, this creates chaos and very little measurable progress.
"We'll wait until we can fund a full audit."
Delaying basic triage leaves you exposed if there's a complaint or investigation; you have no data to show effort or progress.
Core stance
For SLED organizations, PDF accessibility must start as a risk-based content governance problem, not a tooling problem.
The right free tools help, but the real leverage comes from:
- Knowing what you have.
- Knowing which PDFs matter most.
- Showing that you're taking reasonable, documented steps each quarter.
What “Accessible PDF” Actually Means in Practice
You don't need to become a standards lawyer, but you do need to understand what auditors and advocates look for. At a practical level, accessible PDFs include:
Tags and structure
The PDF is "tagged" so assistive technologies can identify headings, paragraphs, lists, and tables and follow a logical reading order.
Text, not images of text
Scanned forms or old agendas that are just images with no OCR'd text are effectively invisible to screen readers.
Alt text for meaningful images
Charts, diagrams, or icons that convey information include meaningful alternative text.
Usable tables and forms
Tables are tagged correctly; form fields have labels and can be navigated with a keyboard.
Contrast and basic legibility
Text has sufficient contrast and isn't buried in busy backgrounds.
A formal audit will map all this to Section 508 and WCAG criteria, but your pre-audit goal is simpler: identify where your PDFs clearly fail these basics and where you need deeper review.
A Free, Step-by-Step Method to Audit Your Website's PDFs
You're not certifying compliance — you're creating visibility and a prioritized plan using free or low-friction tools and processes.
Build a Lightweight PDF Inventory
You can't manage what you can't see. Before you worry about accessibility checks, you need a rough list of PDFs.
- 1
Crawl or search your own site for PDFs.
- Use your existing search (e.g., filter on "filetype:pdf").
- Many agencies also use their hosting or analytics tools to export lists of PDF URLs.
- Note: Some tools offer free or trial PDF discovery specifically for government — they can quickly list and classify PDFs across your domains.
- 2
Capture just enough metadata to be useful.
For each PDF, track:
- URL
- Title or file name
- Department / owner (if you can infer it from the path)
- Last modified date
- Page views or download counts (if analytics are available)
- 3
Flag "critical" content types.
Add a column to mark PDFs that directly affect public access:
- Forms (applications, complaints, permits)
- Legal notices, policies, procedures
- Instructional materials and parent communications in districts
- Program eligibility or benefits information
You're not aiming for a perfect catalog on day one. The inventory should be “good enough” to identify high-risk clusters.
Prioritize Using a Simple Risk Model
To avoid overwhelm, apply a simple scoring model to each PDF or group of PDFs:
Impact
Usage
Age / Relevance
Priority Score
Priority = Impact + Usage + Age
Start your checks with the highest scores. When leadership or legal asks, you can say: “We've focused first on the documents that most affect residents, students, and staff.”
Use Free PDF Accessibility Checkers for Quick Triage
Several free tools can give you a fast read on whether a PDF has basic accessibility issues.
Online or desktop PDF accessibility checkers
Tools designed to test PDFs for conformance with PDF/UA and WCAG can quickly flag missing tags, role maps, and structural problems.
Free or trial AI-assisted audit tools
Some newer platforms for governments and universities will automatically discover, scan, and classify PDFs for accessibility and policy compliance, often with a free tier or pilot.
How to use them in a pre-audit workflow:
- 1Take your top 20–50 high-priority PDFs from the inventory.
- 2Run them through one or more free checkers.
- 3Record a simple status in your spreadsheet: "Passes basic checks," "Fails structural checks" (no tags, bad reading order), or "Scanned image only."
- 4Add a notes column for obvious issues (e.g., "No tags; complex tables; scanned signature page").
Do Quick Manual Checks That Reflect Real Users
Automated tools can't see everything. A manual sniff test goes a long way, and it's something you can train non-technical staff to do.
Open with a screen reader or text-to-speech tool.
- Logical reading order (does it jump around columns or headers?)
- Heading announcements (are sections identified?)
- Whether tables are read in a sensible way.
Try selecting and copying text.
- If you can't select text, it's likely a scanned image and inaccessible without OCR.
Tab through form fields.
- The tab order follows the visual layout.
- Fields have meaningful labels announced.
Check for obvious visual barriers.
- Very light text, embedded text in images, or instructions that rely only on color are red flags.
Document these observations in your spreadsheet so you can show that your organization is not just running tools but actually checking real-world usability.
Classify PDFs into Four Actionable Buckets
Many SLED agencies get stuck because they don't know how to turn findings into a practical plan. A pattern that works well is this four-bucket model:
Fix Now
Critical forms, policies, or notices that are frequently used. Issues are fixable with existing skills or vendor support (e.g., re-exporting from Word, basic tagging). These go to the top of your remediation queue.
Replace with HTML or Web Forms
Content that doesn't need to be a PDF. Recurring information, FAQs, or policy text that is better as a web page. Over time, this reduces your "PDF surface area" and future audit burden.
Archive with Clear Labeling
Low-traffic, historical content that you're required to retain but not actively promote. Keep it available upon request and add a clear note: "If you need this in an accessible format, contact [email/phone]."
Retire or Consolidate
Duplicative, outdated, or unnecessary PDFs. Removing them is the fastest way to reduce risk.
This bucket approach reflects real SLED constraints: you can't remediate everything at once, but you can show a reasoned, documented plan.
A Realistic Mini Case: A Mid-Size County's Pre-Audit
A mid-size county IT director gets word that the state auditor will be looking at digital accessibility. The county doesn't have budget for a full audit yet, but they don't want to be blindsided. Here's how they apply the free method:
- Communications runs a site search and exports a list of ~1,200 PDFs.
- An intern helps categorize them by department and flags high-impact items: permit applications, tax documents, election materials, and public health advisories.
- Each PDF gets a simple priority score based on impact, usage, and age.
- The top 100 high-priority PDFs are scanned with a free accessibility checker and a limited pilot of an AI-based PDF audit tool.
- Results show that many election documents and tax forms are untagged or scanned images, and several public health notices are accessible enough with minor fixes.
- A small working group — IT, Communications, and the ADA coordinator — manually checks a sample of critical PDFs using keyboard and screen reader tests.
- They classify PDFs into the four buckets: fix now, convert to HTML, archive, retire.
- They decide to rebuild the top five forms as HTML in their CMS, reducing PDF reliance for high-volume interactions.
- The IT director documents the process, findings, and decisions in a short memo, with the spreadsheet attached.
- When budget planning comes around, they use this data to justify funding a formal accessibility audit and targeted remediation support.
- If questioned by auditors or advocates, they can show a defensible, risk-based approach and a living remediation plan — not just good intentions.
This is not a perfect solution, but it's a credible one that fits the rhythm of real SLED funding cycles and staffing realities.
How to Turn This Process into Part of Your Brand of Governance
Accessibility work isn't just compliance; it's part of your agency's brand. Here are ways to make this pre-audit process build your brand rather than just fill a checkbox:
Adopt a clear point of view.
Instead of treating accessibility as "IT's problem," frame it as a core equity, inclusion, and service quality issue. Make it part of your public narrative: "We believe residents shouldn't need perfect vision or motor skills to access county services."
Make your framework your "signature."
The simple model in this post — Inventory → Prioritize → Triage → Bucket — can become your standard internal playbook for documents. Use the same language in briefings, RFPs, and training.
Talk specifically about your constraints.
Acknowledge grant timelines, RFP cycles, and the reality that accessibility work often happens in the margins of people's jobs. This honesty builds trust with both staff and the public.
Signal quiet authority.
"A common issue we see across departments is that PDFs are created by staff who never see the public side of the process." It reminds people you're learning from experience, not just from standards documents.
Share progress publicly.
Without over-promising, publish a short note on your website that explains how you're improving digital accessibility and invite feedback. This turns a potential liability into a story about continuous improvement.
Bringing It All Together
If you're a CIO, web manager, superintendent, or agency leader staring at a sea of PDFs, you don't need to wait for a big contract or a formal audit to act. You can start now — using free tools and a practical framework — to:
- Know what you have.
- Focus on what matters most.
- Document reasonable, good-faith effort.
- Build a culture that treats accessibility as part of service quality, not just compliance.
That is how a simple, free PDF accessibility audit becomes part of a stronger, more trustworthy public-sector brand.
Run a free PDF accessibility audit
WPPersona's free PDF audit tool scans your agency's PDFs and gives you a prioritized report — no account required.
Run Free PDF Audit