WebAIM - Web Accessibility In Mind

E-mail List Archives

[EXT] Label in name

for

From: Sailesh Panchang
Date: Jun 23, 2021 3:21PM

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. No further testing of SC 2.5.3 is required in this case.
Therefore, even WCAG 2.0 considered the needs of voice input AT users; only the benefit that accrues by using H44 remains undocumented. Though the native HTML LABEL element (and thus H44) rank lower in the accessible name computation, it has benefits for multiple user groups and should be the preferred technique.
Other techniques to assign an accessible name to a UI control that must be used in other situations (when name and visible text cannot be identical) should include guidance now that are part of G208 / G211.
After all that is the way to permit "different user agents, including assistive technologies, can extract and present this information to users in different modalities" i.e. make the name programmatically determinable.
I believe just the new failure technique "F96: Failure due to the accessible name not containing the visible label text" would reinforce the guidance for existing techniques to ensure conformance and benefit for all user groups.
SC 2.5.3 text: "the name contains the text that is presented visually"
which is hardly different from what the new techniques say:
G208: Including the text of the visible label as part of the accessible name
G211: Matching the accessible name to the visible label

Though this thread discusses SC 2.5.3 in the context of links, the above thoughts still apply.
Thanks,
Sailesh