WebAIM - Web Accessibility In Mind

E-mail List Archives

Re: [EXT] Label in name

for

From: Patrick H. Lauke
Date: Jun 23, 2021 4:57PM

On 23/06/2021 22:21, Sailesh Panchang wrote:
> Some thoughts for consideration:
> The Understanding doc states the SC does not apply when there is no visible label.
> In a sense it does not apply also when one has used technique H44 (for-id) method to associate the visible label with the control thereby meeting SC 1.3.1.

It's not that it does not apply. I'd rather say that following H44 is
also a good way to satisfy the SC.

> No further testing of SC 2.5.3 is required in this case.

You'd still want to test to check that the accessible name wasn't
overridden on the control, negating the benefit of H44...something like

<label for="foo">Foo</label>
<input id="foo" aria-label="Bar">

> Therefore, even WCAG 2.0 considered the needs of voice input AT users;

Not really. It's more a side effect.

> Though the native HTML LABEL element (and thus H44) rank lower in the accessible name computation

The "ranks lower" part only comes into play if there are multiple
potential sources for the accessible name in play, as in the above example.

> it has benefits for multiple user groups and should be the preferred technique.

Is there a point in having a "preferred" technique? What matters is the
end result, regardless of how the author achieved it. There may well be
valid situations where an author couldn't use H44 directly, but still
achieved the same result in another way. Which is fine and passes.

P
--
Patrick H. Lauke

https://www.splintered.co.uk/ | https://github.com/patrickhlauke
https://flickr.com/photos/redux/ | https://www.deviantart.com/redux
twitter: @patrick_h_lauke | skype: patrick_h_lauke