WebAIM - Web Accessibility In Mind

E-mail List Archives

Re: advice on page with Non-distinguishable links

for

From: Birkir R. Gunnarsson
Date: Nov 30, 2016 1:24PM

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 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.
>
>
>
>