Accessible PDFs are a legal requirement in many jurisdictions, yet most designers treat them as an afterthought. They finish the layout, export a polished PDF, and assume the job is done. The problem is that a visually beautiful document can be completely invisible to someone using a screen reader, and that gap carries real consequences. WCAG (Web Content Accessibility Guidelines) gives designers a clear, testable framework for closing that gap.
Originally built for websites, these guidelines apply equally to exported PDFs because PDFs are interactive documents that users navigate, read aloud, and interact with digitally. Adobe InDesign has strong built-in tools for producing WCAG-ready PDFs, but they only work if you know where to look and when to act. Building accessibility into your InDesign workflow from the start is faster, cheaper, and more reliable than patching problems later in Acrobat.
Why WCAG Compliance Matters for PDF Documents
Who Is Affected by Inaccessible PDFs
More than a billion people worldwide live with some form of disability. That includes people with visual impairments who use screen readers, people with motor disabilities who rely on keyboard navigation instead of a mouse, people with cognitive disabilities who depend on clear structure and consistent heading hierarchies, and people with low vision who need sufficient contrast to read body text. An inaccessible PDF can exclude or disadvantage many of these users.
The document might be a government report, a product brochure, a medical form, or an annual report. Whatever it contains, if a screen reader cannot parse the reading order or interpret an image, that information simply disappears for a significant portion of the audience.
Legal and Regulatory Pressure Designers Should Know About
Accessibility requirements for digital documents are becoming increasingly important across many jurisdictions. In the United States, Section 508 requires federal agencies to make their electronic and information technology accessible, while the Americans with Disabilities Act (ADA) can apply to digital content provided by public entities and businesses covered by the Act.
In the EU, the European Accessibility Act introduces accessibility requirements for specified products and services, including certain digital services. For designers, these requirements reinforce the importance of treating accessibility as a core part of professional document production rather than an optional consideration.
Understanding WCAG Principles as They Apply to PDFs
WCAG organises its requirements around four principles, often called POUR: Perceivable, Operable, Understandable, and Robust. Each one maps directly onto decisions designers make during layout.
Perceivable: Making Visual Content Available to All
Every user must be able to receive content regardless of the sense or technology they use to consume it. For a PDF, that means images need descriptive alt text so that screen readers can announce them. Charts and infographics need text equivalents or captions that convey the same information the visual encodes.
Colour alone cannot carry meaning, because someone with colour blindness will miss a message conveyed only by a red or green indicator. Contrast ratios must meet minimum thresholds so that low-vision users can distinguish text from background. Every visual decision a designer makes has a perceivability dimension.
Operable and Robust: Structure, Navigation, and Tagging Basics
Operable content lets users navigate the document without relying solely on a mouse. In PDF terms, that means a logical tab order so keyboard users can move through links, form fields, and interactive elements in a sensible sequence. Bookmarks support navigation through long documents. Headings structured at the correct levels let screen reader users jump between sections rather than reading every word sequentially.
Robust content holds up across different assistive technologies, which in PDF terms means proper tagging. Tags are the behind-the-scenes structure that tells a screen reader what each element is: a paragraph, a heading, a table cell, a list item, a figure. Without tags, a PDF lacks the semantic structure assistive technologies need to interpret and navigate the content reliably.
Setting Up Your InDesign Document for Accessibility from the Start

Retrofitting accessibility after a document is finished costs significantly more time than building it in from the beginning. A few upfront decisions pay dividends throughout the entire project.
Document Language and Metadata Settings
Set the document language before you type a single word. Set the correct language for your text using InDesign’s language settings and paragraph styles, and confirm the document language when exporting the PDF.
Screen readers use the document language to select the correct pronunciation engine and text-to-speech rules. A screen reader encountering French text tagged as English will mispronounce it badly enough to make the content unintelligible.
In the File > File Info panel, add useful metadata such as the Title, Author, Subject, and Keywords. A descriptive document title is important for accessibility, while the other fields provide helpful document metadata. Adding a document title takes only a few moments and helps ensure the PDF is properly identified.
Using Paragraph Styles to Create Semantic Structure
Paragraph styles are the backbone of an accessible InDesign document. Every heading should use a named style (Heading 1, Heading 2, Heading 3) with an Export Tagging assigned in the style options. To set this, open a paragraph style, navigate to Export Tagging, and map the style to the correct HTML/PDF tag.
Body text maps to<p>, top-level section titles map to <h1> or <h2> depending on hierarchy, and pull quotes or captions get their own appropriately tagged styles. On export, InDesign uses these mappings to generate tagged PDF elements. Designers who format text manually with local overrides instead of styles produce PDFs that lack semantic structure, because InDesign has no way to infer heading hierarchy from font size alone.
The Articles Panel: Controlling Reading Order
The Articles panel (Window > Articles) controls the order in which a screen reader reads content, regardless of where elements sit visually on the page. A sidebar that appears physically beside a paragraph in the layout might get read in the middle of a sentence if the reading order is not explicitly defined.
Add all meaningful content elements to the Articles panel and drag them into the correct logical sequence. Exclude decorative elements entirely. This is the single most impactful accessibility step many designers skip, and it cannot be replicated in Acrobat without laboriously retagging every page.
Writing and Applying Alt Text for Images and Graphics
Object Export Options: Where to Add Alt Text
Alt text in InDesign lives in the Object Export Options dialogue. Select any image or graphic frame, then go to Object > Object Export Options and click the Alt Text tab. From the dropdown, choose Custom and type your description directly. InDesign stores this alt text and passes it into the tagged PDF on export.
For images that pull descriptions from metadata already embedded in the image file, you can select the option to read from the XMP metadata field. Every meaningful image must have a corresponding description set at the object level before export.
Writing Effective Alt Text vs. Marking Decorative Images
Good alt text describes what the image communicates in context, not just what it depicts. A photograph of a bar chart should not be described as “bar chart image.” It should describe the trend the chart shows: “Bar chart showing a 34% increase in renewable energy adoption from 2019 to 2023.” Keep descriptions under 150 characters where possible, and front-load the most important detail.
For decorative images such as borders, background textures, or purely aesthetic icons, open Object Export Options, go to Tagged PDF, and set Apply Tag to Artifact. This instructs assistive technologies to skip the element, preventing unnecessary noise that can disrupt the reading flow. Getting this distinction right matters: over-describing decorative elements can be almost as disruptive as under-describing meaningful ones.
Colour, Contrast, and Typography Choices That Meet WCAG Standards
Checking Contrast Ratios Without Leaving Your Workflow
WCAG 2.1 AA requires a contrast ratio of at least 4.5:1 between normal body text and its background, and 3:1 for large text (defined as 18pt regular or 14pt bold). Adobe Colour (color.adobe.com) includes a contrast checker where you can input hex values directly and see whether your combination passes. The Colour Contrast Analyser by TPGi is a free desktop tool that lets you sample any colour on screen.
Some InDesign plugins, including Accessible PDF and axesPDF for InDesign, surface contrast warnings directly in the panel. Check contrast for every text-on-colour combination in the design, not just body copy; button labels, captions, and reversed-out headers all need to meet the threshold.
Typography and Layout Choices That Support Readability
For typography, favour typefaces with clear letterform distinction at small sizes. A body text size of around 12pt can improve readability for documents viewed on screen, while generous line spacing and moderate line lengths can make text easier to follow. These are useful design practices rather than specific WCAG AA requirements.
Justified text can create uneven word spacing that disrupts reading flow, so left-aligned body text generally performs better for accessibility. Wide columns of text can also be harder to track across lines, so keeping line lengths moderate can improve readability.
Exporting a Tagged, WCAG-Ready PDF from InDesign

Choosing the Right PDF Export Preset for Accessibility
Go to File > Export and choose Adobe PDF (Interactive) when your document contains hyperlinks, form fields, or navigation elements users will interact with on screen. Choose Adobe PDF (Print) for documents that will primarily be read, with the understanding that you still need to enable accessibility options manually.
Neither preset enables full accessibility by default. Start from a known preset such as PDF/UA-1 if your organisation requires it, or create a custom preset with accessibility options locked in and save it for reuse across the team.
Key Checkboxes in the Export Dialogue That Impact Compliance
In the General tab of the Export dialogue, check Create Tagged PDF. Without this, the PDF exports as an untagged document that screen readers cannot interpret.
In the Advanced section of the Interactive PDF export dialogue, enable Use Structure for Tab Order so the PDF follows the document’s structural reading order when users navigate with the keyboard. Under the Advanced tab, confirm that the document language populated from your metadata settings appears correctly.
Enable Bookmarks and Hyperlinks so navigational elements carry through to the exported file. If you are creating an interactive PDF with form fields, check the Create Acrobat Layers option only if your layer structure is meaningful; unnecessary layers add complexity without benefit.
Validating Your PDF’s Accessibility After Export
Using Acrobat Pro’s Accessibility Checker
Open the exported PDF in Adobe Acrobat Pro, then go to All tools > Prepare for accessibility > Check for accessibility. The checker evaluates the document against a range of accessibility criteria and produces a report organised by category, including document, page content, forms, tables, lists, and headings. Pay close attention to failures rather than warnings.
Common failures include “Figure alternate text failed” (missing alt text), “Title failed” (empty document title field), and “Tab order failed” (reading order not set). Each failure links back to a specific element in the PDF, and most should send you back to the InDesign source file to fix rather than patching in Acrobat’s tag editor, which is tedious and does not persist across re-exports.
Free Tools and Screen Readers for Real-World Testing
PAC (PDF Accessibility Checker) tests PDFs against the PDF/UA standard and provides detailed accessibility results that complement Acrobat’s built-in checker. Use the current version available from the official PAC website rather than referring specifically to PAC 3. For real-world testing, NVDA (NonVisual Desktop Access) is a free, open-source screen reader for Windows that lets you hear how your PDF actually reads aloud.
JAWS is the industry-standard commercial screen reader used by many professional accessibility testers. Tab through the document, listen to how images are announced, and check whether headings allow you to jump through the document structure. No automated checker catches everything a real user would encounter.
Conclusion
Accessible PDFs start with decisions made at the very beginning of a project, not at the export stage. Set the document language and fill in metadata fields before layout begins. Build every text element on named paragraph styles with correct export tags assigned, and use the Articles panel to define the logical reading sequence across every spread.
Write alt text for meaningful images and mark decorative ones as artifacts before export, and check every text and background colour combination against WCAG contrast thresholds and correct failures in the design itself. When you export, enable Create Tagged PDF, Use Document Structure for Tab Order, Bookmarks, and Hyperlinks in the export dialogue.
After export, run Acrobat Pro’s full accessibility checker and test with PAC 3. Listen to the document in NVDA or JAWS to catch anything automated tools miss. When failures appear, fix them in the InDesign source and re-export rather than patching tags manually in Acrobat, which is slow, fragile, and lost with every new export.
WCAG compliance is a learnable, repeatable workflow. Once it becomes part of how you build documents rather than a checklist applied at the end, the overhead drops dramatically. Accessible documents are also better documents. Clearer structure, stronger navigation, and more consistent typography benefit every reader, with or without a disability.