Imagine a benefits claimant sitting down to complete a government form. She opens the PDF, fires up her screen reader, and hears "Document has no accessible text." The form exists. It's even been updated this year. She just can't use it.
That scenario plays out across universities, healthcare systems, and government agencies every day, and the organizations responsible have no idea it's happening because the file looked fine in Preview.
PDF accessibility is a governance problem that most organizations are treating as a formatting problem, which means they're fixing the wrong thing at the wrong scale. An accessible PDF is one whose content can be perceived and navigated by users of assistive technology, not merely one that renders correctly on screen. This distinction matters enormously, because standard PDF document creation workflows produce inaccessible output by default. Every print to PDF from Word, every exported report, every scanned intake form: potentially inaccessible unless accessibility is deliberately built in. In most cases, it isn't.
This article covers what PDF accessibility problems are, what they do to real users, and what the law now requires, so you can understand the full scope before deciding how to act. Digital accessibility starts with knowing where the gaps are.
Here's what you'll come away with:
- Understand what makes a PDF inaccessible and who it locks out.
- Recognize the five primary failure modes and their real-world user impact.
- Identify which compliance frameworks apply to your organization and its deadlines.
- Assess why your PDF problem is almost certainly larger than you think.
Let's start with how inaccessible PDFs affect people who depend on assistive technology.
What inaccessible PDFs do to users and why the scale is larger than you think
The barriers created by inaccessible PDFs are complete lockouts. A screen reader user who encounters an untagged PDF doesn't have a frustrating experience. They get silence. And because inaccessibility is the default output of most PDF creation workflows, the number of documents creating that silence in any organization that's been publishing PDFs for years is almost certainly in the hundreds or thousands.
Personally, the most clarifying way I've found to understand this is to think about what a screen reader needs to do its job. It needs structure: tagged headings for navigation, a defined reading order, alt text for meaningful images (with decorative images appropriately marked), and labeled fields in PDF forms.
An untagged PDF has none of that. When a screen reader encounters one, it either announces "document has no accessible text" or reads the content in whatever order the PDF renderer encounters it, which can mean a three-column policy document is read left-to-right across all columns at once, turning coherent information into noise.
The primary failure modes, and what they mean for users:
| Failure | What it means in practice |
|---|---|
| Missing tags | No document structure; screen readers can't navigate headings or sections |
| Incorrect reading order | Content read out of sequence; multicolumn layouts become incomprehensible |
| Absent or incorrect alternate text | Informational images, charts, and graphs are inaccessible; decorative images lack null alt text, causing noise for screen reader users |
| Inaccessible tables | Data cells read without row or column context |
| Non-descriptive link text | Links announces as "click here" with no destination information |
These failures don't affect a narrow edge case. Screen reader users (blind or low-vision) depend on tags and reading order in every document they encounter. Keyboard-only users, including people with motor disabilities who can't use a mouse, need a navigable structure to move through accessible PDF forms and multipage documents. Users of screen magnification software need logical flow so that content remains readable when zoomed to 400 percent.
The scale argument is the part that organizations consistently underestimate. If your organization has been publishing PDFs for five years using standard office tools, the backlog isn't five documents. Think about what gets exported as PDF: annual reports with charts that need alt text, HR policy packets, procurement forms, training materials, course syllabi, patient intake documents, and compliance notices. Each one is a new inaccessible file unless someone actively built accessibility in, and most publishing workflows never ask that question.
For documents actively used to deliver services and programs, the scope is significant. The DOJ's preexisting-document exception applies only to legacy content not currently used to access programs or services, meaning any high-traffic or service-facing PDF is in scope, regardless of when it was created.
The legal exposure: ADA Title II, Section 508, and the EAA
PDF accessibility has real deadlines, named regulators, and an enforcement record. The DOJ and the Department of Education's Office for Civil Rights have pursued resolution agreements and consent decrees against universities and municipal agencies for digital access failures, including failures involving inaccessible documents.
Teams treat PDF accessibility compliance as something to sort out eventually, right up until a complaint triggers a formal investigation. The frameworks don't wait.
ADA Title II
State and local governments and public universities are under the most immediate pressure. The DOJ's updated rule explicitly puts documents within scope, so PDFs are not a web page problem alone. However, the rule includes narrow exceptions for certain archived content and some preexisting third-party materials. April 2027 is the deadline for larger entities (populations over 50,000), and April 2028 for smaller entities and special district governments, following a one-year extension the DOJ issued by Interim Final Rule on April 20, 2026.
Document properties such as tagging structure, reading order, and form field labels are all within scope. The DOJ has already pursued higher education institutions and municipal agencies for digital access failures, and the ADA Title II document accessibility requirements show exactly what's at stake.
Section 508
Federal agencies and their contractors operate under Section 508 of the Rehabilitation Act, which requires accessible information and communication technology (ICT), including PDFs, when that ICT is developed, procured, maintained, or used on behalf of a federal agency. If your organization delivers ICT products or services under a federal contract, Section 508 applies to those deliverables. Organizations receiving federal financial assistance face parallel obligations under Section 504 of the Rehabilitation Act. Note that Section 508's technical baseline is WCAG 2.0 Level AA (per the 2018 Revised Standards), while ADA Title II requires WCAG 2.1 Level AA, meaning they are different versions with different requirements.
EAA
The EAA, Directive (EU) 2019/882, became enforceable on June 28, 2025. It applies to businesses in specific covered sectors (including e-commerce, banking, transport, telecommunications, and e-books) that provide consumer-facing products or services in EU markets. Notably, microenterprises, businesses with fewer than 10 employees and annual turnover below €2 million, are exempt from its service-side requirements.
Technically, organizations demonstrate conformance with EAA requirements by meeting EN 301 549, the harmonized European ICT accessibility standard, which incorporates WCAG 2.1 Level AA as its web and document content baseline and also covers hardware, software, and electronic documents. PDF/UA is additionally recognized under EN 301 549 for document-specific accessibility.
For any multinational organization operating in covered sectors and providing consumer-facing services in EU markets, this runs as a parallel obligation alongside domestic frameworks. Importantly, because the EAA is a Directive rather than a directly applicable regulation, each EU member state implements it through its own national law, meaning enforcement mechanisms, penalties, and specific procedural requirements vary by country.
For services and products already on the market before June 28, 2025, the EAA provides a transitional period extending to June 28, 2030, meaning organizations do not need to retroactively remediate preexisting compliant services. However, new services and newly published documents must now meet the requirements. Additionally, prerecorded office file formats (including PDFs) published before June 28, 2025, are specifically excepted under the Directive.
There is one thing worth resolving before remediation starts. Both WCAG 2.1 AA (the current legal standard under ADA Title II) and PDF/UA may apply depending on your framework and document type, and they have meaningfully different scopes. WCAG 2.2 is the most current published version of WCAG, but it is not yet mandated under the DOJ rule. Getting that wrong means redoing work. The difference between PDF/UA and WCAG is worth reading before you start. Running an accessibility check against the wrong standard wastes time you don't have when deadlines are active.
If you don't yet know how large your PDF problem is, that's the right first question. A PDF accessibility checker, such as Siteimprove.ai, can audit an existing PDF library to surface the scope and severity of issues, serving as an accessibility tool that tells you where you stand before remediation begins.
Where to go from here
PDF accessibility is a governance problem that shows up dressed as a formatting problem. This is why so many organizations keep patching individual files while the backlog grows. The users locked out by inaccessible documents aren't edge cases. The compliance deadlines aren't distant. And the scale of the problem in any organization that's been publishing PDFs for years is rarely what anyone expects when they first look.
Even for documents that qualify for the preexisting-document exception, covered entities retain an existing obligation under the ADA to provide information in accessible formats upon request. Exception status reduces the burden of proactive remediation, not the duty to respond to accommodation requests.
Three things worth doing before anything else: Audit your existing library to understand what you're dealing with, prioritize by legal exposure and document traffic rather than recency, and put authoring standards in place so new PDFs stop adding to the problem.
The remediating-one-file-at-a-time approach doesn't scale. A systematic look at scope comes first, and knowing where to start is half the work.
This content is for informational purposes only and does not constitute legal advice. WCAG is a technical standard; Legal obligations vary by jurisdiction, entity type, and sector. Legal obligations under ADA Title II, Section 508, and the European Accessibility Act vary by entity type, jurisdiction, and context. Compliance deadlines and rule provisions are subject to change. Consult qualified counsel for legal guidance on your specific compliance obligations.