Most WordPress site owners spend time making their pages and forms accessible — and then upload a pile of inaccessible PDF brochures, menus, reports, and guides without a second thought. In 2026, that oversight has a price tag. The ADA’s updated web accessibility rules now explicitly cover electronic files published on your website, including PDFs. If your downloads aren’t accessible, your site isn’t compliant — regardless of how clean your HTML is.
Why PDFs Are a Separate Problem
A well-coded web page and an accessible PDF are two entirely different things. HTML pages are structured by nature — headings, paragraphs, and lists create a readable hierarchy that assistive technologies can navigate. PDFs, on the other hand, started life as print-first documents. When you export a Word doc or InDesign file to PDF, you get a visual representation of a page, not a structured document.
Screen readers can’t infer meaning from visual layout. Without explicit tags telling the PDF what’s a heading, what’s a paragraph, what’s a table header, and what’s decorative, a screen reader reads the content in whatever order the underlying file happens to store it — which can be completely different from what you see on screen. A two-column layout often gets read left-to-right across both columns simultaneously, turning a clear document into an incomprehensible stream of mixed text.
What the 2026 ADA Rules Say About PDFs
The updated ADA Title II rules — which apply to government agencies and public entities — are explicit: electronic files of any kind published to a website must meet accessibility standards. PDFs are not exempt. The same WCAG 2.1 AA requirements that apply to your web pages apply to your downloadable documents.
For healthcare organizations covered by HHS Section 504, a similar requirement exists, with compliance deadlines now extended to May 2027 for larger recipients and May 2028 for smaller ones. Private businesses under ADA Title III aren’t yet subject to a federal PDF-specific rule with firm deadlines, but courts have consistently treated inaccessible PDFs as ADA violations — and the litigation data backs that up. With over 5,000 digital accessibility lawsuits filed in 2025, plaintiff attorneys are looking for every angle, and PDF-heavy sites are easy targets.
The Most Common PDF Accessibility Failures
Most inaccessible PDFs share the same handful of problems. Understanding them is the first step toward fixing them.
No Document Tags
An “untagged” PDF has no structural information at all. Screen readers see it as a flat image of text — or sometimes just an actual image, with no text to read at all. Tagging a PDF adds the semantic layer that makes it navigable: headings, paragraphs, lists, tables, figures, and reading order.
Missing or Vague Alt Text on Images
Charts, graphs, photos, and logos embedded in PDFs need alt text just like they do on the web. A chart labeled “Figure 1” tells a screen reader user nothing about what the chart shows. Decorative images need to be explicitly marked as artifacts so they’re skipped.
Poor Color Contrast
WCAG 2.1 AA requires a 4.5:1 contrast ratio for normal text and 3:1 for large text — in PDFs as well as on web pages. Light gray text on white backgrounds, colored text on colored backgrounds, and watermarks overlapping body text are all common failures in designed documents.
Scanned Documents Without OCR
A scanned PDF is essentially a photo. Without optical character recognition (OCR) applied and then reviewed for accuracy, there is no text for a screen reader to read. These files are completely inaccessible to users who rely on assistive technology.
Forms Without Proper Field Labels
PDF forms present the same problems as inaccessible HTML forms, but they’re harder to fix. Form fields need programmatic labels, proper tab order, and clear instructions — none of which happen automatically when you export a designed form to PDF.
How to Audit Your WordPress Site’s PDFs
Start by inventorying every PDF linked on your site. Use your browser’s developer tools, a site crawler, or the WordPress Media Library to find all uploaded PDF files. Then prioritize: which ones are most frequently downloaded, most legally sensitive (application forms, contracts, policies), or most likely to be needed by users with disabilities?
For each priority document, run it through a PDF accessibility checker. Adobe Acrobat Pro has a built-in accessibility checker (Tools → Accessibility → Full Check). Free alternatives include PAC 2024 (PDF Accessibility Checker) and the axe DevTools browser extension, which can analyze some PDF content. These tools catch structural issues — missing tags, missing alt text, reading order problems — but they can’t catch everything. A tool that says “no errors” doesn’t mean the document is actually usable; manual review is still necessary for complex documents.
Key things to check manually:
- Can you tab through the document in a logical order?
- Do headings appear as headings in the document structure panel?
- Does every meaningful image have descriptive alt text?
- Are tables properly marked up with header cells?
- Does the document have a title set in the metadata?
- Is the document language declared?
Remediation vs. Replacement
Once you know which PDFs have problems, you have two options: remediate the existing files or replace them with something better.
Remediation means opening the PDF in Acrobat Pro (or a professional PDF remediation tool) and fixing the structure manually. This is labor-intensive for complex documents but often the only option if you don’t have access to the original source files. Professional PDF remediation services exist for large document libraries.
Replacement is often the better long-term strategy for content that changes frequently. If you’re publishing a monthly newsletter, an event schedule, or a restaurant menu as a PDF — consider whether that content would serve users better as an accessible HTML page instead. HTML pages are inherently more accessible, easier to update, better for SEO, and don’t require users to download anything. Not everything needs to be a PDF.
For documents that genuinely benefit from the PDF format — annual reports, formal application forms, technical specifications — invest in making the source files accessible before export. Properly structured Word documents and InDesign files produce significantly better PDFs than poorly structured ones. Turn on heading styles in Word. Add alt text to images before exporting. Use table header row options. These upstream fixes cost far less than remediating the output.
Take Action
Fixing inaccessible PDFs starts with knowing you have them. LEWCA’s WCAG scanner audits your WordPress site for code-level accessibility issues on your web pages — giving you a clear picture of where you stand before you tackle your document library. Pair that with your PDF audit and you’ll have a complete view of your site’s accessibility gaps. Compare LEWCA plans to see what fits your site, or download the free version and start scanning today.