E-mail List Archives
Thread: Providing the correct information about a redundant link
Number of posts in this thread: 5 (In chronological order)
From:
Subject: Providing the correct information about a redundant link
No previous message | Next message →
Hello everyone,
As an absolute beginner in accessibility testing I would like to ask for
a recommendation.
I am working with the project where I am asked to do an accessibility
testing.
I am not sure if I provide an information about the bugs in a correct way.
In the example below I will paste my text with how I described the
redundant links issue.
I will really appreciate any suggestions how it is better to correct the
report and how it is better to report about accessibility issues.
Title:
Accessibility - redundant links
Description:
The redundant links are present on a web page.
Preconditions:
nvda 2020.3.
Steps to reproduce:
1. Launch nvda.
2. Open google chrome and navigate to access travel webpage.
3. Using only keyboard for navigating, press down arrow. You will notice
that screen reader announces link graphic "Moscow" and then the link
"Moscow" below.
Expected result:
The redundant links shouldn't have the images with redundant alternative
text. It is needed to make the alt tag invisible for screen readers by
putting alt="".
In that case the screan reader won't process the image and the user
won't be able to interactwith it, but he will be able to navigate to the
link without any repititions while navigating.
Actual result:
The screen reader tells the text of the image and then it tells the text
of the link which is absolutely the same.
The redundant link on a page means that the screen reader and keyboard
users will have to navigate the same elements several times.
Usually it happens when there is an image with the alt-text and the link
that is located below the linked image.
It is needed to combine all redundant links into one link and remove the
redundant alternative text from images inserting alt="" to them.
Standards and guidelines:
https://webaim.org/standards/wcag/checklist#sc2.4.4
Code:
<a href="/en-US/Guide/Index/41" tabindex="0">
<img class="rounded-circle" width="88" height="88"
src="/media/eadaed3a-c88b-4083-8916-b1d0685f829f_small.png"
alt="Rent&Repair Equipment">
<div class="teammate">
<p>Rent&Repair Equipment</p>
<span>(Guide)</span>
<div class="country">Kaliningrad</div>
</div>
</a>
--
Best regards,
Vsievolod
From: Patrick H. Lauke
Date: Wed, Oct 21 2020 11:23AM
Subject: Re: Providing the correct information about a redundant link
← Previous message | Next message →
On 21/10/2020 17:51, ÐÑеволод Ðопов wrote:
[...]
> Standards and guidelines:
> https://webaim.org/standards/wcag/checklist#sc2.4.4
I would not point to WebAim in terms of "standards and guidelines", but
to the actual WCAG SC
https://www.w3.org/TR/WCAG21/#link-purpose-in-context (and maybe point
to the webaim checklist there as an additional resource, something like
"See also ...")
Also, as an aside, I don't think a redundant link is an actual WCAG
failure (if the link with the same text goes to the same URL). it would
fail 2.4.4 if it had the same text but was going to different places.
P
--
Patrick H. Lauke
https://www.splintered.co.uk/ | https://github.com/patrickhlauke
https://flickr.com/photos/redux/ | https://www.deviantart.com/redux
twitter: @patrick_h_lauke | skype: patrick_h_lauke
From: Patrick H. Lauke
Date: Wed, Oct 21 2020 11:26AM
Subject: Re: Providing the correct information about a redundant link
← Previous message | Next message →
On 21/10/2020 18:23, Patrick H. Lauke wrote:
> Also, as an aside, I don't think a redundant link is an actual WCAG
> failure (if the link with the same text goes to the same URL). it would
> fail 2.4.4 if it had the same text but was going to different places.
There's an *advisory* technique here in WCAG
https://www.w3.org/WAI/WCAG21/Techniques/html/H2 but note that not doing
this is not an actual failure per se.
P
--
Patrick H. Lauke
https://www.splintered.co.uk/ | https://github.com/patrickhlauke
https://flickr.com/photos/redux/ | https://www.deviantart.com/redux
twitter: @patrick_h_lauke | skype: patrick_h_lauke
From:
Subject: Re: Providing the correct information about a redundant link
← Previous message | Next message →
Hello,
Do I understand correctly that it is better not to point on a webaim
recommendations as standards and guidelines in general?
Usually as I do now:
I find an error in the wave tool, try to encounterit myself,
go to the description that wave provides and copy the links where it
says standards and guidelines.
How is it better to do in that case?
I ask that because I haven't found a quick way of finding the needed
wcag recommendation yet.
Thank you.
--
Best regards,
Vsievolod
From: Patrick H. Lauke
Date: Wed, Oct 21 2020 1:14PM
Subject: Re: Providing the correct information about a redundant link
← Previous message | No next message
On 21/10/2020 20:10, ÐÑеволод Ðопов wrote:
> Hello,
>
> Do I understand correctly that it is better not to point on a webaim
> recommendations as standards and guidelines in general?
>
> Usually as I do now:
>
> I find an error in the wave tool, try to encounterit myself,
>
> go to the description that wave provides and copy the links where it
> says standards and guidelines.
>
> How is it better to do in that case?
WebAIM's list is not the standard. WCAG is the standard. Point to WCAG
>
> I ask that because I haven't found a quick way of finding the needed
> wcag recommendation yet.
Aeh...the link to the relevant WCAG SC is right there on the WebAIM
checklist if you actually press the link in the "WCAG Success Criteria"
column there. (i.e. on
https://webaim.org/standards/wcag/checklist#sc2.4.4 follow the link to
2.4.4 "Link Purpose (In Context)"
P
--
Patrick H. Lauke
https://www.splintered.co.uk/ | https://github.com/patrickhlauke
https://flickr.com/photos/redux/ | https://www.deviantart.com/redux
twitter: @patrick_h_lauke | skype: patrick_h_lauke