Update 3.3.2 understanding doc and g167 technique #4102
+25
−3
Conversation
This file contains 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 site configuration. |
as not everyone might read this page and then check out every technique to then find the updated G167, I've added two new written examples to the understanding doc as well. (though the one about when instructions might be needed or not is a bit out of scope for this PR, i still thought it might be a nice addition... we can pull it out if people disagree or don't want scope creep)
scottaohara
changed the title
bruce-usab
approved these changes
Oct 18, 2024
giacomo-petri
approved these changes
Oct 21, 2024
Co-authored-by: Giacomo Petri <giacomo.petri@usablenet.com>
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.
closes #4088
includes new icon-button example in G167 to showcase how a button represented by an icon alone can be used in certain instances for labeling form fields
also updates the understanding doc to provide two new written examples to the examples section list.
One to not make someone have to know to look to g167 to understand that "icons" can also serve as labels
And the second to provide an example of how two websites could have the same sort of input, but one needs instructions (due to extra requirements) while another doesn't (because they are super chill).