-
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
Fix underline behavior in Link component #2249
Conversation
🦋 Changeset detectedLatest commit: 00f67db 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 |
|
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.
🤘🏻 Lovely fix
@camertron This has resulted in underlines being rendered on hover when |
Uh oh! @kintner, the image you shared is missing helpful alt text. Check #2249 (comment). Alt text is an invisible description that helps screen readers describe images to blind or low-vision users. If you are using markdown to display images, add your alt text inside the brackets of the markdown image. Learn more about alt text at Basic writing and formatting syntax: images on GitHub Docs. |
What are you trying to accomplish?
The
Primer::Beta::Link
component does not render an underlined link when theunderline: true
argument is passed. I'm not sure why, since links are underlined by default. This PR makes the underlining explicit and stops using the primer/css.no-underline
utility class. It also setsunderline: false
as the default, since that's the current behavior anyway, and will likely result in sweeping (and potentially unwanted) changes to dotcom.Screenshots
Integration
No changes necessary in production.
Risk Assessment
Accessibility
Underlining links when they are surrounded by other text is considered an accessibility best-practice. So, while this change does not fix any axe violations, it is more accessible and may impact teams' scorecards positively.
Merge checklist
- [ ] Added/updated documentation- [ ] Added/updated previews (Lookbook)Take a look at the What we look for in reviews section of the contributing guidelines for more information on how we review PRs.