E-mail List Archives

Search E-mail List Archives for

Number of posts in this thread: 6 (In chronological order)

From: Jon Brundage
Date: Tue, Oct 01 2019 8:13AM
Subject: WCAG 2.1 2.5.3 Label in name
No previous message | Next message →

Hello-

Our organization has used hidden text to expand links that need more context than what is displayed visually.

For example, where multiple "learn more" links appear on a page we will expand them- the visual is "learn more" but we make them unique and meaningful by adding "about (subject)" with hidden text. Or if an image button is used the ALT text is expanded "ALT="learn more about (subject)"

Under WCAG 2.1 2.5.3 "Label in Name" is this technique no longer acceptable? Due to the need to identify links with voice dictation, must the full link text now appear visually? The extra space needed to expand all links visually is a design constraint that we would like to avoid if possible.

thanks

Jon

From: Steve Green
Date: Tue, Oct 01 2019 8:16AM
Subject: Re: WCAG 2.1 2.5.3 Label in name
← Previous message | Next message →

You can still use that technique as long as the visible label is an exact substring of the accessible name as computed by the accessible name computation algorithm.

Steve Green
Managing Director
Test Partners Ltd

From: Jon Brundage
Date: Tue, Oct 01 2019 8:30AM
Subject: Re: WCAG 2.1 2.5.3 Label in name
← Previous message | Next message →

Thanks Steve- could you cite an example of "exact substring of the
accessible name as computed by the accessible name computation algorithm"?

Jon

From: Steve Green
Date: Tue, Oct 01 2019 9:01AM
Subject: Re: WCAG 2.1 2.5.3 Label in name
← Previous message | Next message →

It's pretty well described at https://www.w3.org/WAI/WCAG21/Understanding/label-in-name.html#accessible-name-and-description-computation-specification

The first thing is to work out what the accessible name is. If your code is something like "Learn more <span class="hidden">about sausages</span>", the accessible name will be "Learn more about sausages".

It must be possible to obtain the visible label by removing zero or more characters from the start and end of the accessible name. So "more about sausages" would be fine, as would "more", but "more sausages" or "pork sausages" would not.

Steve

From: Peter Krautzberger
Date: Tue, Oct 01 2019 9:07AM
Subject: Re: WCAG 2.1 2.5.3 Label in name
← Previous message | Next message →

Bryan Garaventa's implementation at [1] is also very useful to quickly test
some markup.

Peter.

[1]
https://whatsock.github.io/w3c-alternative-text-computation/Editable%20Live%20Input%20AccName%20Test.html

Am Di., 1. Okt. 2019 um 17:02 Uhr schrieb Steve Green <
= EMAIL ADDRESS REMOVED = >:

> It's pretty well described at
> https://www.w3.org/WAI/WCAG21/Understanding/label-in-name.html#accessible-name-and-description-computation-specification
>
> The first thing is to work out what the accessible name is. If your code
> is something like "Learn more <span class="hidden">about sausages</span>",
> the accessible name will be "Learn more about sausages".
>
> It must be possible to obtain the visible label by removing zero or more
> characters from the start and end of the accessible name. So "more about
> sausages" would be fine, as would "more", but "more sausages" or "pork
> sausages" would not.
>
> Steve
>
>
>

From: glen walker
Date: Tue, Oct 01 2019 10:22PM
Subject: Re: WCAG 2.1 2.5.3 Label in name
← Previous message | No next message

All good advice so far, Jon. I think the confusion comes in because you're
looking at it "backwards". Anything that is visible (in your case, "learn
more") must exist in the "accessible name". So when you look at the title
of the success criteria, "label in name", "label" is what you visually see
on the screen and "name" is the "accessible name", which is what the screen
reader says.

So if you display "learn more" and your accessible name is "*learn more *about
(subject)", then your label *is* contained in the name so you're good.

I would like to learn more about sausages, though.