PDF Accessibility¶
Adobe Acrobat Pro comes with an accessibility checker that tests whether a PDF is accessible according to their standards.
Acrobat Pro Tests¶
PDF Accessibility Tests¶
Test |
Definition |
Not ADA Title 2 |
If not ADA Title 2, Why? |
If ADA Title 2, Why? |
---|---|---|---|---|
Title |
A title is in the title bar. |
WCAG 2.4.2 requires a descriptive title. |
||
Figures alternate text |
Images in the document either have alternate text or are marked as artifacts. |
WCAG 1.1.1 requires alt text for non-text content. |
||
Other elements alternate text |
Content other than figures have required alternate text (such as multimedia, annotation, or 3D model) |
Also part of WCAG 1.1.1. |
||
Image-only PDF |
The document contains non-text content that is not accessible. If the document appears to contain text, but doesn’t contain fonts, it could be an image-only PDF file. |
WCAG 1.1.1 requires a text alternative for all content. |
||
Tagged PDF |
Document is tagged to specify the correct reading order |
Needed for programmatic structure (1.3.1, 1.3.2). |
||
Tab order |
The tab order parallels the document structure. |
WCAG 2.4.3 requires logical navigation order. https://www.w3.org/WAI/WCAG22/Understanding/focus-order.html. |
||
Nested alternate text |
Screen readers don’t read the alternate text for nested elements. Therefore, don’t apply alternate text to nested elements. |
X |
PDF/UA-specific; WCAG only cares that alt text is present and meaningful. |
|
Associated with Context |
Make sure that alternate text is always an alternate representation of content on the page. If an element has alternate text but does not contain any page content, there is no way to determine which page it is on. If the Screen Reader Option in the Reading preferences is not set to read the entire document, then screen readers never read the alternate text. |
WCAG 1.1.1 requires alt text be correctly tied to the object. |
||
Hides annotation |
Alternate text can’t hide an annotation. If an annotation is nested under a parent element with alternate text, then screen readers don’t see it. |
X |
Only an issue for WCAG if it hides meaningful content from assistive tech. |
|
Rows |
This rule checks whether each TR in a table is a child of Table, THead, TBody, or TFoot. |
WCAG 1.3.1 requires table structure. |
||
TH and TD |
In a proper table structure, TH and TD are children of TR. |
WCAG 1.3.1 requires header and data cell association. |
||
Headers |
For accessibility, it’s necessary that all tables in the PDF have a header. |
Applies to both table headers (1.3.1) and document headings (2.4.6). |
||
Regularity |
To be accessible, tables must contain the same number of columns in each row, and rows in each column. |
X |
A PDF/UA check for consistent table column widths; WCAG doesn’t require this. |
|
List items |
The check reports whether each List Item (LI) is a child of List (L). When this rule check fails, the structure of this list is incorrect. Lists must have the following structure: A List element must contain List Item Elements. And, List Item Elements can only contain Label Elements and List Item Body Elements. |
WCAG 1.3.1 requires lists to be programmatically determined. |
||
Lbl and LBody |
Lists must have the following structure: A List element must contain List Item Elements. And, List Item Elements can only contain Label Elements and List Item Body Elements. When this rule check fails, the structure of this list is incorrect. |
Part of proper list semantics (1.3.1). |
||
Appropriate nesting |
This rule checks nested headings. When this check fails, headings are not nested properly. |
WCAG 1.3.1 requires correct hierarchy. |
||
Primary Language |
Setting the document language in a PDF enables some screen readers to switch to the appropriate language. This check determines whether the primary text language for the PDF is specified. |
WCAG 3.1.1 requires language to be specified. |
||
Bookmarks |
This check fails when the document has 21 or more pages, but doesn’t have bookmarks that parallel the document structure. |
X |
Helpful for navigation but not required by WCAG. |
|
Tagged Content |
This check reports whether all content in the document is tagged. Ensure that all content in the document is either included in the Tags tree, or marked as an artifact. |
WCAG 1.3.1 requires semantic structure. |
||
Tagged Annotations |
This rule checks whether all annotations are tagged. Ensure that annotations such as comments and editorial marks (insert and highlight) are either included in the Tags tree or marked as artifacts. |
WCAG 1.3.1 requires annotations be available to assistive tech. |
||
Character encoding |
Specifying the encoding helps PDF viewers’ present users with readable text. However, some character-encoding issues aren’t repairable within Acrobat. |
Needed so text can be programmatically determined and read correctly (affects 3.1.1, 4.1.2). |