Re: (WCAG 2.1) Do we want to replace ​"programmatically determined link context" in 2.4.4 with "Accessible Name"?

I’d probably go from most to least specific, e.g:

2.4.4 Link Purpose (In Context): The purpose of each link can be determined from the link text alone, or from its Accessible Name, 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. (Level A)



However, if we include Accessible Name then it could be different from the link-text, is that a desirable possibility?



Conceptually you would need to have it as: “or from the (link text/accessible name) together with its programmatically determined link context”



From the spec [1] it’s aria-labelledby > aria-label > text > title > summary.



Therefore you could have a link such as:

<a href=”/news/” aria-label=”read more”>News</a>



Which would be “news” from looking at it, but “read more” from a screen reader.



I think it opens the SC up to too many connotations and different interfaces, I’d rather keep to link-text + context.



Unless there is another SC elsewhere that prevents this type of confusion?



The principle that I’m trying to follow is to avoid multiple interfaces whenever possible (e.g. thinking “screen readers do this, visual users do that”), and keeping things like Accessible Name to only when they are absolutely needed.



Cheers,



-Alastair



1] https://www.w3.org/TR/html-aapi/#h3_a-element