• Media Type Adobe Acrobat PDF > Links
  • State Active
  • Advisory No

It is important that links are tagged properly as links in order for the link to be keyboard accessible and to be indicated as actionable with a role of 'link' to users of assistive technology.

Compliant Example

// pseudo-code //
<Link>
  <Link OBJR />
  www.adobe.com
</Link>

Non-Compliant Example

// pseudo-code //
<Link>
  www.adobe.com
</Link>

With Acrobat 8 Use the Create Link Command

  1. Select the text or object for which you want to create a link.
  2. Right-click (Windows) or Control-click (Mac OS) the selection, and choose Create Link from the context menu.
  3. In the Create Link dialog box, select the appropriate options, and then follow the on-screen instructions to specify a URL, page view, or file as the link target.

By default, the selected text for each link becomes the link text. After you add all the links, you can edit the tag tree to add alternative text to the links, further improving the accessibility of the PDF.

Acrobat 7 and prior

Use the link tool to create a link if the link currently does not exist. Use the tags tree to make the link accessible.

  1. Open the tags tree
  2. Activate Options > Find
  3. Choose "unmarked links" from the find drop down list
  4. Activate the next button
  5. Activate the tag button
  6. Verify that the (Link OBJR) child tag was inserted in the correct location within the tag tree
  7. Verify that the parent of the (Link OBJR) tag is a (Link) tag, if it is not create a (Link) tag as its parent and ensure the visible link text is a sibling of the (Link OBJR) tag.

Organization Standards

  • § 508-1194.22 Web Sites and Applications
    • (l) Ensure scripts are accessible
  • Section 508 and 255 (Revised 2017)
    • Chapter 3: Functional Performance Criteria
      • 302.2 With Limited Vision
      • 302.1 Without Vision
      • 302.7 With Limited Manipulation
      • 302.8 With Limited Reach and Strength
  • WCAG 2.0 Level A
    • 2.1.1 Keyboard Accessibility
    • 4.1.2 Name, Role, Value
  • WCAG 2.1 Level A
    • 2.1.1 Keyboard
    • 4.1.2 Name, Role, Value

Other Mapped Standards

  • § 508-1194.21 Software Applications and Operating Systems
    • (d) Information about a user interface element must be textually available
  • § 508-1194.31 Functional performance criteria
    • (a) Ensure access for blind and visually impaired
    • (b) Ensure access for low vision users
    • (f) Ensure users with mobility impairments can use application
  • BITV 2.0 (Priority I)
    • 2.1.1 Tastaturbedienbarkeit
    • 4.1.2 Name, Rolle, Wert
  • HHS PDF 508 Checklist
    • Basic Elements
      • (10) Are all URL’s linked to the correct Web destinations?
    • 1.0 Document Layout and Formatting Requirements
      • (11) Have Acrobat Accessibility Tags been added to the document?
  • HHS PDF 508 Checklist (2014)
    • 1.0 Master Requirements for All Documents
      • (1.8) Do all URLs contain descriptive hyperlinks (i.e., avoid generic phrases like “Click here” and, instead, use phrases that let users know about the content of the linked page prior to selecting it)?
      • (1.9) Are all URLs linked to correct Web destinations?
      • (1.10) Are all internal links/TOC entries functioning correctly (if linked)?
      • (1.11) Are links (including e-mail addresses) keyboard accessible?
    • 3.0 Accessibility Tagging and Reading Order
      • (3.1) Have PDF tags been added to the document?
  • WCAG 2.2 Level A
    • 2.1.1 Keyboard
    • 4.1.2 Name, Role, Value

  • Severity

    8 (red)
    in range of 1 to 10

  • Noticeability

    6 ()
    in range of 1 to 10

  • Tractability

    5 ()
    in range of 1 to 10