Repository navigation
chore(docs): updated standards to wcag 22 - #4762
Merged
Merged
Conversation
Collaborator
edonehoo
requested changes
Sep 2, 2025
edonehoo
left a comment
edonehoo
left a comment
Collaborator
There was a problem hiding this comment.
Couple small things, but otherwise this looks good to me!
| - Interactive elements that display in a pop-up must also display on click, touch, or enter-key events. | ||
|
|
||
| - Screen reader content should match visibly rendered content (refer to the [first note for `aria-hidden` state](https://www.w3.org/TR/wai-aria/#aria-hidden)). | ||
| - Screen reader content should match visibly rendered content (refer to the [first note for `aria-hidden` state](https://www.w3.org/TR/wai-aria/#h-note-59) - keep in mind this references an older version of WCAG guidelines). |
Collaborator
There was a problem hiding this comment.
Suggested change
| - Screen reader content should match visibly rendered content (refer to the [first note for `aria-hidden` state](https://www.w3.org/TR/wai-aria/#h-note-59) - keep in mind this references an older version of WCAG guidelines). | |
| - Screen reader content should match visibly rendered content (refer to the [first note for `aria-hidden` state](https://www.w3.org/TR/wai-aria/#h-note-59), but keep in mind this references an older version of WCAG guidelines). |
| When a `label` element cannot accompany a form input element, provide one using using `aria-label` or `aria-labelledby`, as outline by the [WCAG technique ARIA14](https://www.w3.org/WAI/WCAG22/Techniques/aria/ARIA14). | ||
|
|
||
| In a single-field form, the submit button label can serve as the field label for sighted users, [following the "G167" guidelines](//www.w3.org/TR/WCAG20-TECHS/general.html#G167). For assistive devices, use `aria-labelledby`. | ||
| In a single-field form, the submit button label can serve as the field label for sighted users, followwing the [WCAG technique G167](https://www.w3.org/WAI/WCAG22/Techniques/general/G167). For assistive devices, use `aria-labelledby`. |
Collaborator
There was a problem hiding this comment.
Suggested change
| In a single-field form, the submit button label can serve as the field label for sighted users, followwing the [WCAG technique G167](https://www.w3.org/WAI/WCAG22/Techniques/general/G167). For assistive devices, use `aria-labelledby`. | |
| In a single-field form, the submit button label can serve as the field label for sighted users, following the [WCAG technique G167](https://www.w3.org/WAI/WCAG22/Techniques/general/G167). For assistive devices, use `aria-labelledby`. |
Contributor
Author
There was a problem hiding this comment.
My w key has been my bane for a while now because of this 😭
| [Use label elements to associate text labels with form controls](https://www.w3.org/WAI/WCAG22/Techniques/html/H44) (such as `input`, `textarea`, or `select`) when both are present. This technique provides an accessible name to screen readers and makes the label clickable to increase the overall clickable area of the form element. | ||
|
|
||
| When a `label` element cannot accompany a form input element, provide one using using `aria-label` or `aria-labelledby`, as outline by the ["ARIA14" guidelines](//www.w3.org/TR/WCAG20-TECHS/ARIA14.html). | ||
| When a `label` element cannot accompany a form input element, provide one using using `aria-label` or `aria-labelledby`, as outline by the [WCAG technique ARIA14](https://www.w3.org/WAI/WCAG22/Techniques/aria/ARIA14). |
Collaborator
There was a problem hiding this comment.
Suggested change
| When a `label` element cannot accompany a form input element, provide one using using `aria-label` or `aria-labelledby`, as outline by the [WCAG technique ARIA14](https://www.w3.org/WAI/WCAG22/Techniques/aria/ARIA14). | |
| When a `label` element cannot accompany a form input element, provide one using using `aria-label` or `aria-labelledby`, as outlined by the [WCAG technique ARIA14](https://www.w3.org/WAI/WCAG22/Techniques/aria/ARIA14). |
edonehoo
approved these changes
Sep 4, 2025
nicolethoen
approved these changes
Sep 5, 2025
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
4 participants
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 #4763