The key to an easier accessible PDF: Create an accessible source document.

The “source document” is the software you used to convert the document to PDF. (LIke Microsoft Word or Adobe InDesign)

Steps for an Accessible PDF Document

  1. Review the  various source document accessibility checklists to make your source documents accessible. 
  2. When converting to PDF, do not use the FIle – Print feature of the document software.
  3. Referencing the PDF testing checklist, run it through either  Adobe Acrobat Professional Accessibility Checker or the  free PDF Accessibility Checker (PAC) 2024 checker and remove all errors.

Frequently Asked Questions Related to Document Accessibility and Testing

What Version of WCAG can Adobe Acrobat Professional test?

Adobe Acrobat Professional: Web Content Accessibility Guidelines (WCAG) 2.0

If the state conforms to WCAG 2.2, and Adobe and PAC 2024 can’t check up to WCAG 2.2, does that matter?

No, the relevant document guidelines that were added in WCAG versions 2.1 and 2.2 are manual checks. The automated tools can’t check for them anyway.

Does every WCAG 2.2 Standard apply to documents?

No, see the data below for a list of 19 guidelines which apply to documents.

There is a PDF standard called PDF/UA. Does the state have to comply with PDF/UA?

No, the state does not require compliance with PDF/UA. The state complies with a specific set of WCAG guidelines for documents. See below.

WCAG That Specifically Applies to PDF Documents

What WCAG Guidelines Apply to Documents/PDF?
Which Guidelines Can be Automatically Tested in Adobe Acrobat Professional?
Which Guidelines Can Be Automatically Tested in PAC 2024?
WCAG 1.1.1 (Non-text Content)
Can test WCAG 1.1.1
(Checks that it is present, but not for accuracy)
Can test WCAG 1.1.1
(Checks that it is present, but not for accuracy)
WCAG 1.3.1 (Info & Relationships)
Can test WCAG 1.3.1
Can test WCAG 1.3.1
WCAG 1.3.2 (Meaningful Sequence)
Can test WCAG 1.3.2
Can test WCAG 1.3.2
WCAG 1.4.1 (Use of Color)
(Visual test)
(Visual test)
WCAG 1.4.3 (Contrast-Minimum)
Can test WCAG 1.4.3
Can test WCAG 1.4.3
WCAG 1.4.5 (Images of Text)
(Visual test)
(Visual test)
WCAG 1.4.11 (Non-Text Contrast)
(Manual test with color contrast checker)
(Manual test with color contrast checker)
WCAG 2.4.1 (Bypass Blocks)
Can test WCAG 2.4.1
(Bookmark failure if document is more than 20 pages)
(Manual test of checking document length)
WCAG 2.4.2 (Page Titled)
Can test WCAG 2.4.2
Can test WCAG 2.4.2
WCAG 2.4.3 (Focus Order)
(Manual test of checking order in tag tree)
Can test WCAG 2.4.3
WCAG 2.4.4 (Link Purpose - In Context)
(Visual test)
(Visual test)
WCAG 2.4.5 (Multiple Ways)
Can test WCAG 2.4.5
(Bookmark failure if document is more than 20 pages)
(Visual test of checking document length)
WCAG 2.4.6 (Headings & Labels)
(Visual test)
(Visual test)
WCAG 3.1.1 (Language of Page)
Can test WCAG 3.1.1
Can test WCAG 3.1.1
WCAG 3.1.2 (Language of Parts)
Can test WCAG 3.1.2
Can test WCAG 3.1.2
WCAG 3.2.2 (On Input)
(Manual test - PDF form)
(Manual test - PDF form)
WCAG 3.3.1 (Error Identification)
(Manual test - PDF form)
(Manual test - PDF form)
WCAG 3.3.3 (Error Suggestion)
(Manual test - PDF form)
(Manual test - PDF form)
WCAG 4.1.2 (Name, Role, Value)
(Manual test)
(Manual test)

Need the ability to do more advanced PDF accessibility remediation for complex PDF documents?

A few examples include:

  • Documents with a more complex design (like newsletters, brochures or data visualizations)
  • Documents which combine multiple files from many different formats (like Annual Reports or large meeting agendas)
  • Scanned documents where there is no source document and need to be converted to text

TRAINING: Visit the LinkedIn Learning “Advanced Accessible PDF” Course or Missouri Assistive Technology’s YouTube Videos, “PDFs Simply Made” and “Advanced PDF Accessibility”.

Have a resource for ICT Accessibility to share with us?