PDF accessibility checklist: 15 checks before publishing

What this checklist can and cannot prove

This checklist is a release gate, not a legal certification. It helps a reviewer find the structural failures that most often prevent keyboard and assistive-technology users from understanding a PDF. Apply the specific standard and procurement requirements that govern your organization.

The checks align with established guidance from Section508.gov and W3C's WCAG2ICT. W3C also publishes PDF techniques, such as correct reading and tab order, as examples of ways to satisfy WCAG success criteria.

The 15-point PDF accessibility checklist

1. 01. The PDF contains real text. Confirm text can be selected and copied in a meaningful order. Image-only scans need OCR and manual review before structural remediation.
2. 02. The document is tagged. Open the tag tree and verify that visible content is represented. A document can report that it is tagged while still having an unusable structure.
3. 03. The title and language are set. Use a descriptive document title, show it in the initial view, and set the primary language so assistive technology uses the correct pronunciation rules.
4. 04. Headings form a logical outline. Use heading tags for actual sections, not for visual emphasis. Avoid skipping levels when the content structure does not justify it.
5. 05. Reading order follows meaning. Check columns, sidebars, captions, footnotes, and repeated headers. The tag order should make sense without relying on page position.
6. 06. Lists are represented as lists. List labels and list items need the correct relationships so a screen reader can announce the list and its item count.
7. 07. Tables expose their relationships. Identify header cells and their scope. Test merged cells, multi-level headers, and tables that continue across pages.
8. 08. Images have appropriate alternatives. Write concise alt text for informative images, provide longer explanations for complex graphics, and mark decorative images as artifacts.
9. 09. Links describe their destination. Replace repeated text such as 'click here' with meaningful link purpose, and verify that annotations are included in the tag structure.
10. 10. Forms work without a mouse. Every control needs a programmatic name, logical tab order, clear instructions, accessible errors, and the correct control type.
11. 11. Decorative page content is artifacted. Running headers, footers, page numbers, background shapes, and visual separators should not interrupt the reading sequence.
12. 12. Color is not the only signal. Instructions, charts, errors, and status information must remain understandable without color perception. Check text and meaningful graphic contrast.
13. 13. Security permits accessibility. Confirm document permissions do not block text access for assistive technology and that protected workflows remain usable.
14. 14. Automated validators are reviewed, not obeyed blindly. Use PAC, Acrobat, veraPDF, or another agreed tool, then investigate each result. A passing automated report is not a complete user test.
15. 15. A person tests a representative task. Navigate headings, links, tables, and forms with a keyboard and screen reader. Confirm the content is understandable, not merely present in the tag tree.

A fast triage sequence

When time is limited, do not start by repairing individual tags. Determine whether the document belongs in the PDF path at all.

1. Can the content become HTML? Frequently updated reading material usually becomes easier to navigate and maintain as a semantic web page.
2. Can the layout adapt? If yes, the automated workflow can produce hosted HTML and a rebuilt tagged PDF for review.
3. Must the original PDF stay visually identical? Send forms, signed records, fixed packets, and layout-critical reports to manual remediation.
4. Does the file contain sensitive information? Use only approved systems and contracts. Test with a sanitized sample when the workflow has not been cleared for the real data.

Automated checks versus manual checks

What to keep as evidence

• The source document and the exact published version.
• The validator name, version, profile, and dated result.
• The manual test steps, reviewer, findings, and corrections.
• Known limitations and the route for requesting an alternative.
• The content owner and next review date.

Run the first check now

The free PDF checker provides an initial structural score and issue list. Use it to triage the file, then apply the manual checks above before making a conformance claim. If PDF/UA and WCAG terminology is causing confusion, read PDF/UA versus WCAG.