Add a Label in Name (WCAG SC 2.5.3) requirement in Links test

[lisli1]

Is your feature request related to a problem? Please describe.

From a StackOverflow question:

In the tests of the "Link Purpose" section of Accessibility Insights for Web, there is no reference to WCAG SC 2.5.3, Label in Name.

SC 2.5.3 is referenced in the Native Widgets & Custom Widgets sections, in the Instructions subsection.

However, I'm not seeing a test for Label in Name in the "Links" section at all. These days, many websites make their links look like buttons. When a speech-input user is trying to activate a link that looks like a button, the accessible name for the link must either be equivalent to the visible text on that element or must contain the visible text on that element in its entirety. Otherwise, speech-input users who attempt to use the visible label to activate the link will be unsuccessful.

Describe the desired outcome

There should be a "Label in Name" requirement under the "Links" test

Describe alternatives you've considered

Additional context

[ghost]

This issue requires additional investigation by the Accessibility Insights team. When the issue is ready to be triaged again, we will update the issue with the investigation result and add "status: ready for triage". Thank you for contributing to Accessibility Insights!

[ghost]

This issue has been marked as ready for team triage; we will triage it in our weekly review and update the issue. Thank you for contributing to Accessibility Insights!

[LiLoDavis]

We are investigating using the experimental label-content-name-mismatch rule to address this issue. This rule verifies that the accessible name matches or includes the visible text label. The rule might generate a false positive if there is a mismatch but the visible text label is not programmatically associated with the control. A false negative would not be a significant problem for assessment, because users also verify that any visual label is programmatically associated. Nor would a false negative be a significant problem in FastPass, because it is not intended to identify all issues. If the axe rule doesn't work out, we could add an assisted requirement to the Links test. See attached document for details. Links - Label in name.docx

[ghost]

This issue requires additional investigation by the Accessibility Insights team. When the issue is ready to be triaged again, we will update the issue with the investigation result and add "status: ready for triage". Thank you for contributing to Accessibility Insights!

[ferBonnin]

this is now available in prod