PDF Accessibility Guide: Make Your PDFs Readable

PDF accessibility means making a PDF that everyone can read and navigate, including people who are blind or have low vision and rely on a screen reader. You get there by tagging the document's structure, adding real headings and image alt text, setting a logical reading order, and making sure the text is selectable rather than a picture of a page. It matters more than ever, because the gaps are huge. According to Accessibility.build, around 60% of PDF forms have accessibility issues and roughly 60% of PDFs lack a proper document title. This guide walks through what accessible means, the standards, and how to fix your files.

Advertisement

What is PDF accessibility?

PDF accessibility is about structure the eye can't see. When you look at a PDF, you understand it visually: this big line is a heading, that block is a paragraph, those cells form a table. A screen reader can't infer any of that from the way it looks. It needs the document to spell out, in code, what each piece of content actually is.

An accessible PDF carries that hidden structure, called tags, so assistive technology can announce the content correctly and in the right order. An inaccessible PDF is often just a wall of text or an image with no structure at all, which a screen reader either skips or reads as gibberish. The difference is invisible on screen but total for someone who can't see it.

Why does PDF accessibility matter?

First, because a lot of people need it. The World Health Organization estimates that at least 2.2 billion people have a near or distance vision impairment (WHO). When your PDF is a flat scan or an untagged mess, you're shutting a large group out of your content entirely.

Second, it's increasingly the law. In the US, ADA Title II now points to WCAG 2.1 AA for public entities, with compliance deadlines rolling out from 2026 onward, as explained in RatedWithAI's 2026 PDF accessibility guide. Europe's accessibility rules push the same way. So an accessible PDF isn't just kind, it's fast becoming a requirement for government, education, and business documents alike.

What makes a PDF accessible?

A handful of ingredients turn a plain PDF into an accessible one. The single most important is tagging, but they all work together.

• Tags. An invisible layer that labels each part as a heading, paragraph, list, or table. Tags are the PDF version of HTML elements.
• Real headings. Proper heading levels (H1, H2, H3) so users can jump around instead of reading top to bottom.
• Alt text. A short text description on every meaningful image, so a screen reader can explain what it shows.
• Reading order. A set order so content is announced logically, not in the random order objects were placed.
• Selectable text. Real text, not a scanned picture, so it can be read, searched, and resized.
• Title and language. A document title and a set language so assistive tech identifies and pronounces the file correctly.
• Marked-up tables. Header rows and cells defined so data tables make sense read aloud.

Get tagging and reading order right and you've done most of the work. Accessibility.build notes that about 50% of tagged PDFs still have broken navigation from incorrect heading levels, so the details really do matter.

What are the WCAG and PDF/UA standards?

Two standards govern accessible PDFs, and they do different jobs. As the University at Buffalo explains it, WCAG 2.1 AA makes sure the content inside the PDF meets accessibility requirements, while PDF/UA makes sure the file format itself is properly engineered for assistive technologies.

Put simply, WCAG is the what and PDF/UA is the how. WCAG (Web Content Accessibility Guidelines) sets the goals: enough contrast, meaningful alt text, logical structure. PDF/UA (ISO 14289) is the technical rulebook for how a PDF must be built to be read by assistive tech. You aim for both. Hit WCAG 2.1 AA for the content and PDF/UA for the file structure, and your document is genuinely accessible rather than just close. If your content lives in Word first, structure it well there, since a clean source makes an accessible export far easier.

How do you make a PDF accessible?

Here's the practical order of work, whether you're fixing an old file or making a new one.

1. Start with structure in the source. Use real headings, lists, and table styles in Word or your design tool before exporting. Good structure in equals good tags out.
2. Make sure the text is real. If you're working from a scan, run OCR first so there's actual text to tag. Our PDF to text guide covers pulling selectable text out of a document.
3. Add or fix tags. Use a PDF editor to tag the document, or check the tags that carried over from your export.
4. Write alt text. Add a short, useful description to every image that carries meaning. Mark purely decorative images as decorative.
5. Set the reading order. Confirm the content is announced in the order a person would actually read it.
6. Add a title and language. Set the document title and language in the file properties.

If you need to make edits to text or images along the way, our guide on how to edit a PDF free shows the browser-based options. And keep the file lean, since a bloated PDF is slower for everyone, including assistive tech.

How do you check if a PDF is accessible?

Don't guess, test. An accessibility checker scans your file and flags exactly what's missing: untagged content, images with no alt text, no document title, or a broken reading order. Adobe Acrobat has a built-in checker, and the free PAC tool (PDF Accessibility Checker) tests specifically against PDF/UA.

Automated checks catch the mechanical problems, but they can't judge whether your alt text is actually useful or your reading order truly makes sense. So finish with a human pass: open the file in a screen reader and listen. If it reads clearly, in order, and describes the images, you're there. If it jumps around or goes silent on a chart, you've found your next fix.

What else do people ask about accessible PDFs?

What makes a PDF accessible?

An accessible PDF is tagged, so assistive technology can read its structure in the right order. It has real headings, alt text on images, a set reading order, marked-up tables, a document title and language, and selectable text rather than a flat scan. Tagging is the single most important factor.

What is a tagged PDF?

A tagged PDF has an invisible layer of tags that label each part of the document, like headings, paragraphs, lists, and tables. Tags are the PDF equivalent of HTML elements. They tell a screen reader what each piece of content is and what order to read it in, which is what makes the file usable without sight.

What is the difference between WCAG and PDF/UA?

WCAG is a content guideline covering what a document communicates to users with disabilities. PDF/UA is a structural standard covering how the PDF file itself is built for assistive technology. WCAG tells you the goals, PDF/UA tells you how to construct the file. Meeting both gives you a genuinely accessible PDF.

Are scanned PDFs accessible?

No. A scanned PDF is just an image of a page, so a screen reader sees nothing to read. To make it accessible you first run OCR to turn the image into real, selectable text, then add tags, headings, and alt text. A flat scan with no text layer is the least accessible kind of PDF.

How do you check if a PDF is accessible?

Run an accessibility checker, which flags missing tags, absent alt text, no document title, and reading-order problems. Adobe Acrobat has a built-in checker, and free tools like PAC (PDF Accessibility Checker) test against PDF/UA. Also try reading the file with a screen reader to hear how it actually sounds.

Sources: Accessibility.build, "How to Make PDFs Accessible" (accessibility.build). RatedWithAI, "PDF Accessibility: ADA Compliance Guide 2026" (ratedwithai.com). University at Buffalo, "WCAG 2.1 AA vs PDF/UA" (buffalo.edu). World Health Organization, "Blindness and vision impairment" (who.int). Last updated: 2026-07-19.