E-mail List Archives
Thread: advice on page with Non-distinguishable links
Number of posts in this thread: 24 (In chronological order)
From: Angela French
Date: Wed, Nov 30 2016 10:39AM
Subject: advice on page with Non-distinguishable links
No previous message | Next message →
Hello,
I'm looking for some advice on how we might be able to remedy the Non-distinguishable Links errors on a page I'm working on.
The page consists of Year headings and underneath each year is a set of links to documents. These documents are titled the same for each year:
* Introductions
* Enrollments
* Selected Programs
* Student Progress and Success
* Etc.
This results in numerous link labels that are the same but go to different destinations. Short of adding the year to each link label, is there another way to handle this? Adding the year would seem to add unnecessary visual and aural redundancy.
Thanks!
Angela French
Internet/Intranet Specialist
Washington State Board for Community and Technical Colleges
360-704-4316
= EMAIL ADDRESS REMOVED = <mailto: = EMAIL ADDRESS REMOVED = >
www.sbctc.edu<;http://www.sbctc.edu/>;
From: Beranek, Nicholas
Date: Wed, Nov 30 2016 10:55AM
Subject: Re: advice on page with Non-distinguishable links
← Previous message | Next message →
Hi Angela,
This is assuming that you are following level AA and not AAA. If you have a look at SC 2.4.4 Link Purpose (In Context), you'll find the following sufficient technique: H33: Supplementing link text with the title attribute. Therefore, if you add a title attribute to each link and include the year as its value, then it will satisfy this success criterion.
Another technique that is not included as a sufficient technique is using the heading itself as the context for the links, or even the name of the region or landmark in which it's contained. I would like to ask others what their thoughts are about this. If that is deemed sufficient, then you have already satisfied it.
Nick
--
Nick Beranek
Digital Accessibility Team
On 11/30/16, 12:39 PM, "WebAIM-Forum on behalf of Angela French" < = EMAIL ADDRESS REMOVED = on behalf of = EMAIL ADDRESS REMOVED = > wrote:
Hello,
I'm looking for some advice on how we might be able to remedy the Non-distinguishable Links errors on a page I'm working on.
The page consists of Year headings and underneath each year is a set of links to documents. These documents are titled the same for each year:
* Introductions
* Enrollments
* Selected Programs
* Student Progress and Success
* Etc.
This results in numerous link labels that are the same but go to different destinations. Short of adding the year to each link label, is there another way to handle this? Adding the year would seem to add unnecessary visual and aural redundancy.
Thanks!
Angela French
Internet/Intranet Specialist
Washington State Board for Community and Technical Colleges
360-704-4316
= EMAIL ADDRESS REMOVED = <mailto: = EMAIL ADDRESS REMOVED = >
www.sbctc.edu<;http://www.sbctc.edu/>;
The information contained in this e-mail is confidential and/or proprietary to Capital One and/or its affiliates and may only be used solely in performance of work or services for Capital One. The information transmitted herewith is intended only for use by the individual or entity to which it is addressed. If the reader of this message is not the intended recipient, you are hereby notified that any review, retransmission, dissemination, distribution, copying or other use of, or taking of any action in reliance upon this information is strictly prohibited. If you have received this communication in error, please contact the sender and delete the material from your computer.
From: Angela French
Date: Wed, Nov 30 2016 10:58AM
Subject: Re: advice on page with Non-distinguishable links
← Previous message | Next message →
I hadn't remembered the title attribute. That is an acceptable solution for our CMS. Works for me! Thanks.
Angela French
From: Angela French
Date: Wed, Nov 30 2016 12:08PM
Subject: Re: advice on page with Non-distinguishable links
← Previous message | Next message →
What about in a table like this? http://www.sbctc.edu/our-colleges/college-contact-list.aspx . Do you think title attributes are necessary or does the table provide adequate context?
Angela French
From: Beranek, Nicholas
Date: Wed, Nov 30 2016 12:13PM
Subject: Re: advice on page with Non-distinguishable links
← Previous message | Next message →
The column headers add that context. Therefore, the title attributes are unnecessary.
--
Nick Beranek
Digital Accessibility Team
On 11/30/16, 2:08 PM, "WebAIM-Forum on behalf of Angela French" < = EMAIL ADDRESS REMOVED = on behalf of = EMAIL ADDRESS REMOVED = > wrote:
What about in a table like this? http://www.sbctc.edu/our-colleges/college-contact-list.aspx . Do you think title attributes are necessary or does the table provide adequate context?
Angela French
From: Angela French
Date: Wed, Nov 30 2016 12:31PM
Subject: Re: advice on page with Non-distinguishable links
← Previous message | Next message →
Even though in links list mode a screen reader user wouldn't have that context?
From: Moore,Michael (Accessibility) (HHSC)
Date: Wed, Nov 30 2016 12:35PM
Subject: Re: advice on page with Non-distinguishable links
← Previous message | Next message →
Exactly.
Mike Moore
Accessibility Coordinator
Texas Health and Human Services Commission
Civil Rights Office
(512) 438-3431 (Office)
From: Beranek, Nicholas
Date: Wed, Nov 30 2016 12:36PM
Subject: Re: advice on page with Non-distinguishable links
← Previous message | Next message →
That's correct. SC 2.4.4 Link Purpose (In Context) does not require the link text itself to determine its purpose. The AAA violation, SC 2.49 Link Purpose (Link Only), is what requires the link text by itself provide the context.
I would consider it to be a Best Practice, however, to provide additional information, but it is not something I would penalize someone for.
--
Nick Beranek
Digital Accessibility Team
On 11/30/16, 2:31 PM, "WebAIM-Forum on behalf of Angela French" < = EMAIL ADDRESS REMOVED = on behalf of = EMAIL ADDRESS REMOVED = > wrote:
Even though in links list mode a screen reader user wouldn't have that context?
From: Jonathan Avila
Date: Wed, Nov 30 2016 12:46PM
Subject: Re: advice on page with Non-distinguishable links
← Previous message | Next message →
> 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 ADDRESS 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.
From: Birkir R. Gunnarsson
Date: Wed, Nov 30 2016 1:24PM
Subject: Re: advice on page with Non-distinguishable links
← Previous message | Next message →
Check out the WCAG definition of "programmatically determined context"
forlink text:
http://www.w3.org/TR/UNDERSTANDING-WCAG20/navigation-mechanisms-refs.html#pdlinkcontextdef
It does not include headings, admittedly, but I think headings should
be sufficient.
One thing you can do is to give individual headings a unique ID
attribute and use aria-describedby to point to the appropriate
heading:
<h2 id="y1">1999</h2>
<a href="#" aria-describedby="y1">Enrollment</a>
<h2 id="y2">2000</h2>
<a href="#" aria-describedby="y2">Enrollment</a>
etc.
On 11/30/16, Jonathan Avila < = EMAIL ADDRESS 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 ADDRESS 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.
>
>
>
>
From: Angela French
Date: Wed, Nov 30 2016 1:27PM
Subject: Re: advice on page with Non-distinguishable links
← Previous message | Next message →
Our CMS does not support ARIA and so I am looking for ways to not have to make hand-coding exceptions.
From: Birkir R. Gunnarsson
Date: Wed, Nov 30 2016 6:08PM
Subject: Re: advice on page with Non-distinguishable links
← Previous message | Next message →
For the first link in each list you could add a title attribute whose
contents duplicate the previous heading.
While that would not fully meet the 2.4.4 requirement in theory, I
think it would provide enough context for the user )which is the more
important thing at the end of the day).
On 11/30/16, Angela French < = EMAIL ADDRESS REMOVED = > wrote:
> Our CMS does not support ARIA and so I am looking for ways to not have to
> make hand-coding exceptions.
>
>
From: Jonathan Avila
Date: Thu, Dec 01 2016 10:09AM
Subject: Re: advice on page with Non-distinguishable links
← Previous message | Next message →
> Another technique that is not included as a sufficient technique is using the heading itself as the context for the links, or even the name of the region or landmark in which it's contained. I would like to ask others what their thoughts are about this. If that is deemed sufficient, then you have already satisfied it.
With JAWS you can press JAWSKey+T to read the page title and it will also tell you the name of the closest heading above your location without moving focus. This same functionality isn't available in other assistive technology -- so I believe that lack of broad support caused it to be removed as a sufficient technique.
Jonathan
Jonathan Avila
Chief Accessibility Officer
SSB BART GroupÂÂ
= EMAIL ADDRESS REMOVED =
703.637.8957 (Office)
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.
From: Birkir R. Gunnarsson
Date: Thu, Dec 01 2016 4:02PM
Subject: Re: advice on page with Non-distinguishable links
← Previous message | Next message →
The previous heading used to be listed as a valid technique. Then it
was removed.
I don't know why because I think it is perfectly valid.
A sighted user has to look at the heading next ot a list of links, so
why wouldn't it be sufficient for a screen reader user to do the same?
On 12/1/16, Jonathan Avila < = EMAIL ADDRESS REMOVED = > wrote:
>> Another technique that is not included as a sufficient technique is using
>> the heading itself as the context for the links, or even the name of the
>> region or landmark in which it's contained. I would like to ask others
>> what their thoughts are about this. If that is deemed sufficient, then you
>> have already satisfied it.
>
> With JAWS you can press JAWSKey+T to read the page title and it will also
> tell you the name of the closest heading above your location without moving
> focus. This same functionality isn't available in other assistive
> technology -- so I believe that lack of broad support caused it to be
> removed as a sufficient technique.
>
> Jonathan
>
> Jonathan Avila
> Chief Accessibility Officer
> SSB BART Group
> = EMAIL ADDRESS REMOVED =
> 703.637.8957 (Office)
>
> 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.
>
>
>
From: Angela French
Date: Thu, Dec 01 2016 4:13PM
Subject: Re: advice on page with Non-distinguishable links
← Previous message | Next message →
Thanks you for all your opinions on this subject.
Angela French
From: Jared Smith
Date: Thu, Dec 01 2016 4:13PM
Subject: Re: advice on page with Non-distinguishable links
← Previous message | Next message →
Birkir R. Gunnarsson wrote:
> The previous heading used to be listed as a valid technique. Then it
> was removed.
It's still there, but as an advisory technique -
https://www.w3.org/TR/WCAG20-TECHS/H80.html
This certainly isn't optimal, but relying on the heading to provide
the context is, I think, much more usable to a screen reader user than
extremely verbose and repetitive link texts, which are definitely less
accessible for everyone else.
Jared
From: Angela French
Date: Thu, Dec 01 2016 4:18PM
Subject: Re: advice on page with Non-distinguishable links
← Previous message | Next message →
Perfect! I have quite a few instances like Example 1 on my site. I'll quit worrying so much.
Angela
From: Julie Chan Watson
Date: Fri, Dec 02 2016 1:28AM
Subject: Re: advice on page with Non-distinguishable links
← Previous message | Next message →
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 ADDRESS 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 ADDRESS 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.
>
>
>
>
From: Angela French
Date: Fri, Dec 02 2016 9:28AM
Subject: Re: advice on page with Non-distinguishable links
← Previous message | Next message →
I have done that sort of thing when I hand coded sites, but with CMSs this is not an option for the typical web editor.
Angela French
From: Jonathan C. Cohn
Date: Sat, Dec 03 2016 8:37PM
Subject: Re: advice on page with Non-distinguishable links
← Previous message | Next message →
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 ADDRESS 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 ADDRESS 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 ADDRESS 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.
>>
>>
>>
>>
From: Birkir R. Gunnarsson
Date: Sun, Dec 04 2016 5:03AM
Subject: Re: advice on page with Non-distinguishable links
← Previous message | Next message →
The accessible name calculation algorithm maps a link's title
attribute to its accessible description property if there is another
source of accessible name.
Screen readers choose (correctly in my opinion) to only announce
accessible description in forms mode or when element receives focus.
In this case, if you are exploring the page in browse mode you see the
heading before the link list, so you know the context of the links and
don't need the description.
If you traverse the page with the tab key you have a harder time
seeing the headings (though you can easily) so additional title
attribute may be helpful.
aria-label is tricky. It overrides the visible link text, and creates
potentially a different experience for screen readers (also remember
the first rule of ARIA). Only use it if the link has no visible text
(.e.g. links with CSS background images).
As Jared pointed out, including a large blob of visually hidden
explanatory text in links does not equate to a good screen reader
experience.
General recommendation for effective link text is to keep it short,
same applies when users listen to the link text.
On 12/3/16, Jonathan C. Cohn < = EMAIL ADDRESS 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 ADDRESS 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 ADDRESS 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 ADDRESS 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.
>>>
>>>
>>>
>>>
From: Jonathan Cohn
Date: Sun, Dec 04 2016 9:04AM
Subject: Re: advice on page with Non-distinguishable links
← Previous message | Next message →
Thanks, my exact situation is a list of questions that have been answered, CSS has been used to add a graphic indicating the question was marked by the user to go back to. Also, the list of questions just is numerical values. The developer had added a Title attribute to indicate this CSS and I just suggested using ARIA-LABEL instead. Do you see any issues with this?
Thanks,
Jonathan Cohn
> On Dec 4, 2016, at 7:03 AM, Birkir R. Gunnarsson < = EMAIL ADDRESS REMOVED = > wrote:
>
> The accessible name calculation algorithm maps a link's title
> attribute to its accessible description property if there is another
> source of accessible name.
> Screen readers choose (correctly in my opinion) to only announce
> accessible description in forms mode or when element receives focus.
> In this case, if you are exploring the page in browse mode you see the
> heading before the link list, so you know the context of the links and
> don't need the description.
> If you traverse the page with the tab key you have a harder time
> seeing the headings (though you can easily) so additional title
> attribute may be helpful.
> aria-label is tricky. It overrides the visible link text, and creates
> potentially a different experience for screen readers (also remember
> the first rule of ARIA). Only use it if the link has no visible text
> (.e.g. links with CSS background images).
> As Jared pointed out, including a large blob of visually hidden
> explanatory text in links does not equate to a good screen reader
> experience.
> General recommendation for effective link text is to keep it short,
> same applies when users listen to the link text.
>
>
>
>
> On 12/3/16, Jonathan C. Cohn < = EMAIL ADDRESS 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 ADDRESS 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 ADDRESS 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 ADDRESS 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.
>>>>
>>>>
>>>>
>>>>
From: Beranek, Nicholas
Date: Sun, Dec 04 2016 2:25PM
Subject: Re: advice on page with Non-distinguishable links
← Previous message | Next message →
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 ADDRESS 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 ADDRESS 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 ADDRESS 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 ADDRESS 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.
>>>
>>>
>>>
>>>
From: Birkir R. Gunnarsson
Date: Sun, Dec 04 2016 5:59PM
Subject: Re: advice on page with Non-distinguishable links
← Previous message | No next message
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 ADDRESS 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 ADDRESS 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 ADDRESS 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 ADDRESS 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 ADDRESS 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.
>>>>
>>>>
>>>>
>>>>