2026-05-17 · 5 min read

PDF Accessibility and the DOJ Title II Rule: What Government Agencies Must Fix

# PDF Accessibility and the DOJ Title II Rule: What Government Agencies Must Fix

Most government accessibility conversations start and end with the website. Forms, navigation, keyboard access — these get the attention. The document library does not.

That is a problem. PDFs are the most common accessibility failure type on government sites, and the DOJ Title II Final Rule covers them just as much as it covers your homepage.

This post explains what makes a government PDF non-compliant, what the standard requires, and how to approach remediation before the April 2027 deadline.

PDFs Are Explicitly Covered by the Rule

The DOJ Title II Final Rule does not apply only to HTML web pages. According to ADA.gov, the rule covers "electronic documents such as PDFs, Word documents, and other file formats that are published on or accessible through a public entity's website or mobile app."

If your agency publishes PDFs — meeting agendas, budget documents, ordinances, permit applications, zoning notices, any document made available to the public through your website — those documents must conform to WCAG 2.1 Level AA.

Government agencies that are auditing their websites but ignoring their document libraries are not building a defensible compliance posture. They are auditing approximately half the problem.

What Makes a PDF Non-Compliant

Not all PDF failures are equal. Here is how they map to WCAG 2.1 success criteria:

1. Scanned image PDFs (automatically fails 1.1.1)

A PDF created by scanning a paper document and saving it as an image — without running OCR or adding a text layer — is inaccessible to screen readers. There is no text to read. It fails WCAG 1.1.1 (Non-text Content) absolutely.

This is the most common and most severe PDF failure on government sites. Meeting minutes from 2018, archived ordinances, historical budgets — if they were scanned and never remediated, they are non-compliant.

2. Missing tag structure (fails 1.3.1)

PDF accessibility requires a logical tag tree: document, headings, paragraphs, lists, tables, figures, and form fields must all be tagged in a way that communicates structure to assistive technology. An untagged PDF — including many PDFs exported directly from Word or InDesign without using the accessibility export settings — presents as an undifferentiated stream to a screen reader. WCAG 1.3.1 (Info and Relationships) requires that structure and relationships be conveyed through the markup.

3. Missing document title (fails 2.4.2)

Every PDF must have a document title defined in the document properties — not just in the file name. WCAG 2.4.2 (Page Titled) requires it. Screen reader users navigating between browser tabs identify documents by their title, not their URL. A PDF titled "Untitled" or "Microsoft Word - Q2_Meeting_Agenda.docx" fails this criterion.

4. Reading order errors (fails 1.3.2)

The tag order in a PDF determines how assistive technology reads the content. In multi-column documents, complex tables, or documents with sidebars, the visual reading order often does not match the underlying tag order. Screen reader users experience this as content that jumps around nonsensically. WCAG 1.3.2 (Meaningful Sequence) requires that the content reading order be determinable.

5. Missing form field labels and instructions (fails 1.3.1, 3.3.2)

PDF forms — permit applications, license renewals, payment forms, service requests — must have all fields labeled and all required fields clearly indicated. An interactive PDF form that sighted users can navigate visually may be completely opaque to a screen reader user if the form fields lack programmatic labels.

6. Missing alternative text on images and figures (fails 1.1.1)

Charts, maps, photographs, and decorative images embedded in PDFs all require appropriate treatment under WCAG 1.1.1. Informational images require alt text that conveys the content or function. Decorative images must be marked as artifacts so screen readers skip them.

7. Insufficient color contrast (fails 1.4.3)

Text in PDFs must meet the same 4.5:1 contrast ratio for normal text (3:1 for large text) that HTML content must meet under WCAG 1.4.3. Government documents often use light gray body text, gold or blue headers on colored backgrounds, or watermarks over text — all common contrast failures.

The PDF/UA Standard

PDF/UA-1 (ISO 14289-1) is the ISO standard for universally accessible PDFs. A PDF/UA-conforming document satisfies the structural accessibility requirements that WCAG 2.1 demands for PDF content.

W3C's PDF Techniques for WCAG 2.1 documentation maps specific PDF implementation requirements to WCAG success criteria. These techniques are the specific instructions for what a compliant PDF must contain: tag structure, reading order, alt text, document properties, language specification, and form field labels.

For government agencies building a compliance program, PDF/UA conformance is the target standard for new document production. It provides a documented, auditable basis for claiming that a PDF meets WCAG 2.1 requirements — which is exactly what DOJ enforcement documentation requires.

The Scale of the Problem

A government website may have dozens of HTML pages. The same agency may have thousands of PDFs. Meeting agendas going back years. Every ordinance ever passed. Every budget document, every annual report, every form made available to the public.

Remediating all of them before April 2027 is not realistic for most agencies. The defensible approach is:

1. Prioritize new documents. Establish a workflow that produces accessible PDFs going forward. Every meeting agenda, every new form, every new report produced after a certain date must meet the standard. Stop the bleeding before addressing the backlog.

2. Prioritize high-use documents. Identify the documents that residents actually access — the top 50 most-viewed PDFs by traffic, the current-year budget, all active forms, all currently-posted notices. Remediate these first.

3. Document your approach. A remediation plan that shows you have identified the scope, prioritized by impact, and committed to a timeline is defensible. An agency that has made no effort is not.

4. Post a notice for documents you haven't yet remediated. The Title II Final Rule allows agencies to provide accessible alternatives — if a document is not yet accessible, agencies can offer to provide the content in an accessible format upon request, provided they respond promptly. This is a bridge, not a solution, but it is recognized as an interim measure.

Getting a Baseline

Before you can prioritize remediation, you need to know what you have. A preliminary PDF audit — typically a sample of 50-100 documents across different content types — tells you the distribution of failure types, the proportion of scanned vs. tagged documents, and the estimated remediation effort.

The Parallax WCAG audit from Morton Technology Consulting covers PDF review as part of its 200-page government site assessment. The full audit includes document library sampling, failure categorization, and remediation prioritization — alongside the full HTML site review, manual testing with NVDA and VoiceOver, and a completed accessibility statement draft.

For agencies building their own assessment capability first, the WCAG Pre-Audit Readiness Kit ($149) includes a PDF review checklist covering the eight most common failure types, a remediation effort estimator, and a document inventory template for tracking your library scope.

---

*Morton Technology Consulting LLC, Tallahassee, FL. WCAG 2.1 audits and PDF accessibility remediation for Florida government agencies. [email protected]*

Morton Technology Consulting LLC — WCAG 2.1 AA audits for Florida government agencies. Parallax audit → · WCAG Readiness Kit → · All posts →