How Poorly Tagged PDFs Deceive Screen Readers 

There’s a well-intentioned assumption that runs through a lot of IT departments: that some accessibility work is always better than none. If a PDF has some tags, it’s at least partially accessible, right? It’s better than nothing.

Not necessarily. In fact, when it comes to PDFs, a partially or poorly tagged document can create a worse experience for users with disabilities than a completely untagged one, and it can expose your organization to liability.

Here’s why that matters, and what to do about it.

What Happens When a PDF Is Completely Untagged

When a screen reader user encounters a PDF with zero tags, they know they have a problem. Most screen readers will alert the user immediately. It will say something like “this document is not tagged and may not read correctly.” That’s not a great experience, but it’s an honest one. The user knows the document is inaccessible and can make an informed decision: ask for an alternative format, contact the organization, or move on.

An untagged PDF is a known failure. It’s visible, it’s detectable by automated accessibility checkers, and it’s the kind of thing that gets flagged immediately in an audit. It’s bad, but it’s fixable and it’s transparent.

What Happens When a PDF Is Poorly Tagged

A partially or incorrectly tagged PDF is a different beast entirely. The screen reader sees tags and assumes the document has been prepared for accessibility. It doesn’t know the tags are wrong, incomplete, or misleading. So it reads whatever it finds faithfully and without warning.

What that sounds like in practice can range from mildly confusing to completely incomprehensible:

• Reading order chaos — in a multi-column layout or a document converted from PowerPoint, the screen reader may read across columns instead of down them, or jump from a headline to a footer before finishing the body text. The words are all there, but the meaning is scrambled.
• Garbled tables — a table with missing or incorrect header tags gets read as a stream of disconnected data cells. A screen reader user trying to understand a financial statement or a comparison chart has no way to know which row or column a number belongs to.
• Inconsistent alt text — a document where some images have alt text and others don’t creates a patchwork experience. Decorative images that aren’t properly marked as such get read aloud as clutter. Informative images with no alt text get silently skipped, leaving gaps in the content.
• Phantom or misapplied tags — automated tagging tools sometimes apply tags to artifacts like page numbers, headers, footers, or background elements, causing them to be read aloud mid-sentence. Others miss real content entirely.

In every one of these cases, the user receives no warning that something is wrong. The screen reader is doing exactly what it’s supposed to do — following the tags. The document is the problem, and the user has no way to know that. The user wasted time trying unsuccessfully to complete a task, and as a result they have a negative perception of your  brand.

The Liability Problem With “Good Enough” Remediation

From a compliance standpoint, a poorly tagged PDF fails users and potentially makes your legal position worse.

Here’s the uncomfortable reality: a completely inaccessible document demonstrates a lack of effort. A poorly remediated document demonstrates an attempt at compliance that still fails to meet the standard. In the context of an ADA complaint or a Section 508 audit, that distinction matters. It can signal that your organization understood the obligation, took a partial step, and stopped, which is harder to defend than simply not having started yet.

WCAG 2.1 Success Criteria don’t give partial credit. A document either meets the standard or it doesn’t. Tags that are present but incorrect don’t bring a document into compliance, they just make it harder to detect that it isn’t.

How This Happens in the First Place

Poorly tagged PDFs are usually the product of one of three things:

Over-reliance on auto-tagging. Many PDF creation tools and basic accessibility checkers include an auto-tag function. These tools struggle with anything complex, such as multi-column layouts, tables, forms, images with meaningful content, or documents with unusual formatting. Auto-tagging a document and calling it done is one of the most common sources of the “silent failure” problem.

Inconsistent manual remediation. When remediation is done manually by staff who haven’t been fully trained, or when it’s rushed to meet a deadline, it often results in documents that are partially tagged. While some elements are correct, others are missed or mislabeled.

No quality review step. Tagging a document and testing it are two different things. Quality testing a PDF for accessibility means actually running the document through a screen reader. Organizations that remediate without a testing step have no way of knowing whether the tags they applied are doing what they’re supposed to do.

What Good Remediation Actually Looks Like

Genuinely accessible PDFs are tagged correctly and completely. That means:

• A logical reading order that reflects the intended flow of the document
• Correctly identified headings that create a navigable document structure
• Meaningful alt text for informative images, and artifact tags for decorative ones
• Properly structured tables with tagged headers and data cells
• Forms with properly labeled fields and instructions
• Language tags so screen readers use the right pronunciation engine

It also means testing. Every remediated document should be verified with a screen reader, a robust accessibility checker, or ideally both before it’s considered done.

The Bottom Line for IT Teams

If your organization has done some PDF remediation work, that’s a great start. But it shouldn’t stop there. The quality of remediation matters as much as the quantity. Checking a box that says “tagged” isn’t the same as checking a box that says “accessible.”

For teams overseeing large document libraries or remediation workflows, the key questions to ask are: How were these documents tagged? By what tool or process? And has anyone tested them with a screen reader?

If the answers are uncertain, it may be time to take a closer look.

Use the Right Tools

Equidox is designed to go beyond basic auto-tagging, using AI-powered tools that handle complex document structures accurately. This gives your team the ability to review and verify results before a document is published. If your organization is working through a remediation backlog and wants confidence that the output is genuinely accessible, not just technically tagged, we’d be glad to show you how it works.

 

Nina Overdorff

Nina comes to Equidox with years of sales and marketing experience from a variety of industries and holds a BS in Language Arts Education. Nina has a passion for words, storytelling, and information, which she believes everyone should have access to regardless of ability. After spending time as a teacher with a blind student, she became much more aware of the limitations and abilities of web accessibility, and how essential it is to those experiencing disabilities. “Being able to access information equally ensures that everyone has an equal opportunity for education, employment, and success in life.”