Prepare for Accessibility — Make PDFs Accessible & Compliant

How to Make a PDF Accessible

The Complete Guide to PDF Accessibility

Why PDF Accessibility Is a Legal and Ethical Requirement

Over one billion people worldwide live with some form of disability, and many rely on assistive technologies like screen readers, magnification software, and alternative input devices to access digital content. When PDF documents are not properly structured for accessibility, they are effectively invisible to these users. This is not just an ethical issue but a legal one. In the United States, Section 508 of the Rehabilitation Act requires federal agencies to make their electronic documents accessible, and the Americans with Disabilities Act has been interpreted by courts to apply to digital content including PDFs.

The European Accessibility Act and EN 301 549 standard impose similar requirements across the European Union. Canada, Australia, and many other countries have enacted comparable legislation. Organizations that fail to provide accessible documents face legal action, fines, and reputational damage. More importantly, accessible documents serve everyone better, as proper structure, clear headings, and logical reading order improve the experience for all users regardless of ability.

Understanding PDF Tags and Document Structure

The foundation of PDF accessibility is the tag tree, a hierarchical structure that describes the logical organization of the document's content. Tags identify each element's role: headings (H1 through H6), paragraphs (P), lists (L, LI), tables (Table, TR, TH, TD), images (Figure), links (Link), and many more. Screen readers use these tags to present content in a meaningful order and provide navigation capabilities, such as jumping between headings, skipping tables, and listing all links on a page.

Without tags, a screen reader can only read the raw text in the order it appears in the file's internal structure, which often differs significantly from the visual layout. ZentDoc's auto-tagging engine analyzes the visual layout of your document, identifies the semantic role of each element based on its size, position, font, and context, and generates the correct tag tree automatically. You can then review and adjust the tags manually if needed.

Writing Effective Alternative Text for Images

Alternative text, commonly called alt text, is a textual description of an image that screen readers vocalize for users who cannot see the image. Every meaningful image in an accessible PDF must have alt text, while decorative images that add no information should be marked as artifacts so screen readers skip them entirely. Effective alt text is concise yet descriptive, conveying the essential information the image communicates.

For a photograph of a team meeting, appropriate alt text might be "Five team members discussing quarterly results around a conference table." For a chart showing revenue growth, the alt text should convey the key data: "Bar chart showing revenue growth from 2 million dollars in 2022 to 3.5 million dollars in 2025." Avoid redundant phrases like "image of" or "picture showing" since the screen reader already announces that it is an image. ZentDoc's AI-assisted alt text generator analyzes images and suggests descriptive text that you can review and refine, dramatically accelerating the alt text authoring process.

Setting Correct Reading Order

Reading order determines the sequence in which a screen reader presents content to the user. For simple single-column documents, reading order is straightforward: top to bottom, left to right. But many documents have complex layouts with multiple columns, sidebars, pull quotes, captions, headers, footers, and floating elements that interrupt the linear flow. When a PDF is created from a design tool, the internal content order often does not match the visual layout.

A two-column page might have all left-column text followed by all right-column text, causing a screen reader to read the entire left column before starting the right column, even though a sighted reader would read across both columns paragraph by paragraph. ZentDoc's reading order tool lets you visually define the correct reading sequence by numbering each content block. The tool also detects common layout patterns and suggests the correct reading order automatically, which you can verify and adjust.

Making Tables Accessible

Tables are one of the most challenging elements to make accessible because screen reader users cannot see the spatial relationships between cells. When a sighted person looks at a table, they can instantly see which column header and row header apply to any data cell. A screen reader user depends entirely on proper table tags to provide this context. Each table must have its header cells tagged as TH (table header) and data cells tagged as TD (table data).

The scope attribute on headers indicates whether they apply to a row, column, or group. For complex tables with spanning cells or multiple header levels, IDs and headers attributes explicitly link each data cell to its relevant headers. ZentDoc's table structure tool provides a visual interface for tagging table elements. It auto-detects header rows and columns based on formatting cues like bold text and background colors, and lets you manually adjust the structure for complex tables.

WCAG 2.1 and PDF/UA Compliance Standards

Two main standards govern PDF accessibility. The Web Content Accessibility Guidelines (WCAG) 2.1, published by the W3C, provide comprehensive accessibility requirements organized into four principles: perceivable, operable, understandable, and robust. WCAG defines three conformance levels: A (minimum), AA (recommended), and AAA (highest). Most legal requirements specify WCAG 2.1 Level AA as the target.

PDF/UA (Universal Accessibility), formally known as ISO 14289, is a standard specifically for accessible PDFs that defines technical requirements for PDF document structure, tags, fonts, and metadata. A document that meets PDF/UA generally also meets the PDF-specific requirements of WCAG 2.1 Level AA. ZentDoc checks your document against both standards simultaneously, providing a unified compliance report that identifies which requirements are met, which have issues, and which require manual verification by a human reviewer.

Color Contrast and Visual Accessibility

Color contrast is a critical but often overlooked aspect of PDF accessibility. WCAG 2.1 requires a minimum contrast ratio of 4.5 to 1 for normal text and 3 to 1 for large text between the foreground color and background color. This ensures that text is readable for people with low vision, color blindness, or those viewing documents in challenging lighting conditions. ZentDoc's accessibility checker scans every text element in your document and calculates its contrast ratio against the underlying background.

Elements that fail to meet the minimum contrast ratio are flagged with their current ratio and the minimum required ratio. The tool suggests color adjustments that bring the contrast into compliance while maintaining the visual design intent as closely as possible. Beyond contrast, information should never be conveyed through color alone; charts that use only color to distinguish data series must also use patterns, labels, or other visual differentiators to ensure colorblind users can interpret the data correctly.

Document Language and Metadata Requirements

Accessible PDFs must specify the document's primary language in the metadata so screen readers can use the correct pronunciation engine. A document tagged as English will be read with English pronunciation rules, which is essential for correct vocalization. If the document contains passages in other languages, those passages should be tagged with their specific language to trigger the appropriate pronunciation engine for those sections.

ZentDoc automatically detects the document language and sets it in the metadata. It also identifies passages in different languages and tags them accordingly. Beyond language, the document title should be set in the metadata and configured to display in the title bar rather than the filename, providing meaningful context when users have multiple documents open. A document description and keywords in the metadata further enhance accessibility and discoverability of the document.

Frequently Asked Questions