Clarify SC 3.3.2 phone number example wording#5025
Open
venkatvemuri28 wants to merge 2 commits intomainfrom
Open
Clarify SC 3.3.2 phone number example wording#5025venkatvemuri28 wants to merge 2 commits intomainfrom
venkatvemuri28 wants to merge 2 commits intomainfrom
Conversation
Update the Labels or Instructions understanding example to remove title-attribute phrasing and use explicit visual-label wording for the three phone-number fields. Fixes #4913
✅ Deploy Preview for wcag2 ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
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
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.
Summary
This PR addresses issue #4913 by updating one outdated example in the SC 3.3.2 (Labels or Instructions) Understanding document.
The previous example referenced invisible labels using the
titleattribute for multi-part phone fields, which is misleading in this context.This change keeps the existing example structure and intent, but replaces that wording with explicit visual-label wording for each phone-field segment.
File Changed
understanding/20/labels-or-instructions.htmlOriginal vs Corrected Example Snippet
Original (before)