Element does not Indicate User Can Interact with It

Archived Issue

Current Iteration of Issue

Short Description

Screen reader does not recognize that an element is clickable, even though visually it appears clickable

Long Description

  • Sometimes customized elements are created to look like a link or button, but they do not have the proper semantic markup to indicate the proper interaction. A screen reader will read the element as a piece of text.
  • A screen reader user might try clicking on the element because they suspect it should do something, or someone else might tell them the element's function. However, some screen reader users will never click on the element and thus will not have access to any of its functions.
  • These elements do not appear in the tab order, so someone tabbing from one actionable element to the next will miss it.
  • Some screen readers generate a list of elements, , but elements lacking the proper markup do not appear in the list.
  • Screen reader short cut keys will not access these elements, removing a tool for efficient page navigation.
  • Not all screen readers are able to activate the element.

Example of Issue

Example of elements that give screen reader no indication they are clickable


  • Use standard links and buttons when possible.
  • When creating customized elements, Make sure they have proper semantic markup.



Impacted Assistive Technology

Screen Reader

Impacted Type of Device