WebAIM - Web Accessibility In Mind

E-mail List Archives

Re: [EXTERNAL]Linking article previews

for

From: Mark Magennis
Date: Jul 22, 2019 10:36AM

I think that's debatable Jonathan. SC 2.5.3 talks about "the words which visually label a component" and goes on to say "it is first necessary to determine which text on the screen should be considered a label for any given control". I don't see anything that explicitly states that this must include all of the text on or within the bounds of the control and to me it intuitively feels like it shouldn't. Is there any more guidance on this from WAI or a general consensus that has arisen from discussion?

Mark

Mark Magennis
Skillsoft | mobile: +353 87 60 60 162
Accessibility Specialist


-----Original Message-----
From: WebAIM-Forum < <EMAIL REMOVED> > On Behalf Of Jonathan Avila
Sent: 22 July 2019 17:22
To: WebAIM Discussion List < <EMAIL REMOVED> >
Subject: Re: [WebAIM] [EXTERNAL] Re: Linking article previews

I've seen a related issue with cards. If the whole card is actionable and you want to meet WCAG 2.1 SC 2.5.4 Label in Name then the accessible name for the card must contain everything shown in the card as text. This means that you can't have a summarized accessible name for the card. This seems problematic in some situations.

Jonathan

Jonathan Avila, CPWA
Chief Accessibility Officer
Level Access
<EMAIL REMOVED>
703.637.8957 office
Visit us online:
Website | Twitter | Facebook | LinkedIn | Blog



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 < <EMAIL REMOVED> > On Behalf Of Mark Magennis
Sent: Monday, July 22, 2019 11:59 AM
To: WebAIM Discussion List < <EMAIL REMOVED> >
Subject: Re: [WebAIM] [EXTERNAL] Re: Linking article previews

CAUTION: This email originated from outside of the organization. Do not click links or open attachments unless you recognize the sender and know the content is safe.


Well, Brian didn't want the entire text of the article to be read out as the link name, but I imagined that his UX crew probably still want the entire area of the article to be mouse clickable.

I actually have almost the same issue here except the approach I've suggested won't work for us. We have cards that represent learning assets (courses, videos, audiobooks, etc.) and which contain a lot of content (name, type, details, image, etc.) just like Brian. We also want the card to be a link that opens the asset, we want mouse users to be able to click anywhere on it, but we don't want all that content to be read out as the link title. But our cards also contain a Like button and an Actions menu and we are finding that when the Actions menu button receives focus in IE11, JAWS and NVDA both read out the entire contents of the card before reading the button's name. The 'cause' appears to be a tabindex="-1" on an ancestor div but that's there for a good reason so we're having to think creatively about how to get rid of it without getting rid of it. Sometimes I wish we could just get rid of Internet Explorer. But we can't.

Mark

Mark Magennis
Skillsoft | mobile: +353 87 60 60 162
Accessibility Specialist


-----Original Message-----
From: WebAIM-Forum < <EMAIL REMOVED> > On Behalf Of glen walker
Sent: 22 July 2019 16:14
To: WebAIM Discussion List < <EMAIL REMOVED> >
Subject: Re: [WebAIM] [EXTERNAL] Re: Linking article previews

That was Brian's original request, that he didn't want the entire <div> to be the link. That was actually my first idea but I changed it after I re-read his question.

On Mon, Jul 22, 2019 at 3:27 AM Mark Magennis < <EMAIL REMOVED> >
wrote:

> Glen, a problem with this approach is that the whole on-screen area of
> the article is no longer clickable. You have to click on the title.
>
>
>