PDF Remediation and Web Accessibility

Subheader

What Organizations Need to Know

Featured Image

two adult professionals discussing work in an office setting

Lead-in

Most state and local organizations are aware by now that new accessibility deadlines are coming. The real question is whether you’re ready for them.

In April 2024, the Department of Justice updated its regulations under the Americans with Disabilities Act (ADA), expanding what qualifies as “web content” and clarifying who must comply. These updates have major implications not just for websites, but for documents—especially PDFs.

Let’s break down what changed, how it affects your organization, and what practical steps you can take to get compliant.

Sections

The updated regulations expand accessibility requirements in two important ways:

First, all web content must meet accessibility guidelines. This now explicitly includes not just web pages, but also online applications, videos, and documents like PDFs.
Second, the rules apply broadly—to all state and local government organizations, as well as any organization that receives government funding, such as nonprofits providing public services.

For websites, accessibility requirements have been relatively well understood– typically measured against WCAG 2.1 standards. Documents, however, are another story.

PDFs are one of the most common ways organizations share information online—from reports and forms to regulations and applications. In fact, PDFs are second only to HTML as the most widely used online content format.

If your organization has been publishing content online for years, there’s a good chance you have:

A large number of PDFs
Limited visibility into where they all live
Little to no confidence that they’re accessible

That’s not unusual—and you’re not alone. PDF accessibility has historically been overlooked, even by well-intentioned organizations.

The good news is that this problem is manageable if you approach it step-by-step.

abstract image of waves that look like pages of paper

PDFs aren’t inherently bad.

But an overreliance on them creates real challenges. Compared to web pages, PDFs are often:

Inaccessible to screen readers and keyboard users
Not responsive on mobile devices
Difficult to update, track, and govern over time

For these reasons, we generally recommend moving away from PDFs on your website whenever possible. HTML pages are easier to maintain, more accessible by default, and better for users.

That said, some documents still need to exist as PDFs for legal, business, or user-experience reasons. The key is being intentional.

Before you can fix anything, you need to know what you have.

Start by creating a content inventory of all PDFs available on your website. For very small sites, this might be done manually. For most organizations, it’s best handled with a site crawler like Screaming Frog and exported into a spreadsheet.

Each row should represent a single document.

This step can feel tedious, but it’s foundational. You can’t make informed decisions about accessibility without a clear picture of your content.

Once you have an inventory, begin reviewing each document and add key details, such as:

When it was last updated
Who owns or edits it
How much traffic or how many downloads it receives
Whether the original source file still exists (Word, InDesign, etc.)

This is where many organizations realize that a significant portion of their PDFs are outdated, unused, or no longer necessary.

As you work through each document, next ask:

Is this still actively used?
Does it need to be available online?
Could this content be delivered as an HTML page instead?

From both an accessibility and maintenance standpoint, HTML is almost always preferable. Only keep PDFs when there’s a clear reason to do so.

After you’ve narrowed your list, you can begin evaluating the remaining PDFs for accessibility.

Start with automated accessibility checkers. Tools like Adobe Acrobat and other PDF accessibility scanners can help identify common issues, such as:

Missing document titles or language settings
Incorrect or missing tag structure
Untagged images
Color contrast problems
Table and list errors

Automated tools won’t catch everything, but they’re an essential first step.

Making PDFs accessible is often referred to as PDF remediation.

The goal is to ensure that documents have proper semantic structure and can be understood by assistive technologies. This typically includes:

A logical reading order
Proper heading structure (H1–H6)
Correct tagging for paragraphs, lists, and tables
Alt text for images, charts, and graphics
Document-level settings like title and language

Tags are the backbone of accessible PDFs. They provide the structure that screen readers rely on to interpret content meaningfully.

After automated testing, manual testing is essential. Navigate the document using only a keyboard and listen to it with a screen reader. If it doesn’t make sense audibly, it’s not accessible.