-
Notifications
You must be signed in to change notification settings - Fork 628
Banner: Should prefer aria-labelled-by over aria-label #6701
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
Conversation
🦋 Changeset detectedLatest commit: eeba853 The changes in this PR will be included in the next version bump. This PR includes changesets to release 2 packages
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 |
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.
Pull Request Overview
This PR fixes an accessibility issue in the Banner component by implementing proper precedence for aria labeling attributes. When both aria-labelledby
and aria-label
are provided, the component now prioritizes aria-labelledby
and conditionally sets aria-label
only when aria-labelledby
is not present.
- Adds support for
aria-labelledby
prop extraction and conditional aria attribute setting - Implements proper accessibility precedence where
aria-labelledby
takes priority overaria-label
- Adds comprehensive test coverage for the new labeling behavior
Reviewed Changes
Copilot reviewed 2 out of 2 changed files in this pull request and generated no comments.
File | Description |
---|---|
packages/react/src/Banner/Banner.tsx | Extracts aria-labelledby prop and implements conditional logic to prevent both aria attributes from being set simultaneously |
packages/react/src/Banner/Banner.test.tsx | Adds test cases to verify proper aria attribute precedence and that only one labeling method is used at a time |
👋 Hi, this pull request contains changes to the source code that github/github depends on. If you are GitHub staff, we recommend testing these changes with github/github using the integration workflow. Thanks! |
size-limit report 📦
|
The failure in the integration tests is unrelated to this PR and I'm investigating it separately. |
😢 Hi from github/github-ui. The integration workflow has failed: https://github.com/github/github-ui/actions/runs/17419544075 |
Part of https://github.com/github/primer/issues/5628
During a migration effort on github-ui, I found that a test there was failing due to
Banner
setting botharia-labelled-by
andaria-label
Changelog
New
Changed
Removed
Rollout strategy
Testing & Reviewing
Merge checklist