-
Notifications
You must be signed in to change notification settings - Fork 180
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(side-navbar): keyboard a11y #222
base: master
Are you sure you want to change the base?
Conversation
replace div with button to allow activation using space and enter Signed-off-by: Gaurav Gupta<[email protected]>
14f8b22
to
6c1c260
Compare
This comment was marked as resolved.
This comment was marked as resolved.
Looks like DCO is missing a space (between name and the |
Thanks for reopening this, I might find time to fix the DCO issue and rebase this |
This comment was marked as resolved.
This comment was marked as resolved.
This comment was marked as resolved.
This comment was marked as resolved.
This comment was marked as resolved.
This comment was marked as resolved.
I think that this would also make the buttons clickable with vimium! |
@@ -35,10 +35,10 @@ export const NavBar: React.FunctionComponent<NavBarProps> = (props: NavBarProps, | |||
<div className='nav-bar__version'>{props.version && props.version()}</div> | |||
{(props.items || []).map((item) => ( | |||
<Tooltip content={item.title} placement='right' arrow={true} key={item.path + item.title}> | |||
<div className={classNames('nav-bar__item', { active: isActiveRoute(locationPath, item.path) })} | |||
<button type="button" className={classNames('nav-bar__item', { active: isActiveRoute(locationPath, item.path) })} |
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.
I think this can actually just use a <Link>
element from react-router
, which would also solve #166
replace div with button to allow activation using space and enter.
This fixes one of the issues mentioned in #221