Skip to main content
  1. All Posts/

Links and Buttons – Accessibility Guidelines

Accessibility GSA Section 508
Table of Contents

Link Purpose (In Context) #

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, except where the purpose of the link would be ambiguous to users in general.

Best Practice: Although the requirement allows for it, avoid vague link text like “click here” and “read more”. Avoid using the same link text for links that have different destinations.

This requirement covers both links and buttons.

Content/Design Considerations

  • Give links a descriptive name so users will know where the link will take them if selected.
  • Similarly, label buttons so that their function is clear.

Development Considerations

  • The destination or function of each link/button should be clearly explained in the link/button text or programmatically-determined link context.
  • Tip: ARIA Links
    • Use HTML element to create links whenever possible.
    • ARIA links do not have any native styling or functionality, so you will need to add things like keyboard support, underline and color.
    • Use CSS to change the cursor to a pointer (in most browsers this looks like a hand). If you don’t, the cursor will look like a text selector, which will be confusing to sighted users.