WebAIM - Web Accessibility In Mind

E-mail List Archives

Re: advice on page with Non-distinguishable links

for

From: Birkir R. Gunnarsson
Date: Dec 4, 2016 5:59PM

aria-label is supposed to override the text of the link per the
accessible name computation which goes:
1. aria-labelledby
2. aria-label
3. native labeling (for buttons and links tah is the contents f the
element, for a form field it would be the contents of the connected
label element).
4. title

So
THe accessible name of this link should be Google (not Bing):
<span id="foo1">Google</span>
<a href="http://www.bing.com" aria-labelledby="foo1">Bing</a>

the accessible name of this link is Bing:
<a href="http:/www.google.com" aria-label="bing">Google</a>

This is why using ARIA to label elements should be avoided.
-B



On 12/4/16, Beranek, Nicholas < <EMAIL REMOVED> > wrote:
> Sometimes I'll find that aria-label overwrites the innerText of an anchor so
> I try to avoid it. Also, it will be considered the accessible name of a link
> when what we're looking for is an accessible description. Therefore,
> aria-describedby would be your best bet.
>
> Sent from my iPhone
>
>> On Dec 3, 2016, at 10:38 PM, Jonathan C. Cohn < <EMAIL REMOVED> >
>> wrote:
>>
>> When using the title attribute most screen reader browser combinations
>> speak title and screen text when tabbing between links but not when using
>> screen reader navigation.
>>
>> Is there a disadvantage to aria labels in text links?
>>
>> Best wishes,
>>
>> Jonathan Cohn
>>
>>> On Dec 2, 2016, at 3:28 AM, Julie Chan Watson
>>> < <EMAIL REMOVED> > wrote:
>>>
>>> Hi
>>> I read a great article about the use of the title attribute on links, and
>>> how screen readers handle them.
>>> Advice was to not use them as they are not read out by screen readers,
>>> unless there is no link text at all.
>>> Recommendation was to add all the text you need as the link text, and put
>>> <span> around the screen reader specific bits. and hide from other users
>>> with css.
>>>
>>> https://silktide.com/i-thought-title-text-improved-accessibility-i-was-wrong/
>>> <https://silktide.com/i-thought-title-text-improved-accessibility-i-was-wrong/>
>>>
>>>
>>> --
>>> Julie Chan Watson
>>> Web Developer
>>> Corporate Information & Computing Services (CiCS)
>>> The University of Sheffield
>>>
>>>
>>>>> On 30 Nov 2016, at 19:46, Jonathan Avila < <EMAIL REMOVED> >
>>>>> wrote:
>>>>>
>>>>> That's correct. SC 2.4.4 Link Purpose (In Context) does not require the
>>>>> link text itself to determine its purpose.
>>>>
>>>> The thinking behind this was that a screen reader user could keep their
>>>> focus on the link and use other common screen reader commands to access
>>>> other contextual information. For example, screen readers often provide
>>>> commands to read the header, sentence, paragraph, and list item without
>>>> requiring the user to move focus.
>>>>
>>>> As for the links list -- I'd consider that a feature request to screen
>>>> reader vendors. As far as I know even if title is used JAWS will only
>>>> display the title in the list of links if there isn't link text there
>>>> already. Aria-label should work.
>>>>
>>>> Jonathan
>>>>
>>>> Jonathan Avila
>>>> Chief Accessibility Officer
>>>> SSB BART Group
>>>> <EMAIL REMOVED>
>>>> 703.637.8957 (Office)
>>>> Vis Visit us online: Website | Twitter | Facebook | LinkedIn | Blog
>>>> Don't miss Trends in Accessibility & Electronic Documents on Wed 12/7!
>>>>
>>>> The information contained in this transmission may be attorney
>>>> privileged and/or confidential information intended for the use of the
>>>> individual or entity named above. If the reader of this message is not
>>>> the intended recipient, you are hereby notified that any use,
>>>> dissemination, distribution or copying of this communication is strictly
>>>> prohibited.
>>>>
>>>>
>>>>
>>>>