Skip to main content

Unique and descriptive link text

Explanation

This is a plain language description of the guideline or criterion, probably based on Understanding WCAG or similar. It should include the authors' rationale for including the guideline. It should also include an explanation of how implementation benefits users. Include both users with disabilities as well as those who wouldn't identify that way. Reference/cross reference standards and include links when necessary. Define all abbreviations, technical terms or jargon used below in this section in context. Include link to longform definition in the Accessible ICT Terms and Definitions as well.

Demonstration

Screen

reader demonstration: Unique and descriptive link names (BAD)


Screen

reader
demonstration:

Explanation

Unique and descriptive link names (GOOD)

Techniques

Include techniques for fixing the problem. If it's general, just spell it out here. If it's application-specific, use Medium headings for each software type. Stick to groups as much as possible (Microsoft 365, Google Workspaces, on the Web) rather than individual software. If it's worth discussing a specific application feature, it's worth including a screenshot.

Where applicable, provide more than one option for addressing the issue. Try to include a range of effort levels. Reference/cross reference standards and include links when necessary.

Learn more

Include either a bulleted list of external links and resources (internal ones should be linked in context above) or Medium headings that include a description as well as the link. Links should have unique and descriptive names.

  • Hi! I'm a link.