2.5.3 Label in Name - case insensitve?

[patrickhlauke]

I'm going to assume (based on the described use cases/benefits) that 2.5.3 is case insensitive. For instance, I'd assume the following passes:

<button aria-label="Delete">DELETE</button>

If others agree, suggest this should be clarified/mentioned in the understanding document (don't think it currently does, unless I missed)

https://www.w3.org/WAI/WCAG22/Understanding/label-in-name.html

[giacomo-petri]

I’m curious if it makes a difference whether an acronym is used in uppercase vs lowercase.

Let's consider:

• "ADD" as a word in the context of "add to bag": <button aria-label="add">ADD</button> No issues
• "ADD" as an acronym for "Attention Deficit Disorder": <a href="..." aria-label="add">ADD</a> Could there be any issue here?

I know that VoiceOver, for instance, tends to read uppercase acronyms as individual letters. However, I’m unsure how speech recognition technologies handle this. Do they recognize acronyms letter by letter, or do they interpret the entire word?

In the context of "Attention Deficit Disorder," I wouldn't expect someone to pronounce "add" as a word. Instead, I would anticipate it being spelled out as "A," "D," "D."

Does it make a difference for speech recognition technology users if you use:

<a href="..." aria-label="add">ADD</a> vs <a href="..." aria-label="ADD">ADD</a>

?

[filippo-zorzi]

Voice Control (with Chrome, for what it matters) doesn't distinguish between "add" and "ADD".

https://github.com/user-attachments/assets/dcbc1e9c-ff3b-48f9-acbd-de73348690ff

"A.D.D." has to be spelled out but this is not in the focus of this issue.