ADA Guidelines for Accessible PDFs: How to Create Accessible Documents in Adobe Acrobat Pro

This guide explains how to create, review, and remediate accessible PDF documents from the source file and in Adobe Acrobat Pro. It presents core principles, workflow steps, required elements, and institutional best practices to strengthen compliance, inclusion, and digital resilience.

By Cristo Leon, Ph.D.

Created Friday, March 13, 2026.

1. Purpose and rationale

PDF accessibility should not be treated as a narrow compliance exercise. It is a core practice of equitable communication, inclusive teaching, and sustainable document design. Accessible PDFs improve usability for people who use screen readers and other assistive technologies, but they also benefit broader audiences, including mobile users, multilingual readers, and anyone working under constrained viewing conditions. This aligns both with legal obligations and with Universal Design for Learning principles that emphasize broader access through better design. (ADA.gov)

2. Scope

These guidelines apply to institutional PDF content intended for public or academic use, including syllabi, handbooks, reports, forms, contracts, instructional materials, presentations exported as PDFs, and archived or legacy documents distributed through university systems.

3. Foundational principle: fix the source first

Accessibility remediation should begin in the source file, not in the PDF, whenever the source is available. Microsoft Word, PowerPoint, and similar authoring tools preserve structural information such as headings, lists, table headers, hyperlinks, and alternative text when the file is properly authored and then exported to PDF. Adobe Acrobat Pro should be used primarily for final verification and for remediating legacy or externally supplied PDFs when the original source cannot be edited. Adobe’s own guidance emphasizes starting with a well-structured source document whenever possible. (Adobe Help Center)

4. Exporting to PDF correctly

Documents should be exported to PDF using Save As PDF or Export to PDF, not by using Print to PDF. Printing to PDF commonly strips structural metadata and accessibility information, producing a visually similar but semantically degraded file. When exporting, users should ensure that document structure tags for accessibility are retained. Adobe and accessibility guidance both treat tagged PDF generation as a core requirement for downstream accessibility. (Adobe Help Center)

5. Required accessibility elements in PDFs

An accessible PDF should include the following minimum components:

Document title and metadata. Every PDF should have a meaningful title set in document properties so assistive technologies can identify the file correctly. Acrobat’s accessibility workflow explicitly prompts for this because missing titles are a common defect. (Adobe Help Center)

Declared document language. The primary language of the document must be set correctly so screen readers apply proper pronunciation and parsing rules. Acrobat includes language declaration as part of its accessibility workflow. (Adobe Help Center)

Structural tags. The document must include semantic tags for headings, paragraphs, lists, tables, figures, and other content elements. Tags provide the nonvisual structure that allows screen readers to interpret hierarchy and navigation. Without tags, a PDF may appear readable visually while remaining functionally unusable to assistive technologies. (Adobe Help Center)

Logical reading order. The content must be presented in the correct reading sequence. This is especially important for multicolumn layouts, sidebars, mixed media documents, and exported slide decks. Automated tools may not reliably detect intended order, so manual review is necessary. Adobe notes that Acrobat Pro supports reading order editing because this is a frequent remediation need. (Adobe Help Center)

Alternative text for meaningful images. Figures, diagrams, charts, and instructional images must include concise alternative text that communicates purpose and informational value. Purely decorative elements should be marked decorative so they are ignored by screen readers. (Adobe Help Center)

Accessible tables. Tables must include header rows and a structurally meaningful layout. Tables should not be used for visual layout. In source files, designated header rows should be set before export. In Acrobat, tables may require additional checking when imported from older or poorly structured files. (Adobe Help Center)

Searchable text. Scanned PDFs must be processed with OCR so text becomes machine-readable and selectable. Image-only PDFs are not accessible because assistive technologies cannot reliably interpret them as text. Acrobat’s accessibility workflow includes OCR specifically for this reason. (Adobe Help Center)

Functional links and form fields. Hyperlinks should be active and clearly identified. If the PDF contains forms, fields must be programmatically labeled and tab in a logical order. Acrobat’s workflow distinguishes between ordinary PDFs and fillable forms because forms require additional remediation steps. (Adobe Help Center)

6. Recommended workflow in Adobe Acrobat Pro

For PDFs that require remediation in Acrobat Pro, the recommended baseline workflow is:

  1. Open the PDF in Acrobat Pro.
  2. Use Guided Actions or Prepare for accessibility / Make Accessible.
  3. Add or confirm document title and language.
  4. Run OCR if the file is scanned or image-based.
  5. Review auto-tagging results.
  6. Check alternative text for figures.
  7. Run the Accessibility Checker.
  8. Manually inspect reading order, heading structure, tables, and image tagging.
  9. Save the remediated file and recheck before distribution.

Adobe describes the guided workflow as a structured process that identifies missing titles, scanned text, forms, tables, and images that need attention. (Adobe Help Center)

7. Limits of automation

Automated accessibility tools are necessary but not sufficient. Acrobat’s checker can identify common issues, but it cannot reliably determine whether reading order is conceptually correct, whether alternative text is meaningful, whether a table is logically structured, or whether OCR output introduced errors. Adobe’s own documentation notes that accessibility checking assists evaluation but does not guarantee compliance or usability on its own. Human review remains essential. (adobe.com)

8. Guidance for scanned and legacy PDFs

When a document originates as a scan, remediation is possible but often limited by source quality. Low-resolution images, skewed pages, shadows, handwritten notes, and older photocopies reduce OCR accuracy and often produce fragmented or incorrect tags. In these cases:

  • run OCR first,
  • review the recognized text for errors,
  • inspect tagging manually,
  • correct reading order,
  • retag headings and figures as needed.

Where a source document can be reconstructed or reauthored, rebuilding the file may be more efficient and more accessible than attempting to repair a poor scan. Adobe guidance supports choosing workflow based on the document’s origin and purpose. (Adobe Help Center)

9. Standard PDF versus PDF/A

For routine teaching, communication, and operational use, a standard tagged PDF is generally preferable. PDF/A is designed for archival preservation and may restrict dynamic content or create unnecessary complexity for ordinary workflows. It should be used only when archival requirements explicitly demand it. Adobe’s guidance distinguishes workflow by document purpose, and PDF/A is best treated as a preservation format rather than a default accessibility format. (Adobe Help Center)

10. Institutional good practice

Institutions should treat PDF accessibility as part of a broader content lifecycle rather than as a last-minute remediation task. Good practice includes training authors to create accessible source files, requiring accessibility checks before publication, maintaining shared templates, and prioritizing high-use public-facing documents for remediation. DOJ guidance for state and local governments emphasizes planning, inventorying content, and integrating accessibility into ordinary operations rather than handling it only after complaints arise. (ADA.gov)

Condensed operational checklist

Before distributing a PDF, confirm that:

  • the file was exported from an accessible source, not printed to PDF
  • the document title is set
  • the primary language is defined
  • text is searchable
  • headings and lists are tagged properly
  • reading order is correct
  • images have meaningful alt text or are marked decorative
  • tables include header structure
  • links and forms are functional and labeled
  • Acrobat’s Accessibility Checker has been run
  • a human reviewer has verified the result

Closing

Accessible PDFs are not merely compliant PDFs. They are documents that preserve meaning across devices, modalities, and user needs. By fixing source files first, exporting correctly, and using Acrobat Pro for targeted remediation and verification, institutions can improve legal readiness, pedagogical inclusion, and long-term digital resilience at the same time. (ADA.gov)