Accessibility results - Page content

Advice on which issues can be solved automatically by clicking Fix is available in online Help. This also provides more guidance for manually resolving issues.

  • 2-1: Is all content tagged?

    See Tagged PDF and Tag panel.

  • 2-2: Are all annotations tagged?

    See Tagged PDF and Tag panel.

  • 2-3: Does the tab order reflect the logical page layout?

    Because tabs are often used to navigate in a PDF, the tab order on a page must parallel the document structure.

    Solution: On the Tab Order tab of the Page Properties dialog box, select the Use Document Structure option. See Define tab order for form fields within a page for details.

  • 2-4: Do the character codes obey norms?

    Specifying the character encoding helps PDF viewers present users with readable text. However, some character-encoding issues cannot be solved by the program.

    Solution: To ensure proper encoding, 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.

  • 2-5 Have all multimedia objects been tagged?

    This rule checks all multimedia objects for tagging.

    Solution: Make sure that multimedia objects are either included in the Tags tree or marked as an artifact. You can assign tags using the Tag panel. In the Tag panel, you can also change a tag to Artifact: select the element and select Change Tag to Artifact from its context menu.

  • 2-6 Do any objects cause screen flicker?

    Animations, scripts and other items may cause screen flicker; these can induce seizures in people suffering from certain types of epilepsy. These elements can also be difficult to see when the screen is magnified.

    Solution: manually remove or modify the script or content that is causing the screen to flicker.

  • 2-7: Does the page contain any scripts that cannot be accessed?

    Content is allowed to be script-dependent providing both content and functionality can be handled by accessibility aids. Typically this relates to behavior when buttons in forms clicked. Ensure that scripting does not hinder keyboard navigation or prevent the use of any input device.

    Solution: check the scripts manually. Remove or modify any script or content that compromises accessibility.

  • 2-8: Does the page require any 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.

    Solution: edit or remove scripts that impose timely user response so that people have enough time to read and use the content.

  • 2-9: Are multiple links to a single target avoided?

    For hyperlinks 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 the required information. If there are multiple links to a single destination, be sure there is a way for users of screen readers to skip over these repetitive links.

    Solution: 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, include a ‘Skip navigation’ link.

  • 2-10: Is the target size appropriate?

    The size of the target (or its equivalent, substitute target) for mouse, pen, or touch inputs should cover at least 44 by 44 CSS pixels, unless it is an inline (text) target.