-
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: Added side navigation accessibility test page #2864
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.
Thanks for creating this @RachelCorsino.
I've updated the base branch, made some formatting edits, and made two small suggestions.
…s-site into rc-side-nav-checklist
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! One small change and one question for a11y
| - summary: Focus indicator is clearly visible in side navigation. | ||
| summary_additional: When you use a keyboard to tab into the side navigation, the links have a visible underline, bold style or other clear indication that links are interactive. | ||
| test_status: pass | ||
| test_type: keyboard | ||
| version_tested: 3.8.2 | ||
| wcag_criterion: 2.4.7 |
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.
question (non-blocking): Was there a reason we changed the Gherkin for focus indicators? This mentions a visible underline and bold style but neither is the default for focus indicators. Most of our other descriptions for 2.4.7 read:
Focus indicator is clearly visible. When you use a keyboard to navigate through the header, there will be a visible outline or other clear indication where the the focus is.
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.
Hmm...I'm not sure why that one got changed. I think it should reflect the way others have been written. The previous way potentially helps with some generalizing, versus tying people to those options.
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.
Let me know if this change is what you had in mind! 77b383e
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.
Code looks good and follows standards. Re-running CI checks because of a potential timeout.
| githubPr: 4163 | ||
| githubRepo: uswds | ||
| versionUswds: 2.11.2 | ||
| - date: NNNN-NN-NN |
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.
chore: Will need to add date before final merge.
| title: Side navigation accessibility tests | ||
| type: component | ||
| items: | ||
| - date: NNNN-NN-NN |
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.
chore: Will need to add date before final merge.
|
Also updated the test status for |
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.
Looks good! Approved!
Summary
Added accessibility test page for side navigation component
Related issue
Closes #2857
Preview link
Preview link: Side Navigation Component Page
Testing and review
Follow these steps: