PDF Accessibility: How to Make PDFs Everyone Can Read (2026)
Make your PDFs accessible to people with disabilities. Covers tagged PDFs, reading order, alt text, color contrast, form labels, and WCAG compliance.
- Make your PDFs accessible to people with disabilities.
- Why PDF Accessibility Matters.
- Covers tagged pdfs: the foundation.
- Covers reading order.
- Covers alternative text for images.
Why PDF Accessibility Matters
Over 1 billion people worldwide live with some form of disability. When you publish an inaccessible PDF, you’re potentially excluding 15% of your audience. Beyond the ethical imperative, accessibility is increasingly a legal requirement:
- US government documents must comply with Section 508
- EU public sector websites must meet WCAG 2.1 AA under the Web Accessibility Directive
- Many private sector lawsuits now cite inaccessible PDFs as ADA violations
- Educational institutions must provide accessible materials under disability rights laws
Tagged PDFs: The Foundation
Tags are the structural backbone of an accessible PDF. They define what each piece of content is — heading, paragraph, list, table cell, image — so assistive technology can present it meaningfully.
-webkit-backdrop-filter alongside backdrop-filter for Safari support. Without the prefix, the effect is invisible to roughly 25% of mobile users.How to Create Tagged PDFs
- Microsoft Word: Use built-in heading styles (Heading 1, Heading 2) and export with “Create Tagged PDF” enabled
- Google Docs: Apply heading styles, then File → Download as PDF. Tags are generated automatically.
- Adobe InDesign: Use paragraph styles mapped to PDF tags, export with “Create Tagged PDF” checked
- LibreOffice: Use heading styles, export with “Tagged PDF” option enabled
Reading Order
Screen readers read content in the tag order, not the visual layout order. A two-column layout that looks logical visually might be read column-by-column (left top to bottom, then right top to bottom) when the intended order is row-by-row.
backdrop-filter inside a position: fixed element can cause severe scroll performance issues. Test thoroughly on real iOS devices.- Always check reading order after creating your PDF
- Avoid complex multi-column layouts when possible
- Test with a screen reader (VoiceOver on Mac, NVDA on Windows)
- Adobe Acrobat Pro’s “Reading Order” tool lets you fix order issues
Alternative Text for Images
Every image that conveys meaning needs alternative text. This includes charts, diagrams, infographics, and photos. Decorative images should be marked as artifacts (ignored by screen readers).
- Be concise but descriptive: “Bar chart showing quarterly revenue growth from $2M to $3.4M”
- Don’t start with “Image of” — screen readers already announce it’s an image
- For complex charts, provide the data in a table nearby
- Add alt text in your source document before exporting to PDF
Color and Contrast
Text must have sufficient contrast against its background. WCAG 2.1 requires a minimum contrast ratio of 4.5:1 for body text and 3:1 for large text. Use our Contrast Checker to verify your color combinations before creating your PDF.
- Never rely on color alone to convey information (e.g., red text for errors)
- Provide text labels alongside color-coded elements
- Test with our Color Blindness Simulator to verify readability
Accessible PDF Forms
- Every form field needs a descriptive label
- Set a logical tab order so keyboard users can navigate fields sequentially
- Provide clear instructions and error messages
- Mark required fields with both visual indicators and screen-reader-accessible labels
- Test the form with keyboard-only navigation (no mouse)
Quick Accessibility Checklist
☐ Heading structure is logical (H1 → H2 → H3)
☐ Reading order matches intended flow
☐ All meaningful images have alt text
☐ Decorative images are marked as artifacts
☐ Color contrast meets WCAG 4.5:1 minimum
☐ Information isn’t conveyed by color alone
☐ Document language is set
☐ Tables have header rows defined
☐ Form fields have labels and tab order
☐ Document title is set in properties