What is PDF Accessibility?
A PDF is accessible when every person — including people who use screen readers, people with low vision, people with motor impairments, and people with cognitive disabilities — can read, understand, and navigate it fully.
Think of it like a building. A non-accessible building might have stairs at the entrance. A building with a ramp alongside those stairs is accessible — it works for everyone, not just people who can walk.
An accessible PDF works the same way. It doesn't look different to most people. But underneath the visual layer, it has a carefully built structure that allows assistive technology — like screen readers — to interpret and read it out loud in a way that makes sense.
people worldwide live with some form of disability
of top websites fail basic accessibility checks
people have a vision impairment of some kind
Most PDFs created by exporting from Word, InDesign, or Canva are not accessible by default. Accessibility requires deliberate action during the creation process — it doesn't happen automatically.
Who benefits from accessible PDFs?
The word "disability" can make some people think this is a niche issue. It isn't. Accessible design benefits a much wider group of people than most assume.
People who are blind
Use screen readers that read out every element. A poorly tagged PDF becomes an unintelligible jumble of random text fragments.
Low-vision users
May zoom in 200–400%. Need proper reflow and scalable text so the document doesn't break apart at large sizes.
People with motor disabilities
Navigate with keyboard only or switch devices. Need logical tab order and accessible forms they can actually fill in.
Cognitive differences
Clear structure, plain language, and logical reading order help people with dyslexia, ADHD, or cognitive disabilities comprehend content.
Older adults
Age-related vision and hearing changes affect over 40% of people over 60. Accessible design meets their needs too.
Mobile users
Reflowable, well-structured PDFs work far better on small screens. Accessibility helps everyone on any device.
Why it's required by law
PDF accessibility is not just a nice-to-have. In many countries, it is a legal requirement — especially for public sector organisations, businesses above a certain size, and any company serving the public.
Failing to provide accessible documents can result in fines, lawsuits, loss of public contracts, and significant reputational damage. The legal trend is clear: requirements are getting stricter, not looser.
The European Accessibility Act (EAA)
From 28 June 2025, the European Accessibility Act applies to a wide range of private companies doing business in the EU. This includes digital documents — including PDFs — shared with customers or the public. This is a major shift: previously, these rules mainly applied to the public sector.
EN 301 549
The European standard EN 301 549 defines the technical requirements for accessible ICT products and services in Europe. It references WCAG 2.1 and PDF/UA as the relevant standards for documents. Public procurement contracts in the EU must typically comply with this standard.
In the USA: ADA & Section 508
The Americans with Disabilities Act (ADA) has been applied to digital documents through numerous lawsuits. Section 508 of the Rehabilitation Act requires federal agencies and their contractors to ensure ICT products — including PDFs — are accessible. Courts have consistently ruled that inaccessible PDFs violate ADA requirements.
The number of accessibility-related lawsuits in the USA has grown by over 300% in the past five years. Many target company documents — including PDFs — not just websites.
How accessible PDFs actually work
Here's a mental model that helps: imagine every PDF as having two layers.
The visual layer is what you see on screen. Beautiful typography, images, columns, colour — everything that makes a document look good.
The logical layer is invisible. It's a set of behind-the-scenes instructions that tell software: "This text is a heading. This image shows a bar chart. This table has a header row. Read this paragraph before that one."
Screen readers and other assistive technology ignore the visual layer entirely. They rely only on the logical layer to understand the document. If the logical layer is absent, wrong, or incomplete — the user gets garbage.
The four pillars of accessible PDFs
Tags (structure)
PDF tags define what every element is: heading, paragraph, list, table, figure. Without tags, the document is a flat, unstructured image of text to assistive technology.
Reading order
The order in which content is read out loud must match the intended logical order — not the visual layout. Multi-column layouts and complex designs often get this wrong automatically.
Alternative text for images
Every meaningful image must have a text description (alt text). Decorative images must be explicitly marked as such so they're skipped by screen readers.
Metadata and document properties
Title, language, and other metadata help screen readers identify what document they're in and read it in the correct language with the right pronunciation rules.
Tags: the invisible skeleton of your PDF
Tags are the most important accessibility feature in a PDF. They are hidden codes attached to every element in the document that describe what that element is — not what it looks like, but what role it plays.
Think of tags like HTML elements on a website: <h1> for a main heading, <p> for a paragraph, <ul> for a bullet list. PDF tags work the same way.
Common PDF tags you need to know
| Tag | Means | Why it matters |
|---|---|---|
<H1>–<H6> |
Headings | Screen reader users navigate by headings to jump around the document — like a table of contents |
<P> |
Paragraph | Normal body text. Without this tag, blocks of text may be read as a single line or ignored |
<L> <LI> |
List / List item | Screen readers announce "list of 5 items" — giving context before reading each item |
<Table> <TR> <TH> <TD> |
Tables | Without table tags, tabular data is read as a confusing stream of unrelated cells |
<Figure> |
Image / graphic | Marks where images are, so alt text can be linked to them |
<Artifact> |
Decorative content | Tells screen readers to skip this element — used for page numbers, decorative lines, etc. |
<Link> |
Hyperlink | Makes links recognisable and keyboard-operable |
Images and alt text
Every image in a PDF falls into one of two categories: meaningful or decorative. The handling is completely different for each.
Meaningful images
These images convey information that isn't available anywhere else in the text. A chart, a photograph of a product, a diagram of a process, a signature — these are meaningful. They need alternative text (alt text): a written description that communicates the same information the image provides visually.
Decorative images
These are visual elements that don't add information — ornamental lines, background shapes, purely aesthetic illustrations. These should be marked as Artifact in the PDF tag structure, which tells screen readers to skip them entirely. This avoids cluttering the listening experience with meaningless descriptions.
Charts and infographics are the most commonly inaccessible images in PDFs. A complex chart with no alt text is completely invisible to a screen reader user. Every data point, trend, and key insight must be described in text — either as alt text or as a caption below the image.
Complex images: go further
For complex diagrams, infographics, or charts, alt text alone may not be enough. Consider:
- Providing a full text description of the chart's data in the document body
- Adding a data table below the chart with the actual numbers
- Using a "long description" linked from the figure (supported in PDF/UA)
Reading order: the hidden disaster in most PDFs
This is the issue that surprises most people. A PDF can look perfectly logical on screen — columns flowing naturally left to right, captions under images, headings before body text. But the actual reading order stored in the file can be completely different.
Screen readers follow the reading order defined in the file structure — not the visual layout. A two-column PDF might read all of column 1, then all of column 2... or it might jump randomly between both. A caption might be read before the image it refers to. A sidebar might interrupt the middle of a sentence.
Why does this happen?
Most design applications place elements on the page in the order they were created — not the order they should be read. A graphic designer who adds a pull quote after the main text will place it after the main text in the file structure, even if visually it appears in the middle of a paragraph.
How to fix it
Reading order must be set manually for complex layouts. In Adobe Acrobat Pro, you can use the Reading Order tool or the Tags panel to reorder elements. In InDesign, you control reading order through the Articles panel before export.
WCAG: the global accessibility rulebook
The Web Content Accessibility Guidelines (WCAG) are the internationally recognised set of rules for digital accessibility. Although written for websites, WCAG applies to PDF documents too — and is referenced in virtually every national accessibility law worldwide.
WCAG is built on four principles, often remembered as POUR:
Perceivable
Information must be presentable in ways users can perceive — including through non-visual means.
Operable
All functionality must be operable — for example, navigable via keyboard, not just a mouse.
Understandable
Content and operation must be understandable — clear language, predictable structure.
Robust
Content must be interpreted reliably by a wide variety of assistive technologies, now and in the future.
The three levels of conformance
WCAG criteria are organised into three levels. Level AA is the standard required by most laws.
| Level | What it means | Example for PDFs |
|---|---|---|
| A | Minimum. Must pass. Without this, some users cannot access the content at all. | All images have alt text; document has a title; language is set |
| AA | Standard. Required by most legislation. Removes significant barriers. | Colour contrast ratio at least 4.5:1; text can be resized 200% without loss of content |
| AAA | Enhanced. Not always possible for all content. Going above and beyond. | Contrast ratio at least 7:1; sign language interpretation provided |
Colour contrast: the most commonly failed criterion
Text must have sufficient contrast against its background. This is one of the most frequently failed accessibility criteria — and it's one of the easiest to check.
✗ Fails AA (ratio: ~1.6:1)
✓ Passes AAA (ratio: 15.5:1)
WCAG 3.0 is currently under development and will introduce a new contrast model called APCA (Advanced Perceptual Contrast Algorithm), which better reflects how human eyes perceive contrast than the current formula.
Testing tools — how to check your PDFs
You can't rely on visual inspection to verify PDF accessibility. You need dedicated tools that inspect the underlying structure and report problems automatically.
Automated checking tools
-
Adobe Acrobat Accessibility Checker Built into Acrobat Pro (and available in free Acrobat Reader to a lesser extent). Runs an automated check against PDF/UA and WCAG criteria. A good first pass — but not exhaustive. Adobe Accessibility Guide ↗
-
PAC 2024 (PDF Accessibility Checker) Free tool for Windows. One of the most thorough automated PDF accessibility checkers available. Checks against PDF/UA and WCAG. Highly recommended for anyone creating accessible PDFs professionally. Download PAC 2024 ↗
-
axe DevTools for PDFs Professional accessibility testing platform with PDF support. Used widely by enterprises and accessibility consultants. axe DevTools ↗
-
CommonLook PDF (Formerly Commonlook) Enterprise-grade PDF accessibility testing and remediation tool. Widely used in government and large organisations. CommonLook ↗
Screen readers for manual testing
-
NVDA — NonVisual Desktop Access Free, open-source screen reader for Windows. The most commonly used screen reader in the world. Essential for testing how your PDFs actually sound to users. Download NVDA ↗
-
VoiceOver (Apple) Built into macOS, iOS, and iPadOS. No installation needed. Activate with Cmd+F5 on Mac. A great way to test PDFs on Apple devices. VoiceOver Guide ↗
-
Narrator (Windows) Built into Windows. Less feature-rich than NVDA or JAWS, but useful for a quick sanity check without installing anything. Narrator Guide ↗
The accessibility checklist — before you publish
Use this checklist before sharing any PDF. It covers the most critical requirements. A document that passes all of these is well on its way to genuine accessibility.
- The document has a descriptive title set in Document Properties (not just the filename).
- The document language is set in Document Properties. This ensures screen readers use the right voice and pronunciation.
- The PDF is tagged. All content elements — headings, paragraphs, lists, tables — have correct semantic tags.
- Heading levels are logical and nested correctly. H1 → H2 → H3, never jumping from H1 to H4.
- Reading order is logical and matches the intended reading sequence, especially in multi-column layouts.
- All meaningful images have alt text. Decorative images are marked as Artifacts.
- Tables have header rows tagged with <TH> and are not used for layout purposes.
- Colour contrast meets WCAG AA: at least 4.5:1 for normal text, 3:1 for large text (18pt+ or 14pt bold+).
- Colour is not the only means of conveying information. Symbols, labels, or patterns supplement colour cues.
- All links have descriptive text. Not "click here" — but "Download the 2024 Annual Report (PDF)".
- Forms are accessible. All form fields have labels, correct tab order, and error messages that don't rely on colour alone.
- The PDF passes PAC 2024 or Adobe Preflight with no critical errors.
- Manual screen reader test completed. The document was listened to in NVDA or VoiceOver and made sense throughout.
The PDF/UA standard requires a conformance claim in the document metadata. Without this claim, a PDF cannot be said to conform to PDF/UA — even if it passes all technical checks. Add the XMP metadata flag in Acrobat or during export from InDesign.
Essential resources and further reading
PDF accessibility is a deep field with an active community. Here are the most important resources to bookmark — all free, all authoritative.
Official standards and guidelines
-
WCAG 2.2 — W3C The full WCAG 2.2 specification. The authoritative global standard for digital accessibility. Dense, but the Understanding documents alongside it make it accessible. wcag 2.2 ↗
-
PDF/UA Overview — PDF Association The PDF Association is the custodian of PDF standards. Their resources on PDF/UA are the most authoritative and practical available. pdfa.org/pdf-ua ↗
-
Section 508 PDF Resources — GSA The US General Services Administration publishes detailed guidance on making PDFs accessible under Section 508. Practical and clear. section508.gov ↗
Practical guidance
-
WebAIM — Web Accessibility In Mind The best practical, human-readable guide to web and document accessibility on the internet. Their PDF Accessibility guide is essential reading. WebAIM PDF Guide ↗
-
Adobe Accessibility Resource Centre Adobe's own documentation on creating and verifying accessible PDFs in Acrobat and InDesign. Up-to-date and comprehensive. Adobe Accessibility ↗
-
WebAIM Million — Annual Accessibility Report Annual analysis of the top 1 million websites and documents for accessibility failures. Sobering and important data on the state of digital accessibility. WebAIM Million ↗
-
EU Web Accessibility Directive The full text and guidance on Directive (EU) 2016/2102 — the public sector accessibility directive. Includes monitoring requirements and complaint mechanisms. EU Digital Strategy ↗
Tools
-
PAC 2024 — PDF Accessibility Checker Free. Windows. The gold standard automated PDF accessibility checker. Tests against PDF/UA and WCAG. Use it on every PDF before publishing. pac.pdf-accessibility.org ↗
-
WebAIM Contrast Checker Free online tool. Enter two colours and instantly see whether they pass WCAG AA or AAA contrast requirements. Bookmark this. Contrast Checker ↗