In an accessible PDF, all form fields are tagged and part of the document structure. In addition, you can use the tool tip form field property to provide the user with information or instructions.
To tag form fields, choose All tools > Prepare for accessibility > Automatically tag PDF.
See the related WCAG sections: 1.3.1 Info and Relationships. (Level A), 4.1.2 Name, role, value
For accessibility, all form fields need a text description (tool tip).
To add a text description to a form field:
See the related WCAG sections: 1.3.1 Info and Relationships. (Level A), 3.3.2 Labels or Instructions (Level A), 4.1.2 Name, role, value
Make sure that images in the document either have alternate text or are marked as artifacts.
If this rule check fails, do one of the following:
See the related WCAG section: 1.1.1 Non-text Content. (A)
Screen readers don't read the alternate text for nested elements. Therefore, don't apply alternate text to nested elements.
To remove alternate text from nested elements, do the following:
See the related WCAG section: #1.1.1 Non-text Content. (A)
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.
See the related WCAG section: 1.1.1 Non-text Content. (A)
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.
To remove alternate text from nested elements:
See the related WCAG sections: 1.3.1 Info and Relationships. (Level A), 4.1.2 Name, role, value
This report checks for content other than figures that require alternate text (such as multimedia, annotation, or 3D model). 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 Options in the Reading preferences is not set to read the entire document, then screen readers don't read the alternate text.
See the related WCAG section: 1.1.1 Non-text Content. (A)
Because table structure can be complex, it is best practice to check them for accessibility manually.
This rule checks whether each TR in a table is a child of Table, THead, TBody, or TFoot.
Related WCAG section: 1.3.1 Info and Relationships. (Level A)
In a proper table structure, TH and TD are children of TR.
See related WCAG section: #1.3.1 Info and Relationships. (Level A)
For accessibility, it's necessary that all tables in the PDF have a header.
See the related WCAG section: 1.3.1 Info and Relationships. (Level A)
To be accessible, tables must contain the same number of columns in each row, and rows in each column.
See the related WCAG section: 1.3.1 Info and Relationships. (Level A)
Table summaries are optional, but can improve accessibility.
See the related WCAG section: 1.3.1 Info and Relationships. (Level A)
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.
To fix the list structure:
See the related WCAG section: 1.3.1 Info and Relationships. (Level A)
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.
To fix the list structure:
See the related WCAG section: 1.3.1 Info and Relationships. (Level A)
This rule checks nested headings. When this check fails, headings are not nested properly.
To fix the list structure:
See the related WCAG section: 2.4.6 Headings and Labels. (Level AA). The order of headings is not required under WCAG, and is only an advisory technique