-
Notifications
You must be signed in to change notification settings - Fork 115
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
Docs: update accessibility section of PVC Banner #2620
Docs: update accessibility section of PVC Banner #2620
Conversation
🦋 Changeset detectedLatest commit: fc74138 The changes in this PR will be included in the next version bump. This PR includes changesets to release 1 package
Not sure what this means? Click here to learn what changesets are. Click here if you're a maintainer who wants to add another changeset to this PR |
# Focusing a Banner when it appear helps to maximize discoverability of the message, especially in critical scenarios. | ||
# | ||
# To properly focus a banner, add a `tabindex="-1"` to the Banner container, and focus that container (one way is using the [`focus()` API](https://developer.mozilla.org/en-US/docs/Web/API/HTMLElement/focus)). | ||
# | ||
# For more information about the focus management technique, visit the [Staff only: Accessible Banner Prototype docs](https://github.com/github/accessibility/blob/main/docs/coaching-recommendations/toast-flash-banner/accessible-banner-prototype.md#consideration). This guidance is subject to change. |
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.
Focus content should not have changed, except I added a Staff only
to the link!
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, yay!
Co-authored-by: Lindsey Wild <[email protected]>
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 working on this!
Co-authored-by: Cameron Dutro <[email protected]>
Co-authored-by: Cameron Dutro <[email protected]>
Accepted your suggestions! Thanks for reviewing @camertron! |
Looks like we're seeing some breakage because of a change to Rails main. I'm going to merge this and address those failures in a follow-up PR. |
Authors: Please fill out this form carefully and completely.
Reviewers: By approving this Pull Request you are approving the code change, as well as its deployment and mitigation plans.
Please read this description carefully. If you feel there is anything unclear or missing, please ask for updates.
What are you trying to accomplish?
The Banner currently lacks accessibility guidance, and we've seen Banner come up in a few audit issues.
To help unblock existing audit issues and to prevent future audit issues, this PR provides accessibility guidance including:
List the issues that this change affects.
Fixes: https://github.com/github/accessibility/issues/5649
Risk Assessment
be resolved below.
Merge checklist
Take a look at the What we look for in reviews section of the contributing guidelines for more information on how we review PRs.