How to make a PDF accessible and easy for everyone to read

An accessible PDF can be read in a sensible order by a screen reader, navigated with a keyboard, searched, zoomed, and understood without relying only on color or pictures.

The easiest time to make it accessible is before it becomes a PDF.

Start with an accessible source document

In Word, Google Docs, Pages, PowerPoint, or your design tool:

• use real Heading 1, Heading 2, and Heading 3 styles
• use real lists instead of typed dashes
• add concise alt text to meaningful images
• mark decorative images as decorative where supported
• give links descriptive text
• create simple tables with header rows
• keep a logical reading order
• use strong color contrast
• do not use color as the only way to communicate meaning
• set the document language

Avoid using text boxes and tables to force the whole page layout. They can create a confusing reading order.

Export with tags

Use the app's Save as PDF or Export to PDF feature and enable document structure tags or accessibility options.

Printing to PDF may flatten or discard structure, links, bookmarks, and form behavior. It is a useful fallback, not the best accessible export path.

Do not publish image-only scans

If you scanned paper, run OCR so the text becomes searchable. Then check names, numbers, headings, columns, and tables. OCR alone does not create a fully accessible document, but an image with no recognized text is a major barrier.

Check tags and reading order

In an accessibility-capable PDF editor:

1. Run the accessibility checker.
2. Confirm the PDF is tagged.
3. Inspect heading levels.
4. Check the reading order page by page.
5. Add or correct alt text.
6. Check table headers and cells.
7. Give form fields useful labels and a logical tab order.
8. Confirm security settings do not block assistive technology.

Adobe's accessible PDF workflow recommends building accessibility into the source, tagging the PDF, evaluating it, and repairing issues. Automatic tagging helps, but complex layouts still need human review.

Test like a reader

Automated checks do not know whether an image description is useful or a reading order makes sense.

Try to:

• select and copy text in the expected order
• navigate links and form fields with the Tab key
• zoom to 200% or more
• reflow the page if your viewer supports it
• read link text out of context
• listen with a screen reader when accessibility is important

Offer an HTML version for public information

For policies, instructions, event details, and other web content, a well-built HTML page is usually more responsive, searchable, and adaptable than a PDF. Offer the PDF as a printable download, not the only door.

Label links clearly, for example:

Download the annual report (PDF, 3.2 MB, 42 pages)

Accessibility makes PDFs less frightening

Clear headings help everyone skim. Searchable text helps everyone find a name. Descriptive links reduce surprises. Good contrast helps in bright sunlight as well as with low vision.

Accessibility is not an extra coat of polish. It is the work that makes the document behave like information instead of a picture of information.