WCAG Guide

PDF Accessibility: How to Make PDFs WCAG Compliant

May 22, 20267 min read

WCAG and the ADA apply to document content, not just HTML pages. A scanned, untagged PDF is invisible to a screen reader — and PDFs (statements, guides, forms) are often the most important documents on a site. Here is how to make them conformant.

Anatomy of an accessible (tagged) PDF A document page with five tagged parts: 1 document title and language set in metadata, 2 heading tags H1 to H3 in logical order, 3 alt text on images with decorative images marked as artifacts, 4 table header cells that associate data with headers, and 5 a tag tree matching the logical reading order, which is the single most important fix. ACCESSIBLE PDF — TAGGED STRUCTURE 1 2 3 4 5 1Document title + languageSet in the file metadata 2Heading tags H1–H3Real headings, in logical order 3Alt text on imagesDecorative images = artifacts 4Table header cells (TH)Associate each value with its header 5Tag tree = reading orderThe single most important fix
An untagged PDF has none of this structure — a screen reader sees a flat blob.

Why PDFs are an accessibility blind spot

Teams audit their web pages and forget the PDFs linked from them. But a fee schedule, a benefits guide, or an application form in PDF is subject to the same WCAG criteria. An untagged PDF fails WCAG 1.3.1 (Info and Relationships), 1.1.1 (Non-text Content), and more.

The checklist

Tags and reading order

The PDF must have a tag tree that reflects the logical reading order. This is the single most important fix — it is what lets a screen reader navigate headings, paragraphs, and lists.

Document structure

Use real heading tags (H1, H2, H3) in order, real lists, and real paragraphs — not just visually styled text.

Alt text on images

Every informative image needs alternative text; decorative images are marked as artifacts so they are skipped.

Tables

Data tables need header cells defined so screen readers can associate each value with its row and column.

Document language and title

Set the document language (so the screen reader uses the right pronunciation) and a descriptive document title in the metadata.

Forms

PDF form fields need labels (tooltips), a logical tab order, and accessible instructions.

Color and contrast

Same thresholds as the web: 4.5:1 for normal text. Never use color alone to convey meaning.

How to check a PDF

Adobe Acrobat Pro has a built-in Accessibility Checker (Prepare for accessibility). The free PAC (PDF Accessibility Checker) tests against PDF/UA and WCAG. Always finish with a manual screen-reader pass — tags can be present but illogical.

The better long-term fix

Where you can, publish content as HTML instead of PDF. HTML is accessible by default when authored correctly, reflows on mobile, and is far easier to keep conformant than a binary document.

How AccessProof helps

AccessProof audits the HTML pages of your site and flags where PDF downloads are linked, so you can route those documents into a PDF remediation workflow. For the web layer itself, a free scan shows your current WCAG status in under a minute.

Want this checked on your site automatically?

AccessProof scans your site against WCAG 2.2 every day, scores it, and tells you exactly what to fix. Free plan available.