PDF Accessibility Checklist
Checking PDFs for accessibility helps ensure content works for everyone, including users of assistive technologies. Automated checkers can identify some common issues, but manual review is also required for full WCAG 2.1 Level AA compliance. This page outlines recommended tools and key steps for evaluating PDF accessibility.
Important: If accessibility issues are found, fix them in the original source document (such as Word or PowerPoint) and then recreate the PDF. Avoid editing accessibility issues directly in the PDF whenever possible.
Step 1: Start with an Automated Accessibility Checker
Automated checkers provide a good first review and help identify common problems quickly. Important: Automated checkers are only capable of catching around 30% of accessibility errors. Continue to step 2 for information on performing manual checks.
Adobe Acrobat Pro
Adobe Acrobat Pro includes a built‑in accessibility checker.
- Open your PDF in Adobe Acrobat Pro
- Go to Tools → Prepare for Accessibility
- Select Check for Accessibility
- Review the results panel for errors and warnings
Note: Logical reading order and color contrast always require manual review and will appear in the report even if no specific errors are found.
PAC PDF Accessibility Checker (Windows Only)
PAC is a free tool that checks PDFs against PDF/UA and WCAG 2.1 standards.
- Download and open PAC PDF Accessibility Checker
- Click Open Document or drag and drop your PDF into the tool
- Wait for the check to complete
- Review the summary results
- Select Report in Detail to see full findings
Results are grouped by:
- PDF/UA
- WCAG
- Quality
Note: PAC is only available for Windows
Step 2: Perform Manual Checks in Adobe Acrobat Pro
Automated tools cannot detect all accessibility issues. Manual checks are required to ensure the document is fully accessible.
Document Title
Each PDF must have a clear, descriptive title (not just a file name).
- Go to File → Document Properties
- Ensure there is a meaningful title in the Title field

Accessibility Tags
Accessibility tags help screen readers understand the structure of the document (such as headings, lists, tables, and images).
To open the Accessibility Tags panel:
- Right‑click on the right‑hand toolbar in Acrobat Pro
- Select Accessibility Tags
Check that:
- Headings are tagged as headings (not paragraphs), and heading levels follow a proper order
- Tables use the correct structure:
- Header cells are tagged as
<TH> - Data cells are tagged as
<TD>
- Header cells are tagged as
- Empty paragraph tags are not used for spacing
- If a list, paragraph, or table spans multiple pages, it should use one continuous tag rather than separate tags on each page
Lists should include:
<L>for the list<LI>for each list item<Lbl>for bullets or numbers (may not always be present)<LBody>for list content
Links should include:
- A
<Link>tag - A
<Link-OBJR>(object reference) - Clear, descriptive link text

Link Text
Links should clearly describe their destination.
- Avoid vague text like “click here,” “learn more,” or raw URLs
- Use meaningful descriptions that make sense out of context
Images
Images must include alternative text (alt text) if they convey information.
- Confirm alt text clearly describes the image’s purpose
- Decorative images should be marked as artifacts (not tagged)
To view alt text:
- Open the Accessibility Tags panel
- Right‑click the image’s
<Figure>tag - Select Properties

Reading Order
Content must be read in a logical, visual order by screen readers.
To check reading order:
- Right‑click on the right‑hand toolbar
- Select Order
- Review the numbered elements on each page to ensure they match the visual layout

Color & Contrast
Text must have enough contrast against its background to be readable.
- Verify sufficient contrast between text and background (including images).
- Use tools like Colour Contrast Analyzer (free download – available in Company Portal for Windows 11 users).
- All color combinations must meet WCAG 2.1 Level AA contrast requirements.

Printable Forms
- Do not use underscores or dashes to create fill‑in lines
- Use line shapes (marked as decorative) or tabs with underlined text formatting instead
Text Formatting (Best Practice)
Avoid underlining text that is not a link, as it can confuse users.