SC 2.4.4 Link Purpose (In Context) and multiple links with identical link text

[sarasuri]

Hello,
I have a question regarding data tables that contain multiple links with the same link text for example, several links labeled “View” and each leading to different destination. We understand that this can be difficult for screen-reader users as the purpose of each link is only apparent from its visual context. If they access a list of links, they will simply hear “View” repeated multiple times without any context, which can be confusing.

In this situation, we believe it is a failure under SC 2.4.4 Link Purpose (In Context). However, we have recently encountered different viewpoints, and some are questioning whether this actually constitutes a WCAG failure since the success criterion does not explicitly require link text to be unique.

Could you please clarify whether using identical link text such as “View” in this situation is considered a WCAG failure?

Any feedback would be greatly appriciated.
Thank you!

[mbgower]

Draft WCAG 2 Task Force Response
At level AAA, the links fail since they are generic, but most sites only target A/AA. Whether your example passes level A depends on the implementation.

At level A, the link purpose can be derived from the "link text alone or from the link text together with its programmatically determined link context". Your generic "view" links appear in cells of a table. Please see technique H79: Identifying the purpose of a link in a data table using the link text combined with its enclosing table cell and associated table header cells.

If the cells in the Request title column are properly constructed as table headers, this construction meets H79. Screen reader users navigating this table will hear the content of the first cell announced as context as they navigate down through the Action column.

If the first cells of each row are not properly constructed as table headers, then the table usage does not pass the technique's test procedure, and the generic "view" links fail 2.4.4.

Please close this issue if that answers your question.

[samyukthach]

As per WCAG 2.4.4 , the key point is that each link’s purpose must be clear to screen reader users, either from the link text itself or from programmatic context.

So, having multiple links labeled “View” is not automatically a WCAG failure, but it can be problematic if users navigating via a screen reader can’t determine which link goes where or what it does. Visual context alone isn’t enough. There are multiple approaches to fix it.

a. By adding a descriptive link text , for example “View Request 1” / “View Request 2”
b. Hidden screen reader text e.g., Report 1 appended to “View” or aria-label
c. Programmatic context using table headers (scope="row") or aria-labelledby to associate links with their corresponding row

Using one of these approaches, the link purpose is clear for all users while navigating linear or quick navigation.