Accessible PDF documents: what they are and how to check one
What makes a PDF accessible, how an accessible PDF differs from a regular one, and quick ways to tell whether any PDF is accessible.
Last updated
An accessible PDF is one that people can read and use whether they see the page, hear it through a screen reader, read it on a braille display, enlarge it, or move through it with a keyboard. In practice, that means the PDF has real (selectable) text, tags that mark headings, lists, tables and images, a logical reading order, alt text for meaningful images, labeled form fields, a title and a language, and readable color contrast. PDF is not accessible or inaccessible by nature. The same format can be either, depending on how the file was made.
What makes a PDF accessible
| Feature | What it means | Who it helps most |
|---|---|---|
| Real text | Text a computer can read, not a picture of a page | Screen reader users, people who enlarge or reflow text, anyone searching |
| Tags | Hidden labels that say what each part is: heading, paragraph, list, table, image | Screen reader and braille display users |
| Logical reading order | The tags run in the order people should read, including across columns | Screen reader users, people using reflow or read-aloud |
| Headings and bookmarks | A real outline people can jump around | Screen reader and keyboard users, people with cognitive disabilities |
| Alt text and artifacts | Descriptions for meaningful images; decoration marked so it's skipped | People who are blind or have low vision |
| Table headers | Header cells linked to their data cells | Screen reader users |
| Labeled form fields | Each field has a name and a logical tab order | Keyboard, screen reader and voice control users |
| Title and language | The title is announced; the text is pronounced correctly | Screen reader users |
| Color and contrast | Text stands out from its background, and color isn't the only signal | People with low vision or color blindness |
| Descriptive links | Link text says where the link goes | Screen reader users scanning a list of links |
| Embedded fonts and readable characters | Text displays and reads the same on every device | Everyone, especially screen reader users |
| Open security settings | Encryption doesn't block assistive technology | Screen reader users |
Most of these map directly to WCAG 2.1 success criteria and to PDF/UA, the ISO standard for accessible PDFs. Our WCAG vs. PDF/UA guide explains how the two fit together.
Accessible PDF vs. a regular PDF
An accessible PDF and a regular PDF can look identical on screen. The difference is in what's underneath, and you notice it when you use a screen reader or try to reflow the text.
| Regular (untagged) PDF | Accessible PDF | |
|---|---|---|
| Headings | Read as ordinary text; no way to jump between sections | Announced as headings; people can jump from one to the next |
| Images | Skipped, or announced as an unlabeled graphic | Alt text is read; decoration is skipped |
| Tables | Numbers read as a long run, with no column names | Each cell is read with its header |
| Reading order | Follows however the file was drawn, so columns can get mixed up | Follows the intended order |
| Forms | Fields have no names, or can't be reached by keyboard | Each field has a label and a sensible tab order |
| Links | May not be announced as links | Announced as links, with a description |
| Language | May be read with the wrong voice or accent | Read with the right voice |
Exactly what people hear depends on their screen reader and PDF reader, but the pattern is the same: without structure, assistive technology has to guess, and it often guesses wrong.
Are PDFs accessible?
They can be. Tagged PDF has been part of the PDF format since version 1.4 in 2001, and an ISO standard, PDF/UA (ISO 14289), defines what an accessible PDF must contain. Acrobat, Word, PowerPoint and InDesign can all produce tagged PDFs.
Whether a particular PDF is accessible depends on how it was made. Common reasons a PDF isn't:
- It's a scan. The pages are pictures, so there's no text to read. See scanned PDFs and OCR.
- It was printed to PDF. "Print to PDF" drops the structure, even when the source document was accessible.
- It was made for print. Design files exported for a print shop usually have no tags.
- It was tagged automatically and never checked. Automatic tagging gets you started, but it often mislabels headings, tables and images.
PDF also has limits. Pages have a fixed layout, so on a phone people often have to zoom and scroll sideways, and reflow support depends on the PDF reader. For information people read on the web, such as notices, news and simple forms, a web page is often easier for everyone. PDF suits documents meant to be printed, signed or kept as a record.
Common myths about accessible PDFs
- "It passes Acrobat's checker, so it's accessible." Acrobat's checker confirms that structure exists, and it always leaves the reading order and color contrast for a person to check. It can't tell whether alt text or headings are right.
- "PDF/A means accessible." PDF/A is a standard for long-term archiving. Some PDF/A levels require tags, but none of them makes a file accessible on its own.
- "Accessible PDFs look plain." Accessibility lives mostly in the hidden structure. A well-designed document can keep its layout, images and branding, as long as images are described and text has enough contrast.
- "Adding tags is the whole job." Tags are the foundation. They also have to be in the right order, with the right types, and the content they describe has to make sense to people who can't see the page.
How to tell if a PDF is accessible
- Try to select the text. Click and drag across a sentence. If nothing highlights, the page is an image and needs OCR before anything else.
- See whether it's tagged. In Adobe Acrobat or the free Acrobat Reader, open File > Properties and look at the Description tab. It shows "Tagged PDF: Yes" or "No". "Yes" means tags exist, not that they're right.
- Run an automated check. Use our free checker, Acrobat Pro's Accessibility Checker, or PAC, a free checker for Windows. These test everything a machine can verify.
- Do the human checks. Software can't fully judge whether the reading order makes sense, whether alt text is meaningful, whether color carries meaning on its own, or whether link text is clear. A person needs to look.
- Listen to it. Try a screen reader such as NVDA (free for Windows) or VoiceOver (built into Macs and iPhones), or PAC's screen reader preview. Ten minutes of listening teaches you a lot.
The free Acrobat Reader can show whether a file is tagged, but the full Accessibility Checker and the tag editing tools are only in Acrobat Pro.
Who needs accessible PDFs
- State and local governments, public school districts and public colleges must make web content, including PDFs and other documents they post, meet WCAG 2.1 Level AA under the ADA Title II web rule.
- Healthcare providers that receive HHS funding must meet WCAG 2.1 AA under the HHS Section 504 rule.
- Federal agencies follow Section 508, which uses WCAG 2.0 Level AA.
- Private businesses aren't covered by a technical regulation, but WCAG is the yardstick most often used in complaints and lawsuits.
| Who | Rule | Compliance date |
|---|---|---|
| State governments, and local governments serving 50,000 people or more (including their public schools and colleges) | ADA Title II | |
| Local governments serving fewer than 50,000 people, and all special districts | ADA Title II | |
| Healthcare providers that receive HHS funding and have 15 or more employees | Section 504 (HHS rule) | May 2027 |
| Healthcare providers that receive HHS funding and have fewer than 15 employees | Section 504 (HHS rule) | May 2028 |
Our ADA Title II guide covers who's included, what counts as web content, and how to plan. Older documents may fall under an exception; see Title II exceptions explained.
How to make a PDF accessible
The short version: fix the source file first (headings, lists, table headers, alt text, a title and a language), export a tagged PDF, check it, fix what the export missed, and re-check. Our step-by-step guide on how to make a PDF accessible walks through each part in Word, InDesign and Acrobat. If you want to understand what tags are first, start with what is a tagged PDF.
Fix it automatically
Upload a PDF, Word or PowerPoint file to Includoc and you'll see, in plain English, what passes, what fails and what needs a person to review, mapped to WCAG 2.1 AA and PDF/UA. If you choose to fix it, we tag the file, fix the reading order, headings, tables, links, title, language and bookmarks, and run OCR on scanned pages. Our AI drafts alt text and other judgment calls, and you approve them on a review screen before you download the fixed file and a conformance report.
Upload your PDF to fix this automatically
Free check in seconds. Files are deleted within 24 hours.
Standards
| Standard or tool | Reference |
|---|---|
| WCAG 2.1 | |
| PDF/UA-1 (ISO 14289-1) | Clause 7.1 |
| Acrobat rule | Tagged PDF |
| Standard or tool | Reference |
|---|---|
| WCAG 2.1 | |
| PDF/UA-1 (ISO 14289-1) | Clause 7.1 |
| Matterhorn Protocol | Checkpoint 08-002 |
| Acrobat rule | Image-only PDF |
| Standard or tool | Reference |
|---|---|
| WCAG 2.1 | |
| PDF/UA-1 (ISO 14289-1) | Clause 7.2 |
| Matterhorn Protocol | Checkpoint 11-001, Checkpoint 11-002, Checkpoint 11-003, Checkpoint 11-004, Checkpoint 11-005, Checkpoint 11-006 |
| Acrobat rule | Primary language |
Sources
- W3C: Web Content Accessibility Guidelines (WCAG) 2.1 (opens another website)
- W3C: PDF Techniques for WCAG (opens another website)
- ISO: ISO 14289-1:2014, PDF/UA-1 (opens another website)
- ADA.gov: Fact sheet on the ADA Title II web and mobile accessibility rule (opens another website)
- Federal Register, April 20, 2026: Extension of compliance dates (opens another website)
- Adobe: Create and verify PDF accessibility (Acrobat Pro) (opens another website)
Frequently asked questions
Related
- How to make a PDF accessible: a step-by-step guide
Make a PDF accessible from start to finish: fix the source file, export with tags, then check and fix tags, reading order, alt text, tables and forms.
- What is a tagged PDF? Tags, the tag tree and how to check them
A tagged PDF has hidden structure that tells screen readers what each part is. Learn the common tags, artifacts, role maps and how to view and fix tags.
- WCAG vs. PDF/UA: which standard do your PDFs need?
WCAG 2.1 AA is what the ADA Title II rule requires; PDF/UA is the ISO standard for accessible PDF files. How they differ, overlap and map to each other.
- Scanned PDFs and OCR: how to make an image-only PDF accessible
Image-only PDFs have no text for screen readers. Run OCR in Acrobat or OCRmyPDF, check the accuracy, tag the result, and know when to retype instead.
- Image-only PDF – Failed
Acrobat’s “Image-only PDF – Failed” means pages are pictures of text, usually scans. Why OCR alone isn’t enough, and how to make a scanned PDF accessible.