Last updated: November 3, 2026
An accessible PDF is a PDF that people with disabilities can read, navigate and use with assistive technology such as screen readers, magnifiers and braille displays. It has real text, a tag tree that marks headings, lists, tables and images, a logical reading order, alt text, a set document language and a title.
Two PDFs can look the same on screen and still be very different underneath. A standard PDF often has no structure that software can follow, and a scanned PDF may hold no text at all, only a picture of a page. An accessible PDF carries a hidden structure layer, the tags, that tells a screen reader what each part of the page is and in which order to read it.
Standard PDF vs accessible PDF
The difference is mostly invisible to a sighted reader. For a screen reader user it decides whether the document works at all.
| Feature | Standard PDF | Accessible PDF |
|---|---|---|
| Structure | No tags, or tags created automatically and never checked. | A tag tree that marks headings, paragraphs, lists, tables and figures. |
| Text | May be an image of text (a scan) that a screen reader cannot read. | Real, selectable text, with OCR applied to any scanned pages. |
| Reading order | Columns, sidebars and footnotes can be read in the wrong order. | Content is read in the order the author intended. |
| Images | No alternative text, so the information in charts and photos is lost. | Alt text on meaningful images. Decorative images are marked as artifacts. |
| Tables | A grid of cells with no header information. | Header cells are tagged, so a screen reader can announce row and column for each value. |
| Forms | Fields with no labels, or fields that a keyboard cannot reach. | Labeled fields in a logical tab order. |
| Language and title | Not set. The file name shows in the title bar. | Document language and a real title are set in the metadata. |
In short, a standard PDF gives the visual layout. An accessible PDF gives the same content in a form that both people and software can understand.
What makes a PDF accessible: the requirements
An accessible PDF meets these requirements. Most of them come from WCAG and from the PDF/UA standard, which we explain below.
Real text. Every page contains text characters, not only an image of text. Scanned pages need OCR first, and the OCR result must be checked.
Tags. The file is a tagged PDF, and every piece of content is either tagged or marked as an artifact (page numbers, running headers, decoration). Our guide to what a tagged PDF is shows the common tags and how the tag tree works.
Correct tag types. Headings use H1 to H6 in a logical order, lists use list tags, and tables use table, row, header and data cell tags.
Logical reading order. The tag order matches the order in which a person would read the page, including multi-column layouts.
Alternative text. Charts, photos and diagrams that carry information have alt text that gives the same information.
Table headers. Header cells are tagged so that each data cell has context.
Accessible forms. Form fields have labels and tooltips, and keyboard users can reach them in a logical order.
Document language and title. The primary language is set, so a screen reader uses the correct pronunciation, and the title shows instead of the file name.
Bookmarks for long documents, so users can go directly to a section.
Readable visual design. Text has enough color contrast, and information is not given by color alone. These are the same rules as for web pages (WCAG 1.4.3 and 1.4.1).
No security setting that blocks assistive technology from reading the content.
Why accessible PDFs matter
The World Health Organization estimated in 2023 that 1.3 billion people, about 1 in 6, have a significant disability. Many of them use a screen reader, magnification, voice control or a keyboard instead of a mouse. If an invoice, a policy, a course reading or a job application exists only as an inaccessible PDF, these people cannot use it without help.
The legal requirements
Accessibility laws treat PDFs on a website or in a digital service as digital content, so the same rules apply to them as to web pages.
ADA Title II (United States). The Department of Justice rule requires state and local governments to meet WCAG 2.1 AA for web content and documents. Under the current compliance dates, larger public entities must comply by April 26, 2027, and smaller entities by April 26, 2028. Some older documents are exempt, but documents that people still need to use for current services are not.
ADA Title III (United States). Businesses open to the public have no technical standard in the regulation, but courts and settlements usually point to WCAG 2.1 AA, and inaccessible PDFs are a common part of web accessibility complaints.
Section 508 (United States). Federal agencies, and vendors that sell to them, must make electronic documents conform to the Revised 508 Standards, which use WCAG 2.0 AA.
European Accessibility Act (EU). Since June 28, 2025, many consumer products and services, such as banking, e-commerce and e-books, must be accessible. The harmonized standard EN 301 549 includes requirements for documents.
WCAG and PDF/UA: the two standards
WCAG (Web Content Accessibility Guidelines) is the W3C standard for all digital content. It sets the goals: text alternatives, structure, reading order, contrast, keyboard access. The laws above refer to WCAG, and W3C publishes PDF techniques that show how to meet WCAG success criteria in a PDF. See our overview of the WCAG success criteria.
PDF/UA (Universal Accessibility) is the ISO standard for accessible PDF files. It says how the file itself must be built: every piece of content tagged or marked as an artifact, correct tag semantics, the document title shown, the language set, and more. PDF/UA-1 was published as ISO 14289-1 in 2012. PDF/UA-2 (ISO 14289-2) was published in 2024 and is based on PDF 2.0. The PDF Association publishes the Matterhorn Protocol, which lists the failure conditions that make a file fail PDF/UA-1.
WCAG tells you what an accessible document must do. PDF/UA tells you how a PDF must be built to do it. A file can pass a PDF/UA check and still have bad alt text or a confusing reading order, so you need both.
How to tell if a PDF is accessible
Accessible and inaccessible PDFs usually look identical, so you have to check. Start with three quick tests.
Select the text. Press Ctrl+A (Cmd+A on a Mac) in the PDF. If the whole page is selected as one block, or nothing is selected, the page is an image and a screen reader cannot read it.
Look for tags. In Adobe Acrobat, open the Tags panel, or check Document Properties, where "Tagged PDF: Yes" or "No" shows. An untagged PDF is not accessible. A tagged PDF can still fail, because automatic tagging often gets reading order and tables wrong.
Run a checker. The Adobe Acrobat Pro Accessibility Checker and PAC (PDF Accessibility Checker, a free Windows tool from axes4) test the file against PDF/UA and WCAG rules. Our PAC guide shows how to read the results.
Automated checks find missing tags, a missing title or missing alt text. They cannot judge whether the alt text is correct or the reading order makes sense, so finish with a manual review. A short screen reader test (NVDA is free on Windows) shows quickly whether the document reads in a logical order.
How to create or fix an accessible PDF
The easiest way is to build accessibility into the source file. In Microsoft Word, Google Docs or Adobe InDesign, use real heading styles, built-in list tools, table header rows and alt text on images. Then export with a method that keeps the tags, such as Word's "Save as PDF" with document structure tags enabled. A "Print to PDF" export removes the tags.
For PDFs that already exist, you need remediation: you add or correct the tags, set the reading order, add alt text, tag tables and forms, set the language and title, and then check the result again. You can do this by hand in Acrobat Pro, which takes time for long documents. Our step-by-step guide on how to make a PDF accessible and ADA compliant covers each task.
WebAbility's PDF accessibility service fixes the PDF file itself. You upload a document and preview the fixed version for free. For standard PDFs, the result is a tagged PDF/UA file with a set reading order, and each document comes with a conformance report that records what was checked and fixed. Your original file stays unchanged.
Frequently asked questions
What does accessible PDF mean?
It means a PDF that people with disabilities can use as well as anyone else. In practice, the file has real text, tags, a logical reading order, alt text for images, tagged tables and forms, and a set language and title, so it works with screen readers and keyboard navigation.
What is the difference between a PDF and an accessible PDF?
Both use the same file format. A standard PDF stores only how the page looks. An accessible PDF also stores the structure of the content in tags, so assistive technology can read it in the right order and know what each element is.
Can screen readers read PDFs?
Yes, if the PDF has real text and tags. Screen readers such as JAWS and NVDA read tagged PDFs in Adobe Acrobat Reader. Browser PDF viewers also use the tags, but their support varies. A scanned PDF without OCR sounds empty, and an untagged PDF is often read in the wrong order.
Is a tagged PDF automatically an accessible PDF?
No. Tags are required, but they must also be correct. Automatic tagging often marks headings as paragraphs, reads columns in the wrong order or breaks tables. Alt text, table headers, form labels, the language and the title must also be in place.
Can a scanned document be an accessible PDF?
Yes, after work. OCR must first turn the image of the page into real text, and a person should check the OCR result. Then the document needs tags, a reading order and alt text, the same as any other PDF.
What is the difference between PDF/A and PDF/UA?
PDF/A (ISO 19005) is for long-term archiving: it makes sure a file opens and looks the same in the future. PDF/UA (ISO 14289) is for accessibility: it makes sure the file works with assistive technology. A file can meet both, and PDF/A-1a, 2a and 3a also require tags.
Do accessible PDFs need to meet WCAG?
If the PDF is on a website or part of a digital service covered by the ADA, Section 508 or the EAA, yes. Those laws use WCAG (2.0 AA or 2.1 AA, depending on the law) for documents as well as for web pages. PDF/UA is the recommended way to build the file so that it can meet those criteria.
