Creating access for everyone, everywhere requires attention to accessibility attributes, best practices, and requirements. Find accessibility guidance below.


Note: Components in each code library are implemented differently (especially Flutter). Many of the behaviors and attributes described are already handled for you as part of our components. Product teams are responsible for ensuring their apps meet all current requirements. Some of the information below may not apply to your implementation.

Best practices

Ensure the following best practices are met when implementing this component during development.

  • Use an when the link text alone does not convey enough information to a screen reader.
  • Ensure include context to indicate where the link leads, especially if the link is visually grouped in a template. For example, use “Learn more about [something]”.
  • Ensure the always starts with the visible link text.
  • When a link opens or downloads other formats (e.g., .pdf, .mp3), ensure the label indicates this, such as .
  • Indicate when links open in new tabs or pages using
  • Use on external links for added security.
Two dialogs with similar link titles annotated to show the unique aria-labels for each link.

Keyboard controls

Keyboard actions and their corresponding behaviors for links
Key Behavior
EnterActivates link.

VGAR (internal only)

Find links to the Visa Global Accessibility Requirements (VGAR) for this component.