A Practical Authoring, Remediation, and Quality-Assurance Guide

Follow these six steps to create, review, remediate, and share accessible PDF documents.

1 Set Up

Start with the right document and workflow

Why accessible PDF documents matter

An accessible PDF is more than a document that opens and looks correct on screen. Its text and underlying structure must also be available to people who use screen readers, keyboard navigation, magnification, reflow, and other assistive technologies.

PDF accessibility is usually most successful when the original Word, PowerPoint, InDesign, or other source file is created accessibly before conversion. Remediation in Adobe Acrobat Pro can correct many problems, but it should not be treated as a substitute for a well-structured source document.

Core principle

Create an accessible source whenever possible, export it in a way that preserves accessibility, and then inspect the resulting PDF. Visual appearance alone does not confirm accessibility.

Decide whether PDF is the right format

PDF can be useful when a fixed-layout document is required, but it is often more difficult to make accessible than a well-structured web page or source document. Before publishing only a PDF, consider whether the information can be provided in a more flexible accessible format.

  • Use PDF when the format serves a genuine publishing, archival, form, or fixed-layout need.
  • When practical, provide accessible HTML or another usable source format alongside the PDF.
  • If the PDF will be created from an Office document, correct accessibility issues in that source before conversion.

Avoid

Do not create a PDF simply because it preserves visual formatting. Choose the format based on how people need to access and use the information.

Start with an accessible source document

The quality of the source strongly affects the quality of the exported PDF. Before conversion, establish the structure and alternatives that assistive technology will need.

  • Use real heading styles in a logical hierarchy.
  • Use true bulleted and numbered lists.
  • Give meaningful images, charts, and diagrams appropriate alternative text.
  • Use descriptive hyperlink text.
  • Keep data tables simple and identify header rows.
  • Set the document language and meaningful title.
  • Use sufficient color contrast and do not rely on color alone.
  • Keep the reading sequence logical and avoid unnecessary floating or layered objects.

Companion guidance

For Office source files, use the companion guides Creating Accessible Microsoft Word Documents and Creating Accessible Microsoft PowerPoint Presentations before exporting.

2 Organize

Preserve document structure and navigation

Export the PDF without discarding structure

The conversion method matters. An accessible source can lose useful structure if the PDF is created through a workflow that does not preserve tags and document information.

  • Finish accessibility corrections in the source document.
  • Use the application’s Save As, Export, or supported Adobe PDF workflow.
  • When export options are available, preserve document structure tags for accessibility and heading-based bookmarks.
  • Open the exported PDF and review it rather than assuming the conversion was successful.

Avoid

Do not use Print to PDF as the standard accessibility workflow. Printing can flatten or discard structural information that assistive technology needs.

Understand and review PDF tags

Tags are the structural labels within a PDF that identify elements such as headings, paragraphs, lists, figures, links, and table cells. Screen readers use this structure to understand how content is organized.

  • Confirm that the document is tagged.
  • Review whether headings are identified as headings at appropriate levels.
  • Confirm paragraphs, lists, figures, links, and tables are represented appropriately.
  • Remove or correct unnecessary structural elements that interrupt the reading experience.
  • For complex remediation, use the Tags panel in Adobe Acrobat Pro to inspect and repair the structure.

Quality Check

A PDF can technically contain tags and still be inaccessible if those tags are incorrect, incomplete, or arranged in an illogical sequence.

Review headings, lists, and navigation

Long PDFs need predictable structure so readers can understand the hierarchy and move efficiently through the content.

  • Use headings in a logical sequence that reflects the document’s organization.
  • Make sure list items are represented as lists rather than a series of unrelated paragraphs.
  • For long documents, provide useful navigation such as bookmarks generated from the heading structure when appropriate.
  • Confirm that bookmarks describe their destinations and follow the document’s organization.

 

Add meaningful document properties and language

A meaningful document title helps users identify the file, and the correct language supports appropriate pronunciation and text processing by assistive technology.

  • Set a descriptive document title rather than relying only on the file name.
  • Confirm the primary document language.
  • For documents containing substantial passages in another language, review whether language changes are identified appropriately.
  • Use a clear file name that helps users recognize the document before opening it.

Avoid

Do not use bold, size, indentation, or visual numbering as the only indication that content is a heading or list.

3 Add Content

Ensure information is understandable

Provide useful alternatives for visual content

Meaningful images, charts, diagrams, and other figures need a text alternative when their information is not already available in surrounding text. Decorative content should not create unnecessary announcements.

  • Describe the purpose or essential information of meaningful figures.
  • For charts and graphs, communicate the key trend, comparison, or conclusion.
  • Avoid repeating nearby text word-for-word in the alternative text.
  • Mark purely decorative figures so they can be skipped by assistive technology.

Quality check

Alternative text should communicate equivalent meaning in context, not simply identify the object as an ‘image’ or ‘chart’.

Use accessible tables

Tables require clear structural relationships between header cells and data cells. Visually complex tables can become difficult to understand when navigated one cell at a time.

  • Use tables for data relationships rather than page layout.
  • Keep row and column structures as simple as the information allows.
  • Identify header cells correctly.
  • Avoid unnecessary merged, split, or nested cells.
  • Check the table’s tags and reading sequence after conversion.

 

Make links understandable

Links should communicate their destination or purpose without requiring the reader to interpret a long raw URL or vague phrases such as ‘click here.’

Avoid Better
Click here Download the Accessible Word Checklist
More information Microsoft Word Accessibility Support
A long pasted URL CUNYAccessibility Resources

After conversion, confirm that intended hyperlinks remain active and that the link annotation is associated with the correct text.

Design alternative

If a table cannot be made understandable without a complicated grid, consider reorganizing the information into simpler tables, lists, or narrative text.

Pay special attention to PDF forms

Interactive PDF forms introduce additional accessibility requirements. A user must be able to identify each control, understand what information is requested, move through the form in a logical sequence, and complete it without relying on a mouse.

  • Use interactive form fields rather than requiring users to print and handwrite responses.
  • Give each form control a meaningful accessible name or tooltip.
  • Group related radio buttons and checkboxes logically.
  • Check keyboard tab order.
  • Provide clear instructions and identify required fields accessibly.
  • Review form-field tags and run accessibility checks after the form is finalized.

Consider the format

When a form can be delivered effectively as an accessible web form, that format may be easier to maintain and use than a complex PDF form.

4 Format

Make the PDF usable for everyone

Make sure the PDF contains searchable text

A PDF made from a scan may contain only pictures of printed pages. The words may look normal to a sighted reader while remaining unavailable as actual text to search, select, copy, reflow, or read with a screen reader.

  • Try selecting individual words and searching for text in the PDF.
  • If the pages are image-only, use optical character recognition (OCR) to create searchable text.
  • After OCR, review the recognized text for errors, especially names, numbers, headings, tables, and low-quality scans.

Important

OCR creates machine-readable text, but OCR alone does not make a PDF accessible. The document still needs appropriate structure, reading order, alternatives, and other accessibility features.

Verify logical reading order

Reading order determines how content is encountered when it is read linearly by assistive technology or reorganized in a reflowed view. Multi-column pages, sidebars, floating objects, footnotes, and decorative elements can cause unexpected sequences.

  • Review the order in which headings, paragraphs, lists, figures, captions, and tables are encountered.
  • Check multi-column and visually complex pages carefully.
  • Make sure headers, footers, page numbers, and decorative items do not interrupt the main content.
  • Use Acrobat Pro’s accessibility and reading-order tools when structural repairs are necessary.

Practical test

The document should still make sense when the content is followed from beginning to end without relying on its visual position on the page.

Use color and visual presentation accessibly

The PDF should remain understandable for readers who cannot distinguish particular colors or who need increased contrast and magnification.

  • Use sufficient contrast between text or meaningful graphics and their backgrounds.
  • Pair color with labels, text, symbols, patterns, or another non-color cue.
  • Avoid low-contrast text, text over busy backgrounds, and visual treatments that reduce readability.
  • Check the document at high zoom and, when appropriate, in reflow view.
Color-only approach Accessible alternative
Red items require action. Label each relevant item ‘Action Required’ and optionally reinforce it with red.
Green = approved; yellow = pending. Include the text labels ‘Approved’ and ‘Pending’ in addition to color.

Practical test

The document should still make sense when the content is followed from beginning to end without relying on its visual position on the page.

5 Check

Review and test before sharing

Use the Accessibility Checker before sharing

Acrobat Pro can identify many common accessibility issues. Use the checker to locate problems, understand the applicable rule, and guide remediation, but do not treat a passing result as complete proof of accessibility.

  • Open the prepare for accessibility tools in Adobe Acrobat Pro.
  • Run the available accessibility check or full check.
  • Review failed items, warnings, and items that require manual verification.
  • Correct issues in the source document when that is more reliable; otherwise remediate the PDF.
  • Rerun the check after changes.

Perform a manual accessibility review

Before distributing the PDF, perform checks that automated tools cannot fully evaluate:

  • Confirm the document has searchable text and is not merely a collection of page images.
  • Review the heading hierarchy and bookmarks.
  • Follow the reading order through representative pages, especially complex layouts.
  • Check alternative text for usefulness and context.
  • Review table structure and header relationships.
  • Confirm links are descriptive and function correctly.
  • Check that information is not communicated by color alone.
  • Review the document at high zoom or in reflow view.
  • If possible, use a screen reader or text-to-speech spot-check to identify missing or out-of-sequence content.

Remember

Some requirements cannot be judged automatically, including whether alt text is meaningful, whether reading order makes sense, and whether complex content is understandable.

6 Export

Remediate and prepare for distribution

Use Adobe Acrobat Pro for remediation

When a PDF cannot be corrected adequately in its source, Adobe Acrobat Pro provides tools for inspecting and repairing document accessibility. Acrobat Reader is useful for viewing PDFs but does not provide the full remediation toolset.

  • Set or correct the document title and language.
  • Run OCR when the PDF contains scanned images of text.
  • Add or review tags.
  • Review reading order and structural panels.
  • Add or correct alternative text for figures.
  • Review links, tables, and other tagged elements.
  • Run Acrobat’s accessibility checking tools after repairs.

Important

Automated tagging and one-click accessibility actions are starting points. Complex documents still require human review of the resulting structure.

Common Accessibility Mistakes

Common problem Better approach
A scanned PDF contains only images of text. Run OCR, review recognition accuracy, then add and verify document structure.
A document is printed to PDF. Create an accessible source and use a supported Save As or Export workflow that preserves structure.
The PDF contains tags, so it is assumed accessible. Inspect whether the tags are correct, complete, and in a logical order.
A multi-column page reads across columns incorrectly. Repair the reading order or return to the source and simplify the layout.
Alt text says only ‘image’ or ‘chart.’ Describe the visual’s purpose or essential information.
A table uses a complicated grid with merged cells. Simplify the table and verify header/data relationships.
A link says ‘click here.’ Use link text that identifies the destination or action.
The accessibility checker passes, so review stops. Complete manual checks for reading order, alt text quality, tables, navigation, and usability.
A form must be printed and completed by hand. Provide accessible interactive fields or use an accessible alternative format.

Quick Checklist Before Sharing

  • The PDF has a meaningful file name and document title.
  • The document language is set correctly.
  • Text is searchable and scanned pages have been OCR-processed when necessary.
  • The PDF is tagged and the tag structure reflects the content.
  • Headings create a logical hierarchy and long documents have useful navigation.
  • Reading order is logical, including on complex or multi-column pages.
  • Lists are represented as lists.
  • Meaningful figures have useful alternative text and decorative content is handled appropriately.
  • Tables have clear structure and correctly identified headers.
  • Links describe their destination or action and work correctly.
    Color is not the only way meaning is communicated, and contrast is sufficient.
  • The PDF remains usable at high zoom or in reflow where applicable.
  • If the PDF is a form, fields, labels, groups, and keyboard tab order have been checked.
  • Accessibility checking has been run and issues have been reviewed.
  • A manual accessibility review (if possible) has been completed.

References and Further Guidance