-
Notifications
You must be signed in to change notification settings - Fork 148
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
USWDS-Site - Add text input accessibility tests page #2697
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Added one comment about a WCAG label. So far so good otherwise.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looking good! I added some questions and comments below. Let me know if you have any questions.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM!
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looking good! Added just a couple of small questions in the comments.
…1y-checklist-text-input
Co-authored-by: Amy Leadem <93996430+amyleadem@users.noreply.github.com>
Co-authored-by: Amy Leadem <93996430+amyleadem@users.noreply.github.com>
|
@amyleadem I liked the summary changes and merged them! Ready for re-review 👍 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks good to me! Thanks! Before merge, I'd like to have @amycole501 or @alex-hull sign off on the updated summary for 1.3.3.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Instructions that use visual cues also provide non-visual instruction. If you use visual cues like shapes or locations to describe controls (e.g., “input below”), also provide extra instructions explaining how to access the text input. This way, users who can’t see shapes or locations can still understand how to use the controls.
|
Ready for your review @thisisdano ! |
| - date: NNNN-NN-NN | ||
| summary: Added WCAG compliance tag and accessibility test status section. | ||
| affectsGuidance: true | ||
| githubPr: 2697 | ||
| githubRepo: uswds-site |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Important
Flagging that both changelog dates needs to be updated before merge
|
Note: I just moved this issue to fed final since it looks like it is ready for fed review |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Update changelog publish dates
Summary
Added accessibility tests page for the text input component.
Important
Build errors due to broken links will be resolved in #2692
We should update changelog dates before merging.
Related issue
Closes #2628
Preview link
Resources
Testing and review
1.3.3and1.3.4wcag criterion is accurate and link works