This page is meant to serve as a guide for PDF/UA compliance. It will cover important workarounds and key concepts to ensure PDF / UA status in all of your PDF files. To be clear, there is some overlap with posts found on How do I make my PDF Accessible section of this website. This is also different from Section 508 compliance for PDFs.
PDF/UA, or PDF Universal Accessibility, is a standard that ensures PDF content is accessible for people with disabilities. It provides a set of rules and recommendations for creating accessible PDFs that can be read and understood by assistive technologies, such as screen readers, magnifiers, and read-aloud tools. The “UA” in PDF/UA stands for “Universal Accessibility”.
First things first. Download the PAC 2021 Checker
You don’t have to start with checking your file, but it can often give a good starting point.
What is PDF / UA Compliance?
PDF/UA was published by the International Organization for Standardization (ISO) as ISO 14289. The standard is based on the PDF Reference, specifically the features related to accessibility, and its goal is to provide guidelines for creating universally accessible PDF documents and forms.
The main focus areas of PDF/UA compliance are:
- Tagging and Reading Order: The PDF must be correctly tagged, meaning that every element (paragraph, heading, table, list, etc.) is correctly identified, and the reading order should be logical and intuitive.
- Hyperlinks: Make sure hyperlinks are formatted properly!
- Images and Figures: All non-text content like images should have alternate text descriptions (Alt text). These descriptions should be brief but descriptive enough for users who can’t see the image to understand its content and purpose in the document.
- Tables: Tables should be correctly tagged to ensure the relationship between cells and headers is preserved, so that users of assistive technology can understand the information being presented.
- Form Fields: All interactive form fields should be accessible, with descriptive labels and instructions for users.
- Language: The document language should be specified, allowing assistive technology to correctly interpret and vocalize the text.
- Bookmarks: For longer documents, bookmarks should be used to help users navigate to specific sections of the document.
- Color and Contrast: Avoid using color alone to convey information and ensure there is sufficient contrast between the text and the background.
- Validate Your Document: Use an accessibility checker, such as the one built into Adobe Acrobat, to check your document for accessibility issues. Fix any issues that are identified.
- Get Expert Help: If you’re unsure about any part of the process, consult with an expert in PDF accessibility.
How to Achieve PDF/UA Compliance:
- Use the Right Tools: Begin with software that supports accessible PDF creation. Adobe Acrobat Pro, Microsoft Word, and Adobe InDesign have features that support PDF/UA creation.
- Structure Your Document: Use headings, lists, and other structure elements consistently and correctly.
Keep in mind that PDF/UA compliance is not a one-time task; it requires continuous attention. Whenever a PDF document is updated, it should be checked again to ensure it is still compliant with the PDF/UA standard. This can be a time-consuming process, but the end result is a document that is more accessible to all users, including those with disabilities.
PDF / UA Errors
This section will cover a myriad of accessibility errors that can occur from within the PDF Pac 2021 Checker under the PDF UA criteria. There will be some overlap with WCAG 2.1 standards.
- Path Object Not Tagged
- OCCD optional content configuration dictionary contains AS key
- Table header cell has no associated sub cells
More PDF / UA based posts:
Making a PDF Accessible: Episode 03| Moorpark Community College
Welcome to episode three on making college PDFs accessible. Today, we focus on Moorpark Community College’s website. We look at their course wellness document to improve its digital inclusivity. Video Guide In case you missed…
Making College PDFs Accessible: Episode 01 | Ventura Community College
Today, we’re exploring a key aspect of digital inclusivity – PDF accessibility. While reviewing Ventura Community College’s PDF, we identified areas of improvement. Let’s dive in! Video Guide In case you missed them, here are Episode…
How to Make Complex Tables Accessible in Adobe Acrobat Pro DC
This post will go over how to tag complex tables in Adobe Acrobat Pro DC. There is a dedicated section on this site on how to tag tables, but this is a bit of a…
Adobe Acrobat Auto Tagging API for Accessibility
Understanding Adobe Acrobat’s New Auto Tagging API for Accessibility Adobe Acrobat has added a new feature to its accessibility toolkit: the Auto Tagging API. This tool aids in making PDF documents more accessible. If you’re…
Making Accessible Presentations with Canva
This video and post will provide an overview of how to use Canva AI to create a presentation, export it to PDF, and then make it accessible. Utilizing Canva for Accessible Presentations Canva, a popular…
How to create a Doc in Canva and make it accessible
This post will go over how to create a doc in Canva.com and export it to PDF. Then, we will make it accessible! Overview Please follow the steps in the video on how to create…
Tackling the OCCD Key Error in PAC 2021 for PDF/UA Compliance
Welcome to your comprehensive guide for tackling the complex issue of PDF/UA compliance testing. Today, we will focus on a unique error you might encounter – the OCCD (Optional Content Configuration Dictionary) Key Error in…
Table Header Cell Has No Associated Sub Cells
Welcome to an in-depth exploration of a specific issue related to PDF/UA compliance testing, known as the ‘Table Header Cell Has No Associated Sub Cells’ error. This error often comes up when using the PAC…
Path Object not tagged | PDF / UA
Welcome to the world of document accessibility! Today, we’ll demystify a common issue that plagues many users – the ‘Path Object Not Tagged’ error – especially when working with Adobe Acrobat and files exported from…