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 6:08PM

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 REMOVED> > wrote:
> Our CMS does not support ARIA and so I am looking for ways to not have to
> make hand-coding exceptions.
>
> -----Original Message-----
> From: WebAIM-Forum [mailto: <EMAIL REMOVED> ] On Behalf
> Of Birkir R. Gunnarsson
> Sent: Wednesday, November 30, 2016 12:24 PM
> To: WebAIM Discussion List
> Subject: Re: [WebAIM] advice on page with Non-distinguishable links
>
> 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.
>>
>>
>>
>> -----Original Message-----
>> From: WebAIM-Forum [mailto: <EMAIL REMOVED> ] On
>> Behalf Of Beranek, Nicholas
>> Sent: Wednesday, November 30, 2016 2:37 PM
>> To: WebAIM Discussion List
>> Subject: Re: [WebAIM] advice on page with Non-distinguishable links
>>
>> 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 REMOVED> on behalf of <EMAIL REMOVED> >
>> wrote:
>>
>> Even though in links list mode a screen reader user wouldn't have
>> that context?
>>
>> -----Original Message-----
>> From: WebAIM-Forum [mailto: <EMAIL REMOVED> ]
>> On Behalf Of Beranek, Nicholas
>> Sent: Wednesday, November 30, 2016 11:13 AM
>> To: WebAIM Discussion List
>> Subject: Re: [WebAIM] advice on page with Non-distinguishable
>> links
>>
>> 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 REMOVED> on behalf of <EMAIL 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
>>
>> -----Original Message-----
>> From: WebAIM-Forum
>> [mailto: <EMAIL REMOVED> ] On Behalf Of Beranek,
>> Nicholas
>> Sent: Wednesday, November 30, 2016 9:55 AM
>> To: WebAIM Discussion List
>> Subject: Re: [WebAIM] advice on page with Non-distinguishable
>> links
>>
>> 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 REMOVED> on behalf of <EMAIL 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 REMOVED> <mailto: <EMAIL 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.
>> >> >> >> >> >> >> >> >>
>>
>>
>> >>
>> 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.
>> >> >> archives at http://webaim.org/discussion/archives
>> >> >> >> >> >>
>>
>>
>> >>
>> 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.
>> >> >> archives at http://webaim.org/discussion/archives
>> >> >> >> archives at http://webaim.org/discussion/archives
>> >>
>
>
> --
> Work hard. Have fun. Make history.
> > > http://webaim.org/discussion/archives
> > > > > >


--
Work hard. Have fun. Make history.