Clarification of 2.5.3 Label in Name understanding (case insensitivity) #4836
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
✅ Deploy Preview for wcag2 ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
…3812' into patrickhlauke-issue3812
scottaohara
approved these changes
Dec 28, 2025
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
While the understanding document https://www.w3.org/WAI/WCAG22/Understanding/label-in-name.html does mention that capitalization "may" be irrelevant, the advice buries the lede. This makes it a lot more obvious and explicit, while also mentioning that as best practice capitalization/matching accName and visible label may be meaningful for SR users.
In addition, one aspect that always felt strange and out of place in the understanding was the use of inline "live" examples.
They look amateurish, and the first two don't actually "work" - the accessible names of the controls match exactly what the visible labels are. Replaced these with figures AND code samples that do actually show a divergence between label and accName in terms of punctuation/capitalization.
Lastly, this PR fixes some awkwardness in the prose for the mathematical section.
Closes #3812
Preview: https://deploy-preview-4836--wcag2.netlify.app/understanding/label-in-name