Making accessible PDFs

PDFs on your site must meet WCAG 2.1 Level AA accessibility standards under ADA Title II. Districts with 50,000+ students must comply by April 26, 2027; smaller districts by April 26, 2028. This article covers a four-phase process: auditing your library, applying compliance standards, optimizing source documents, and using professional tools to find and fix gaps.

Portable Document Format (PDF) files are a reliable and secure way to present information to your users that will remain consistent on all devices and technologies, including assistive technologies like screen readers. It is your responsibility as a content creator to review and ensure that all PDFs that link from your site are accessible to all users.

This guide provides a professional roadmap to audit, create, and remediate your PDF library to ensure digital equity for all users.

In this article

• Phase 1: Audit and strategize your document library
  • Pro-Tip: Managing old PDF
• Phase 2: Adhere to mandatory compliance standards
  • Core file requirements
  • Semantic tagging and reading order
  • Media and table accessibility
  • Accessible form design
• Phase 3: Optimize the source document before export
• Phase 4: Audit and remediate accessibility gaps with professional tools
  • Validation & testing tools
  • Creation & remediation tools

Phase 1: Audit and strategize your document library

Building an accessible PDF takes a lot of planning, testing, and time. Before creating and linking to a PDF on your site, take these precautions:

• Audit your existing files: Before remediating an old PDF, check its Where Used status. If the document is outdated or rarely accessed, delete it rather than spending time fixing it.
• Prioritize HTML: Ask yourself: Can I present this content more clearly on a standard Composer page? HTML is inherently more accessible and easier to maintain than PDF; if you can present the information as a webpage, that is the superior choice for compliance.

Phase 2: Adhere to mandatory compliance standards

Use this checklist as your primary standard for any document that must remain in PDF format (such as official signed forms or high-density manuals).

Core file requirements

• File naming: Use clear, concise file names (max 30 characters) without special characters or spaces.
• Document metadata: Declare the document Title (in the description tab) and Language (in the advanced tab). HHS Note: The "Title" must be set to display in the window title bar rather than the "File Name."
• Security settings: Ensure that security settings (passwords/permissions) do not interfere with a screen reader's ability to access the text.
• Color contrast: Ensure a color-contrast ratio of at least 4.5:1 for standard text and 3:1 for large text or essential UI components.

Semantic tagging and reading order

• Tagging: Every visual element must be correctly tagged (e.g., <P> for paragraphs, <H1>-<H6> for headings).
• Logical reading order: Use the "Reading Order" tool to verify that content follows a natural sequence (usually top-to-bottom, left-to-right) that makes sense when read aloud.
• Artifacting: Mark purely decorative elements (background shapes, lines, or repeated headers) as "Artifacts" so screen readers skip them.

Media and table accessibility

• Meaningful alt-text: Provide descriptive alternative text for all images. HHS Note: If an image contains text, that text must be included in the alt-text.
• Data tables: Tables must have a dedicated Header Row (<TH>). Do not use tables for visual layout; only use them for data relationships.
• No merged cells: Avoid merged or split cells, as they break the programmatic "grid" that assistive technology relies on.

Accessible form design

• Form labels: Every form field must have a visible label and a corresponding "Tool Tip" that matches the label text.
• Tab order: Users must be able to navigate through all form fields in a logical order using only the Tab key.

Phase 3: Optimize the source document before export

Accessibility must be "baked in" to the native document (Word, InDesign, etc.) before it is ever exported to PDF.

• Native formatting: Use the built-in heading styles and list tools in your word processor. Typing hyphens or numbers manually prevents screen readers from announcing list totals.
• Proper conversion: When saving to PDF, use settings that "Retain structure tags."
• Avoid "Print to PDF": Never use the print-to-PDF function. This creates a "flat" image of the document and strips away all underlying accessibility data.

Phase 4: Audit and remediate accessibility gaps with professional tools

As you prepare your digital library for the April 2026 deadline, use these tools to audit your files and fix any remaining errors.

Validation & testing tools

Use these to identify errors in your PDF's structure, tagging, or reading order:

• Adobe PDF Accessibility Checker: A built-in tool for Acrobat Pro users to run comprehensive "Full Checks" on any document.
• PAC 2024: The free international standard for PDF/UA and WCAG 2.1 validation. Use this to generate the detailed compliance reports required for high-level audits.
• PDF Checker (Mac): A lightweight, native validation tool for macOS users.

Creation & remediation tools

If your audit reveals errors, these specialized tools can help you fix them efficiently:

• CommonLook PDF: A professional plugin for Adobe Acrobat that provides a guided workflow for complex remediation and high-volume document tagging.
• Equidox: A cloud-based, AI-powered tool that automatically identifies headings, lists, and tables to speed up the remediation of large file libraries.
• PAVE: A free, web-based tool ideal for remediating individual documents directly in your browser without specialized software.
• ABBYY FineReader PDF: The industry-leading tool for converting "scanned" image-only PDFs into searchable, accessible text through advanced OCR technology.