Addressing Acrobat Accessibility Issues

Documents

Prevent security settings from interfering with screen readers

A document author can specify that no part of an accessible PDF is to be copied, printed, extracted, commented on, or edited. This setting could interfere with a screen reader’s ability to read the document, because screen readers must be able to copy or extract the document’s text to convert it to speech.

This flag reports whether it’s necessary to turn on the security settings that allow accessibility.

To fix the rule automatically, select Accessibility Permission Flag on the Accessibility Checker panel. Then, choose Fix from the Options menu.

Or, fix accessibility permissions manually:

Choose File > Properties > Security.
Choose No Security from the Security Method drop-down list.
Click OK and close the Document Properties dialog box.

If your assistive technology product is registered with Adobe as a Trusted Agent, you can read PDFs that might be inaccessible to another assistive technology product. Acrobat recognizes when a screen reader or other product is a Trusted Agent and overrides security settings that would typically limit access to the content for accessibility purposes. However, the security settings remain in effect for all other purposes, such as to prevent printing, copying, extracting, commenting, or editing text.

Note:
See the related WCAG section: 1.1.1 Non-text Content. (A), 4.1.2 Name, role, value

Image-only PDF

Reports whether 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.

To fix this rule check automatically, select Image-only PDF on the Accessibility Checker panel, and choose Fix from the Options menu.

Or, to fix this rule check manually, use OCR to recognize text in scanned images:

Choose Tools > Enhance Scans.
The Enhance Scans toolset is displayed in the secondary toolbar.
In the secondary toolbar, choose Recognize Text > In This File.
Select the pages you want to process, the document language, and then click Recognize Text.

Note:
See the related WCAG section: 1.1.1. Non-text content (A)

Tagged PDF

If this rule check fails, the document isn’t tagged to specify the correct reading order.

To fix this item automatically, select Tagged PDF on the Accessibility Checker panel, and then choose Fix from the Options menu. Acrobat automatically adds tags to the PDF.

To specify tags manually, do one of the following:

Enable tagging in the application in which the PDF was authored, and re-create the PDF.
Choose Tools > Accessibility > Autotag Document in Acrobat. The Add Tags Report appears in the navigation pane if there are any issues. The report lists potential problems by page, provides a navigational link to each problem, and provides suggestions for fixing them.
Choose Tools > Accessibility > Reading Order in Acrobat, and create the tags tree. For more information, see Reading Order tool overview.
Open the Tags panel and create the tags tree manually. To display the Tags panel, choose View > Show/Hide > Navigation Panes > Tags. For more information, see Edit document structure with the Content and Tags panel.

Note:
See the related WCAG section: 1.3.1 Info and Relationships, 1.3.2, 2.4.1, 2.4.4, 2.4.5, 2.4.6, 3.1.2, 3.3.2, 4.1.2 Name, role, value

Logical reading order

Verify this rule check manually. Make sure that the reading order displayed in the Tags panel coincides with the logical reading order of the document.

Document 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. If the check fails, set the language.

To set the language automatically, select Primary Language in the Accessibility Checker tab, and then choose Fix from the Options menu. Choose a language in the Set Reading Language dialog box, and then click OK.

To set the language manually, do one of the following:

Choose File > Properties > Advanced and then select a language from the drop-down list in the Reading Options section. (If the language doesn’t appear in the drop-down list, you can enter the ISO 639 code for the language in the Language field.) This setting applies the primary language for the entire PDF.
Set the language for all text in a subtree of the tags tree. Open the Tags panel. Expand the Tags root and select an element. Then choose Properties from the Options menu. Choose a language from the Language drop-down list. (To display the Tags panel, choose View > Show/Hide > Navigation Panes > Tags.)
Set the language for a block of text by selecting the text element or container element in the Content panel. Then, right-click (Windows) or Ctrl-click (Mac OS) the text and choose Properties from the context menu and choose a language from the Language drop-down list. (To display the Content panel, choose View > Show/Hide > Navigation Panes > Content.)

Note:
See the related WCAG section: Language of Page (Level A)

Title

Reports whether there is a title in the Acrobat application title bar.

To fix the title automatically, select Title in the Accessibility Checker tab, and choose Fix from the Options menu. Enter the document title in the Description dialog box (deselect Leave As Is, if necessary).

Or, fix the title manually:

Choose File > Properties > Description.
Enter a title in the Title text box.
Click Initial View, and then choose Document Title from the Show drop-down list.
Click OK to close the Description dialog box.

Note:
See the related WCAG section: 2.4 Page Titled (Level A)

Bookmarks

This check fails when the document has 21 or more pages, but doesn’t have bookmarks that parallel the document structure.

To add bookmarks to the document, select Bookmarks on the Accessibility Checker panel, and choose Fix from the Options menu. In the Structure Elements dialog box, select the elements that you want to use as bookmarks, and click OK. (You can also access the Structure Elements dialog box by clicking the Options menu on the Bookmark tab and selecting the New Bookmarks From Structure command.)

Note:
See the related WCAG sections: 2.4.1 Bypass Blocks (Level A), 2.4.5 Multiple Ways (Level AA)

Color contrast

When this check fails, it’s possible that the document contains content that isn’t accessible to people who are color-blind.

To fix this issue, make sure that the document’s content adheres to the guidelines outlined in WCAG section 1.4.3. Or, include a recommendation that the PDF viewer use high-contrast colors:

Choose Edit > Preferences (Windows) or Acrobat > Preferences (Mac OS).
Click Accessibility.
Select Replace Document Colors, and then select Use High-Contrast Colors. Choose the color combination that you want from the drop-down list, and then click OK.

Page content

Tagged content

This check reports whether all content in the document is tagged. Make sure that all content in the document is either included in the Tags tree, or marked as an artifact.

Do one of the following to fix this rule check:

Open the Content panel and right-click (Windows) or Ctrl-click (Mac OS) the content that you want to mark as an artifact. Then, select Create Artifact from the context menu. (To display the Content tab, choose View > Show/Hide > Navigation Panes > Content.)
Tag the content by choosing Tools > Accessibility > Reading Order. Select the content, and then apply tags as necessary.
Assign tags using the Tags panel. Right-click (Windows) or Ctrl-click (Mac OS) the element in the Tags tree, and choose Create Tag From Selection. Items such as comments, links, and annotations don’t always appear in the Tags tree. To find these items, choose Find from the Options menu. (To display the Tags panel, choose View > Show/Hide > Navigation Panes > Tags.)

Note:
See the related WCAG sections: 1.1.1 Non-text content (A), 1.3.1 Info and Relationships (Level A), 1.3.2 Meaningful Sequence (Level A), 2.4.4 Link Purpose (In Context) (Level A), 3.1.2 Language of Parts (Level AA), 4.1.2 Name, role, value

Tagged annotations

This rule checks whether all annotations are tagged. Make sure that annotations such as comments and editorial marks (such as insert and highlight) are either included in the Tags tree or marked as artifacts.

Open the Content panel, and right-click (Windows) or Ctrl-click (Mac OS) the content that you want to mark as an artifact. Then, select Create Artifact from the context menu. (To display the Content panel, choose View > Show/Hide > Navigation Panes > Content.)
Tag the content by choosing Tools > Accessibility > Reading Order. Select the content, and then apply tags as necessary.
Assign tags using the Tags panel. (To display the Tags panel, choose View > Show/Hide > Navigation Panes > Tags.)

To have Acrobat assign tags automatically to annotations as they’re created, choose Tag Annotations from the Options menu on the Tags panel.

Note:
See the related WCAG section: 1.3.1 Info and Relationships (Level A), 4.1.2 Name, role, value

Tab order

Because tabs are often used to navigate a PDF, it’s necessary that the tab order parallels the document structure.

To fix the tab order automatically, select Tab Order on the Accessibility Checker panel, and choose Fix from the Options menu.

To manually fix the tab order for links, form fields, comments, and other annotations:

Click the Page Thumbnails panel on the navigation pane.
Click a page thumbnail, and then choose Page Properties from the Options menu.
In the Page Properties dialog box, choose Tab Order. Then, select Use Document Structure, and click OK.
Repeat these steps for all thumbnails in the document.

Note:
See the related WCAG section: 2.4.3, Focus Order (Level A)

Character encoding

Specifying the encoding helps PDF viewers’ present users with readable text. However, some character-encoding issues aren’t repairable within Acrobat.

To ensure proper encoding, do the following:

Verify that the necessary fonts are installed on your system.
Use a different font (preferably OpenType) in the original document, and then re-create the PDF.
Re-create the PDF file with a newer version of Acrobat Distiller.
Use the latest Adobe Postscript driver to create the PostScript file, and then re-create the PDF.

Note:
The WCAG doesn’t address Unicode character mapping.

Tagged multimedia

This rule checks whether all multimedia objects are tagged. Make sure that content is either included in the Tags tree or marked as an artifact.

Open the Content panel and right-click (Windows) or Ctrl-click (Mac OS) the content that you want to mark as an artifact. Then, select Create Artifact from the context menu. (To display the Content panel, choose View > Show/Hide > Navigation Panes > Content.)

Tag the content by choosing Tools > Accessibility > Reading Order. Select the content, and then apply tags as necessary.

Assign tags using the Tags panel. Right-click (Windows) or Ctrl-click (Mac OS) the element in the Tags tree, and choose Create Tag From Selection. (To display the Tags panel, choose View > Show/Hide > Navigation Panes > Tags.)

Note:
See the related WCAG sections: 1.1.1 Non-text Content. (A), 1.2.1 Audio- only and Video- only (Prerecorded). (A), 1.2.2 Captions (Prerecorded). (A), 1.2.3 Audio Description or Media Alternative (Prerecorded). (A), 1.2.5 Audio Description (Prerecorded). (AA)

Screen flicker

Elements that make the screen flicker, such as animations and scripts, can cause seizures in individuals who have photosensitive epilepsy. These elements can also be difficult to see when the screen is magnified.

If the Screen Flicker rule fails, manually remove or modify the script or content that causes screen flicker.

Note:
See these related WCAG sections: 1.1.1 Non-text Content. (A), 1.2.1 Audio- only and Video- only (Prerecorded). (A), 1.2.2 Captions (Prerecorded). (A), 1.2.3 Audio Description or Media Alternative (Prerecorded). (A), 2.3.1 Three Flashes or Below Threshold. (Level A)

Scripts

Content cannot be script-dependent unless both content and functionality are accessible to assistive technologies. Make sure that scripting doesn’t interfere with keyboard navigation or prevent the use of any input device.

Check the scripts manually. Remove or modify any script or content that compromises accessibility.

Note:
See these related WCAG sections: 1.1.1 Non-text Content. (A), 2.2.2 Pause, Stop, Hide. (Level A), 4.1.2 Name, role, value

Timed responses

This rule check applies to documents that contain forms with JavaScript. If the rule check fails, make sure that the page does not require timed responses. Edit or remove scripts that impose timely user response so that users have enough time to read and use the content.

Note:
See the related WCAG section: 2.2.1 Timing Adjustable. (Level A)

Accessible links

For URLs to be accessible to screen readers, they must be active links that are correctly tagged in the PDF. (The best way to create accessible links is with the Create Link command, which adds all three links that screen readers require to recognize a link.) Make sure that navigation links are not repetitive and that there is a way for users to skip over repetitive links.

If this rule check fails, check navigation links manually and verify that the content does not have too many identical links. Also, provide a way for users to skip over items that appear multiple times. For example, if the same links appear on each page of the document, also include a “Skip navigation” link.

Note:
See the related WCAG section: 2.4.1 Bypass Blocks. (Level A)

Forms

Tagged form fields

In an accessible PDF, all form fields are tagged and are a part of the document structure. In addition, you can use the tool tip form filed property to provide the user with information or to provide instructions.

To tag form fields, choose Tools > Accessibility > Autotag Form Fields.

Note:
See the related WCAG sections: 1.3.1 Info and Relationships. (Level A), 4.1.2 Name, role, value

Field descriptions

For accessibility, all form fields need a text description (tool tip).

To add a text description to a form field:

Select one of the Form tools, and then right-click (Windows) or Ctrl-click (Mac OS) the form field.
Choose Properties from the context menu.
Click the General properties tab.
Enter a description of the form field in the Tooltip field.

Note:
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

Alternate text

Figures alternate text

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:

Select Figures Alternate Text in the Accessibility Checker panel, and choose Fix from the Options menu. Add alternate text as prompted in the Set Alternate Text dialog box.
Use the Tags panel to add alternate text for images in the PDF.
Open the Content panel and right-click (Windows) or Ctrl-click (Mac OS) the content that you want to mark as an artifact. Then, select Create Artifact from the context menu. (To display the Content panel, choose View > Show/Hide > Navigation Panes > Content.)

Note:
See the related WCAG section: 1.1.1 Non-text Content. (A)

Nested alternate text

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:

Choose View > Show/Hide > Navigation Panes > Tags.
Right-click (Windows) or Ctrl-click (Mac OS) a nested element in the Tags panel and choose Properties from the context menu.
Remove both the Alternate Text and the text to which it’s applied from the Object Properties dialog box, and then click Close.

Note:
See the related WCAG section: #1.1.1 Non-text Content. (A)

Associated with content

Make sure that alternate text is always an alternate representation for 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.

Right-click (Windows) or Ctrl-click (Mac OS) an item to check.
Open it in the Tags panel. (To display the Tags panel, choose View > Show/Hide > Navigation Panes > Tags.)
Remove the Alternate Text from the Tags panel for any nested item that has no page content.

Note:
See the related WCAG section: 1.1.1 Non-text Content. (A)

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.

To remove alternate text from nested elements:

Choose View > Show/Hide > Navigation Panes > Tags.
Right-click (Windows) or Ctrl-click (Mac OS) a nested element in the Tags panel and choose Properties from the context menu.
Remove the alternate text from the Object Properties dialog box, and then click OK.

Note:
See the related WCAG sections: 1.3.1 Info and Relationships. (Level A), 4.1.2 Name, role, value

Other elements alternate text

This report checks for content, other than figures, that requires alternate text (such as multimedia, annotation, or 3D model). Make sure that alternate text is always an alternate representation for 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.

Choose View > Show/Hide > Navigation Panes > Tags.
Right-click (Windows) or Ctrl-click (Mac OS) a nested element in the Tags panel and choose Properties from the context menu.
Remove the alternate text from the Object Properties dialog box, and then click OK.

Note:
See the related WCAG section: 1.1.1 Non-text Content. (A)

Tables

Because table structure can be complex, it is best practice to check them for accessibility manually.

Rows

This rule checks whether each TR in a table is a child of Table, THead, TBody, or TFoot.

See Correct table tags with the Tags panel.

Note:
Related WCAG section: 1.3.1 Info and Relationships. (Level A)

TH and TD

In a proper table structure, TH and TD are children of TR.

See Correct table tags with the Tags panel.

Note:
See related WCAG section: #1.3.1 Info and Relationships. (Level A)