DOCUMENT ACCESSIBILITY / PDF

Make PDF documents accessible

Give readers accurate text, useful structure, and a dependable way through every page, whether they read visually, enlarge the content, or use a screen reader.

Start with the first stepKeep review notes

PDF documents (.pdf) · Seven practical steps · Reviewed 18 September 2026

START HERE

Keep the original file and work on a copy. If you have the Word, PowerPoint, or layout file, start there. If you only have a PDF, inspect its text and tags first. A scan needs text recognition before structural repair. The menu examples below follow Adobe Acrobat Pro desktop guidance updated in February 2026; other versions and editors differ. PDF/UA defines requirements specifically for accessible PDF. WCAG describes accessibility outcomes across web content, including PDFs. They overlap, but satisfying one does not automatically establish conformance with the other.

Work through your PDF file

STEP 01

Start with the best available file

Fixing the source makes future editions easier to maintain. A scan adds a separate text-recognition task.

  1. With a source file, repair its headings, lists, tables, and image alternatives. Use an export option that preserves PDF accessibility tags, then inspect the exported PDF.
  2. With an existing PDF, try selecting and searching text on every type of page. Check for an existing tag tree before deciding what needs repair; selectable text alone is insufficient.
  3. For scanned pages, use optical character recognition (OCR). In Acrobat, open All tools > Scan & OCR, then Recognize Text > In this file. Select the relevant pages and recognition language.
  4. Compare recognized text with the scan, correcting mistakes in words, numbers, punctuation, and reading direction. Improve or replace unreadable scans. Continue with tagging after OCR; recognition does not supply a complete accessible structure.

Check it: Can you find and copy accurate text, including text on inserted or scanned pages?

Adobe: Creating accessible PDFs · Section508.gov: Converting scanned documents

STEP 02

Inspect the tags and reading order

A page can look orderly while its underlying content sends readers between unrelated passages.

  1. Open the Accessibility tags panel in Acrobat Pro. Tags describe the roles and relationships of content; their presence alone does not establish accessibility.
  2. If tags are missing, export again with tagging enabled or use Acrobat's automatic tagging as a starting point. Review the result instead of accepting it unchanged.
  3. Follow the tag sequence through each page. Check columns, sidebars, captions, footnotes, and page transitions. Keep explanations beside the material they explain in the reading sequence.
  4. Highlight the content associated with each tag and inspect the order inside it. Repair missing, duplicated, or misplaced content; a numbered page overlay alone cannot confirm the complete tag structure.

Check it: Does a continuous screen-reader reading follow a meaningful sequence without omissions or interruptions?

W3C PDF3: Tab and reading order · Adobe: Reading Order tool

STEP 03

Identify headings, lists, and tables

Structure lets people navigate sections and understand relationships without relying on font size or position.

  1. Give headings appropriate heading tags and a logical hierarchy. A bold paragraph is still a paragraph unless its role is represented in the tags.
  2. Check that lists have a list container and list-item structure. Typed bullet characters in ordinary paragraphs do not provide the same information.
  3. Inspect each data table for table, row, header-cell, and data-cell tags. Check that headers are associated with the cells they describe.
  4. Simplify complicated merged-cell layouts where possible. Where complex relationships are necessary, repair their associations and verify them with a screen reader.

Check it: Can someone navigate by heading and understand each table value together with its headers?

W3C PDF9: Heading tags · W3C PDF21: List tags · W3C PDF6: Table markup · W3C PDF20: Repairing table associations

STEP 04

Explain images and make text readable

Readers need the information in a visual, and sufficient contrast to use the visible page.

  1. Add image alternatives that explain each meaningful image's purpose in this document. Check their accuracy after export.
  2. For charts or diagrams, put essential findings and detailed information in nearby text or a data table. A short image label rarely conveys the whole message.
  3. Mark purely decorative graphics as artifacts so they do not interrupt reading. Keep informative graphics in the reading structure.
  4. Check text contrast: at least 4.5:1 for ordinary text, or 3:1 for large text of at least 18 point, or 14 point bold. Add words or symbols when color communicates status.

Check it: Can a reader get the same information without seeing the image or distinguishing its colors?

W3C PDF1: Image alternatives · W3C PDF4: Decorative images · W3C: Contrast minimum · W3C: Use of color

STEP 05

Set the title, language, and navigation

Clear document information helps readers recognize the file, hear the right pronunciation, and find sections.

  1. In Acrobat's document properties, enter a descriptive title under Description. Under Initial View, set the window to show the document title.
  2. Set the primary language under Advanced. Identify passages in another language through their tag properties where appropriate.
  3. Add useful bookmarks for longer documents, reflecting their section hierarchy. Open each bookmark to confirm its destination.
  4. Check that PDF page labels agree with the page numbers readers see, including introductory pages using a different numbering system.

Check it: Can someone identify the document and reach a named section without reading every preceding page?

Adobe: Create and verify PDF accessibility · W3C PDF18: Document title · W3C PDF17: Consistent page numbering

STEP 07

Verify the saved file and share it

Export, page replacement, or later editing can change a document that previously worked well.

  1. In Acrobat Pro, use All tools > Prepare for accessibility > Check for accessibility. Investigate failures and complete items needing manual review.
  2. Review meaning and usability yourself, including heading navigation, image descriptions, tables, and keyboard operation. A checker pass does not establish complete WCAG or PDF/UA conformance.
  3. Enlarge the page and try Reflow. Look for lost or overlapping text and a disrupted sequence. Reflow has limitations with forms and other content, so it cannot replace the other checks.
  4. Save, close, and reopen the final PDF. Share this verified version with a descriptive filename. Keep source corrections for the next edition, and offer an accessible HTML or editable version when it better serves readers.

Check it: Have you reviewed the exact file being distributed and recorded any unresolved barriers?

Adobe: PDF accessibility checking · Adobe: Reflow and accessibility features · PDF Association: PDF/UA in accessibility checklists

What that looks like in practice

A scanned timetable

Before

The scan looks clear, but searching for the departure time finds nothing.

Try this

OCR supplies text; the author corrects 08:15 misread as 08:IS, then repairs table structure.

Text recognition and meaningful table relationships solve different problems.

A floating note

Before

A refund note beside the price is read after an unrelated contact section.

Try this

The note follows the price explanation in the tag sequence.

Reading order preserves the connection that position made visible.

A useful field name

Before

The visible label says Booking reference; the field announces Text7.

Try this

Its accessible name is Booking reference, with format instructions before the field.

The control's name now tells a keyboard and screen-reader user what to enter.

When something still isn’t working

The PDF is tagged, but reading jumps around.

Inspect the tag sequence and the content inside tags, especially around columns and inserted pages.

OCR finished, but names and numbers are wrong.

Compare the recognized text with the scan and correct errors before structural review.

Table headers look bold but are not announced.

Check header-cell tags and their associations with data cells.

Every update requires the same PDF repairs.

Correct the source template and export settings, then verify each new PDF.

Go to the original instructions

App menus and features can change. Use the instructions for your version, then check the file people will receive.

Original explanations and examples informed by these references. This guide supports practical checks; it does not replace a complete accessibility evaluation.