-
Notifications
You must be signed in to change notification settings - Fork 0
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 / header navigation list (accessibility) #173
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.
Nice!
- We should be aware that your change breaks other platforms (/repositories) that use
<Header />
. - Snapshots need an update
@royschut thanks for you feedback!
Yes. Therefore I suggest submitting this PR isolated. I think there is no other way around it if we want to aim for an adequate solution. |
@langemike, can we merge this to the accessibility branch or submit a PR to the public repo? |
@ChristiaanScheermeijer I will do that, after I I fixed some rework bugs. |
fd2545f
to
4a5eac4
Compare
4a5eac4
to
dc9614c
Compare
Merged in base repo. |
This change wraps header navigation items within a list. We got this feedback from an accessibility auditor.
I did not want to apply "reset" styles to the
<ul>
withinLayout.module.scss
, because it belongs in theHeader.module.scss
. So I refactored the Header component to make this possible. I have also moved the.headerButton
CSS code toHeader.module.scss
to separate the concerns.I think we should submit this as an isolated PR to the JW team, because of the small refactor.
Ticket: OTT-1230