Operation Manual

383
Accessibility, tags, and reflow
Last updated 4/7/2015
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)
Navigation 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 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