The purpose of each link can be determined from the link text alone or from the link text together with its programmatically determined link context. (Level A)
The purpose of a link should be clear and easy to understand for all users. Whenever possible, the link text should describe its purpose without needing additional context.
Some assistive technologies provide a list of all links on the page. If the link names do not clearly give the purpose, or if multiple links with the same name point to different targets (e.g., “read more”), users are forced to locate the link on the page and search surrounding information for context.
When it is not possible to provide descriptive link text, the content that provides the context must be in the same sentence or be associated with the link programmatically. Ideally, this descriptive content should precede the link, so that users who read content sequentially encounter the link context before the link.
Exception: An exception to the above requirements is granted in cases where the purpose of a link would be ambiguous to users in general. For example, a game may create suspense for all users by presenting links with no indication of what the links will do until activated. However, whatever context is available must be programmatically associated with the link.
Note: In software, a “link” is any non-UI-control text string or image that behaves like a hypertext link. From Guidance on Applying WCAG 2.0 to Non-Web Information and Communications Technologies.
Refer to Understanding SC 2.4.4 for more information (external link to WCAG).
This paragraph appears generically in all checkpoints. Review the General techniques as well as other tabs applicable to your technology. Prioritize the use of technology-specific techniques, and implement the General techniques as needed. You are always required to find, understand and implement accessible code techniques to meet the checkpoint. The documented techniques and supplements are not exhaustive; they illustrate acceptable ways to achieve the spirit of the checkpoint. If numbered, techniques are in order of preference, with recommended techniques listed first. Where used, IBM information that complements the WCAG techniques is indicated as supplemental.
Instructions: Any item in this section represents a technique deemed sufficient. Techniques are ordered from most to least preferred. The first technique should be used when possible. Ensure you review WCAG Common Failures to avoid development mistakes.
- G91: Providing link text that describes the purpose of a link
- G53: Identifying the purpose of a link using link text combined with the text of the enclosing sentence
- G189: Providing a control near the beginning of the Web page that changes the link text allowing the user to choose short or long link text
The following techniques, examples and comments provide additional information beyond that available in the WCAG techniques.
Identifying the purpose of a link using link text combined with programmatically determined link context
When the link text alone is insufficient to provide proper context, additional information can be programmatically determined from relationships with a link, which when combined with the link text, will offer context. For example, in HTML information that is programmatically determined link context includes text that is in the same paragraph, list, or table cell.
Instructions: Any item in this section represents a technique deemed sufficient. Techniques are grouped from most to least recommended.
- Meeting the requirements of General technique G91 with the following preferred technique:
- Using link text combined with programmatically determined link context:
- ARIA7: Using aria-labelledby for link purpose
- H77: Identifying the purpose of a link using link text combined with its enclosing list item
- H78: Identifying the purpose of a link using link text combined with its enclosing paragraph
- H79: Identifying the purpose of a link using link text combined with its enclosing table cell and associated table headings
- H81: Identifying the purpose of a link in a nested list using link text combined with the parent list item under which the list is nested
- Meeting General technique G189 with the following:
- Providing a supplemental description of the purpose of a link using one of the following techniques:
In addition to the General techniques, use the link accessibility trait in your application.
There are no specific Eclipse techniques for this checkpoint. Refer to the General techniques section.
There are no specific Windows-based (MSAA+IA2) techniques for this checkpoint. Refer to the General techniques section.
Many links in this checklist reside outside ibm.com at the Web Content Accessibility Guidelines (WCAG) 2.1. W3C Recommendation 05 June 2018: http://www.w3.org/TR/WCAG21/
Copyright © 1994-2019 World Wide Web Consortium, (Massachusetts Institute of Technology, European Research Consortium for Informatics and Mathematics, Keio University, Beihang University). All Rights Reserved.
Copyright © 2001, 2019 IBM Corporation