PDF Accessibility: The Hidden Compliance Problem Most Government Agencies Don't See Coming

The Document Problem Nobody Talks About

When government agencies start thinking about ADA Title II compliance, they usually think about their website. Does the homepage load correctly with a screen reader? Are the navigation menus keyboard accessible? Do images have alt text?

These are the right questions. But there is a parallel compliance problem that catches most agencies off guard: their documents.

The average government agency has hundreds or thousands of PDFs posted on its website. Budget documents. Meeting agendas and minutes. Environmental reports. Permit applications. Policy manuals. Many of these documents are years or decades old, created before digital accessibility was a compliance requirement. Almost none of them meet WCAG 2.1 Level AA.

The DOJ Title II final rule covers all of this.

Why PDFs Are Harder Than Web Pages

A web page is a living document. You can update it, fix the HTML, add alt text, change heading structure. The changes propagate immediately. Automated tools can scan it continuously.

A PDF is different. It is a fixed-format document with its own internal accessibility structure — or lack thereof. A PDF that looks perfectly readable on screen may be completely opaque to a screen reader if it was created without proper tagging.

The accessibility of a PDF depends on how it was created, not how it looks. A PDF exported from a properly structured Word document will generally have better accessibility than one created by scanning a paper document. A scanned document with no OCR processing is, from an accessibility standpoint, an image — there is no text for a screen reader to find at all.

What Makes a PDF Accessible

WCAG 2.1 applies to PDFs through a set of specific technical requirements. An accessible PDF must have:

• **Document tags**: A tagged PDF has a logical structure tree that screen readers can navigate. Untagged PDFs are essentially inaccessible.
• **Reading order**: The order in which content is read by a screen reader must match the visual reading order. Multi-column layouts, tables, and sidebars frequently create reading order problems.
• **Alternative text for images**: Every image, chart, graph, or decorative element must have appropriate alt text or be marked as decorative.
• **Accessible tables**: Data tables must have header rows identified and associated with their data cells.
• **Document language**: The PDF must specify its language so screen readers use the correct pronunciation rules.
• **Bookmarks**: Documents longer than a few pages should have bookmarks for navigation.
• **Accessible forms**: PDF forms must have labeled fields and be fillable by keyboard.

The Scale of the Problem

We have scanned hundreds of government websites and their associated documents. The pattern is consistent: web pages score in the 60-80 range on our compliance scale. PDF documents frequently score in the 20-40 range.

The most common issues we find:

• Scanned documents with no OCR (completely inaccessible)
• Exported PDFs with no tags (structurally inaccessible)
• Tables without header associations
• Charts and graphs with no alt text or description
• Multi-column layouts with scrambled reading order
• Forms that cannot be completed by keyboard

Many of these documents have been on government websites for years. Some have been downloaded thousands of times. Every download is a potential barrier for a constituent who uses a screen reader.

What the DOJ Rule Requires for Documents

The Title II final rule does not create a separate standard for documents — it applies the same WCAG 2.1 Level AA standard to all web content, which includes documents that are posted on or linked from government websites.

The rule does include a limited exemption for archived content that meets specific criteria: the content must be kept only for reference, research, or recordkeeping; it must not be actively promoted or linked from other content; and it must have been created before the compliance deadline.

In practice, this exemption is narrower than most agencies assume. A document that is linked from your current website navigation, that appears in search results, that constituents regularly download — that is not archived content by any reasonable interpretation.

Prioritizing Remediation

Few government agencies have the resources to remediate every document immediately. The practical approach is prioritization:

• **High priority**: Forms that constituents need to complete (permit applications, service requests, benefit enrollments)
• **High priority**: Documents required for legal or procedural compliance (public notices, meeting agendas, adopted budgets)
• **Medium priority**: Frequently accessed reference documents (program guides, fee schedules, contact directories)
• **Lower priority**: Historical documents with low traffic and no active use

An automated document audit can identify which of your documents have the most severe accessibility problems and help you focus remediation resources where they matter most.

The Workflow Problem

Document accessibility is not a one-time fix. Government agencies produce new documents constantly. Every new PDF posted without proper accessibility structure adds to the compliance debt.

The sustainable solution is process change: ensuring that documents are created accessibly from the start. This means training staff who create documents, establishing templates with proper heading and table structures, and implementing a review step before documents are published.

It also means monitoring. New documents should be scanned automatically when they are posted, flagging accessibility issues before they accumulate.

Getting a Baseline

The first step for any agency is understanding how many documents you have and what condition they are in. A document accessibility audit will crawl your website, identify all posted PDFs and other documents, and score each one against WCAG criteria.

The results are often sobering — but they are also the foundation of a defensible compliance plan. Knowing your baseline, prioritizing your remediation, and documenting your progress is exactly what good-faith compliance looks like under the DOJ rule.