-
Notifications
You must be signed in to change notification settings - Fork 538
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
PageHeader: Address general sign-off review feedback in storybook (missing href values, non-working menus) #3817
Conversation
This reverts commit 1a17796.
|
size-limit report 📦
|
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.
The updates look fine to me based on your comments here.
</Breadcrumbs> | ||
<VisuallyHidden as="h2">Visually Hidden Title</VisuallyHidden> | ||
<VisuallyHidden as="h2">PageHeader.tsx</VisuallyHidden> |
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.
Should this be h1
as well?
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.
Ah my bad. I just read your replies to @jscholes. I see this is intentional
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.
Oh good catch! @pksjce
Just to clarify, the h2
intentional ones I mentioned in my response are the ones under the settings page (reference)
Looking at the current files page implementation, seems like it has changed since I built this component and stories and it should be h1. However, we will address the cases where breadcrumb components are used as a title in the following PageHeader PR and the structure will change a bit, so I think we can leave this as is to reduce the number of merge conflicts if that is okay?
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.
Yes! That seems fine with me. This one is good to merge 👍
As a part of addressing accessibility sign-off review comments https://github.com/github/primer/issues/1115#issuecomment-1499501472
Changelog
New
Changed
Removed
Rollout strategy
Testing & Reviewing
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.