WCAG 2.1 & Adobe PDF Creation & Remediation

PDFs are created and edited in a software publishing program, which means they are handled differently for ensuring accessibility standards are met than websites and web applications. This makes it challenging to determine which WCAG success criteria need to be applied to PDFs. This training has the information you need to understand when to create or fix PDFs to meet WCAG 2.1, Level A and Level AA requirements. 

What you can expect from this role’s training:  

  • Learn how WCAG 2.1 success criteria impact this role.
  • Find training resources related to each success criterion.
  • Access additional resources related to accessibility requirements.
  • Review frequently Asked Questions (FAQs).
Adobe PDF & WCAG 2.1 Role-based Training icon

Which WCAG 2.1 success criteria impact PDF creation & remediation?

Note: The following WCAG 2.1 success criteria (SC) do not currently apply to PDFs:

  • SC 1.3.4: Orientation.
  • SC 1.3.5: Identify Input Purpose.
  • SC 1.4.10: Reflow.
  •  SC 1.4.12: Text Spacing.
  • SC 1.4.13: Content on Hover or Focus.
  • SC 2.1.4: Character Key Shortcuts.
  • SC 2.5.4: Motion Actuation.

View the relevant SC section below for more details on each. As PDF software evolves, we will continue to assess each criterion's applicability.

IMPORTANT note for vendors/contractors: Because not all WCAG 2.1 criteria apply here, you must understand any other form of digital technology you create for the State of Minnesota must meet all WCAG 2.1, Level A and Level AA criteria when applicable. And what testing tools you need to use to validate. Refer to the state's Digital Accessibility Standards for more details.

Open each SC section below to review how it impacts this role:

Additional resources

MNIT Office of Accessibility

W3C

External

FAQs

Do I need an accessible source document? Or can I start with a source document that isn’t accessible and just make it accessible using Acrobat Pro? 

Starting with an accessible source document is best practice, as it makes creating an accessible PDF easier. Additionally, when you update the source document, you won’t need to fix the same issues in the PDF each time, saving you time and effort in the long run.

Do PDFs need to be accessible if they are not going onto our website? 

Yes. If the digital version is distributed or shared in any way, it must be fully accessible. This does not apply to paper copies. Documents should also include boilerplate language on how to contact the original source creator for an alternate version upon request (individual accommodation).

How do I test my PDF to make sure it’s accessible? 

There are several steps to follow below (keep in mind that some documents may require additional checks not covered here). 

For your standard PDFs check the following: 

Automated Checks 

Run the accessibility checker. Keep in mind that the automated checker cannot guarantee a fully accessible document. You must still perform manual checks. The automated tool can only verify the presence of content—it cannot assess the accuracy of that content.

Manual Checks 

  • Check the color contrast. If you have color contrast issues, fix the source document before moving forward.
  • Review the tag tree to check for missing, incorrect, out-of-order, or improperly structured tags. This is where you can address most accessibility issues. Make sure you have an H1 as the title.
  • Check the Document Properties. Make sure the H1 is the same as the Title and all other information is correct. 
  • Check the tab order of interactive elements (form fields, links, buttons, etc.).
  • Check your bookmarks (if it is a multi-page PDF).

I tested my PDF, and it works fine on my computer. How can I ensure it works on everyone’s device, including phones? 

We should make every effort to ensure PDFs are accessible. While we create our documents to meet WCAG 2.1, Level AA as applicable to PDFs, we cannot guarantee they will work for every user or device. If someone encounters accessibility issues with an otherwise accessible PDF due to their device or software, they should be able to request an alternate version from the content provider.

I work with InDesign - what do I need to know when creating a design that will export to a PDF? 

There are excellent resources on the Office of Accessibility's InDesign page