WebAIM - Web Accessibility In Mind

E-mail List Archives

Re: 2.4.4 Link purpose (In context)

for

From: Birkir R. Gunnarsson
Date: Mar 6, 2020 5:10AM

This is where
WCAG shows its age. I think when 2.4.4 vs. 2.4.6 were created we
typically didn't have more than one button per page, the web
experience was link based.
In my interpretation 2.4.4 is about accessible name of links, not visible text.
Links to different destination need to have different accessible
names, even if the visible text is the same.
This is why, yes, you could use aria-label to fix 2.4.4 (or screen
reader only text).
<a href="http://www.1.com" aria-label="learn more about 1">Learn more</a>
<a href="http://www.2.com" aria-label="learn more about 2">Learn more</a>
The requirements for headings and buttons (2.4.6) are less specific
(which is kind of odd, the same principals should apply).


On 3/6/20, Sumit Patel < <EMAIL REMOVED> > wrote:
> Thanks for both of your response ,
> So, If in the case of a "Learn more" button which does not describe
> enough in the context, since it is a button it will fall into 2.4.6.
> But, still here we'll give recommendation as use aria-label. So, which
> SC it will fall into?
>
> On 06/03/2020, Sumit Patel < <EMAIL REMOVED> > wrote:
>> Hai all,
>>
>> Hope all of you are doing well...
>>
>> I was reading about Link purpose and got a small doubt regarding it.
>> As if link doesn't have descriptive link purpose, then it'll fall into
>> 2.4.4. But, we will give recommendation as to provide descriptive
>> label using aria-label. So, which SC it will violate? . 2.4.4 or 2.4.6
>> ?
>>
>> Thanks in advance
>> Sumit Patel
>>
> > > > >


--
Work hard. Have fun. Make history.