How to Make PDFs Accessible: Complete Accessibility Guide
· 6 min read
Why PDF Accessibility Matters
Over one billion people worldwide live with some form of disability. When you create a PDF that isn't accessible, you're potentially excluding 15% of the global population from accessing your content. Beyond the moral imperative, accessible PDFs are increasingly a legal requirement for businesses, government agencies, and educational institutions.
An accessible PDF can be read by screen readers used by visually impaired individuals, navigated by keyboard for those who can't use a mouse, and understood by people with cognitive disabilities through clear structure and organization. But accessibility benefits everyone—properly structured PDFs are easier to search, reflow on mobile devices, and process with automated tools.
The business case is equally compelling. Accessible documents reach a wider audience, demonstrate corporate responsibility, reduce legal risk, and often rank better in search engines because they have well-structured, semantically meaningful content. Creating accessible PDFs isn't just the right thing to do—it's smart business practice.
🛠️ Try it yourself
Key Elements of Accessible PDFs
Document Structure Tags
Tags are the foundation of PDF accessibility. They define the document's logical structure—headings, paragraphs, lists, tables, and images—allowing screen readers to present content in a meaningful order. Without tags, a screen reader encounters a flat stream of text with no structure, making navigation nearly impossible for visually impaired users.
Tags should reflect the document's hierarchy accurately. A main title gets an H1 tag, section headings get H2, subsections get H3, and so on. Paragraphs are tagged as P, list items as LI within L (list) tags, and table cells as TD within TR (table row) tags. This hierarchical structure enables users to jump between sections, skip content, and understand document organization.
Alternative Text for Images
Every meaningful image needs alternative text—a concise description that conveys the image's purpose and content. For a chart showing quarterly revenue, alt text might read "Bar chart showing Q1-Q4 2025 revenue: Q1 $2.1M, Q2 $2.4M, Q3 $2.8M, Q4 $3.2M." Decorative images that add no information should be marked as artifacts so screen readers skip them entirely.
Reading Order
The reading order defines the sequence in which a screen reader presents content. In a simple single-column document, reading order naturally follows top-to-bottom. But in complex layouts with sidebars, callout boxes, and multi-column text, the visual order may not match the logical reading order. Setting the correct reading order ensures content makes sense when read sequentially.
Color and Contrast
Information should never be conveyed by color alone. A form field highlighted in red to indicate an error also needs a text label or icon. Color contrast between text and background should meet WCAG requirements—4.5:1 for normal text and 3:1 for large text. This ensures readability for users with low vision or color blindness.
Font and Text Properties
Fonts must be embedded in the PDF so the text displays correctly on any device. Use actual text rather than images of text—this allows screen readers to read the content and users to adjust text size. If a document must use images of text (like logos), provide alternative text describing the text content.
Creating Accessible PDFs from Scratch
The easiest way to create accessible PDFs is to start with an accessible source document. Whether you're using Word, PowerPoint, InDesign, or Google Docs, building accessibility into the source saves significant remediation time later.
In Microsoft Word: Use built-in heading styles (Heading 1, Heading 2, etc.) rather than manually formatting text to look like headings. Add alt text to all images through right-click > Edit Alt Text. Use Word's table tools to create data tables with header rows. Run the Accessibility Checker (Review > Check Accessibility) before converting to PDF. When saving as PDF, ensure "Document structure tags for accessibility" is checked.
In Google Docs: Apply heading styles from the Format menu. Add alt text to images through right-click > Alt text. Use the built-in table tool for data tables. While Google Docs' PDF export has limited tag support, it handles basic structure well for simpler documents.
In Adobe InDesign: Set up paragraph styles that map to PDF tags. Add alt text through the Object Export Options panel. Use Articles panel to define reading order. Export using the PDF/UA preset for maximum accessibility compliance.
Making Existing PDFs Accessible
When you have PDFs without accessibility features—whether from scanned documents, legacy files, or tools that don't export accessible PDFs—remediation is necessary. This process adds the missing structural elements to make the document accessible.
Start by extracting the text content. Using a PDF to Text converter helps you verify that all text is selectable and correctly ordered. If the PDF is scanned (image-only), you'll need OCR to convert page images into actual text before any accessibility work can begin.
Next, use a PDF editor to add or fix structural tags. This involves identifying each content element and assigning the appropriate tag type. While time-consuming for complex documents, this process is essential for accessibility. Many PDF editors offer semi-automated tagging that can speed up the process significantly.
Add alternative text to every meaningful image. Review the reading order to ensure it follows the logical content flow. Set the document language in the properties so screen readers use the correct pronunciation rules. Add bookmarks for long documents to enable quick navigation.
Testing PDF Accessibility
Accessibility testing should combine automated checking with manual verification. Automated tools catch structural issues quickly—missing tags, images without alt text, unspecified language, and contrast problems. But they can't evaluate whether alt text accurately describes an image or whether the reading order makes semantic sense.
For manual testing, open the PDF with a screen reader. NVDA (free for Windows) and VoiceOver (built into macOS and iOS) are excellent choices. Listen to how the document reads aloud. Can you navigate between headings? Do tables make sense when read row by row? Are images described meaningfully? Does the reading order follow the logical flow of ideas?
Test keyboard navigation separately. Can every interactive element (links, form fields, buttons) be reached and activated using only the keyboard? Tab order should follow a logical sequence through the document's interactive elements.
Compliance Standards
WCAG 2.1. The Web Content Accessibility Guidelines apply to PDFs when they're served on the web. Level AA conformance is the most commonly required standard, covering text alternatives, adaptable content, distinguishable presentation, keyboard accessibility, and predictable navigation.
PDF/UA (ISO 14289). The universal accessibility standard specifically for PDF documents. It defines requirements for tagged PDF structure, font handling, content ordering, and metadata that ensure consistent accessibility across PDF readers and assistive technologies.
Section 508. US federal agencies must ensure their electronic documents are accessible under Section 508 of the Rehabilitation Act. This effectively requires WCAG 2.0 Level AA compliance for all published PDFs.
European Accessibility Act. Beginning in 2025, this EU directive requires accessibility for a wide range of products and services, including digital documents published by organizations within scope.
Frequently Asked Questions
What makes a PDF accessible?
An accessible PDF has proper document structure tags, alternative text for images, a logical reading order, sufficient color contrast, embedded fonts, and a defined document language. These elements allow screen readers and assistive technologies to interpret and present the content correctly to users with disabilities.
Is PDF accessibility legally required?
In many cases, yes. Government agencies in the US must comply with Section 508. Organizations covered by the ADA may need accessible documents. The EU's European Accessibility Act requires accessibility for many digital services. Educational institutions receiving federal funding must provide accessible materials under Section 504.
Can I make an existing PDF accessible without the source file?
Yes. PDF editing tools can add tags, alt text, and reading order to existing PDFs. While it's easier to create accessible PDFs from properly structured source documents, remediation of existing files is entirely possible. For scanned PDFs, apply OCR first using a PDF to text converter to create selectable text.
How do I test if my PDF is accessible?
Use built-in accessibility checkers in PDF software, test with screen readers like NVDA or JAWS, verify color contrast ratios meet WCAG standards (4.5:1 for normal text), and check that all content can be accessed via keyboard navigation. Automated tools catch structural issues, but manual testing with assistive technology catches usability problems.