Skip to content
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

a11y: fix NavItem a11y issues #2502

Merged
merged 15 commits into from
Apr 8, 2020
Merged

a11y: fix NavItem a11y issues #2502

merged 15 commits into from
Apr 8, 2020

Conversation

beyackle
Copy link
Contributor

@beyackle beyackle commented Apr 3, 2020

Description

It was much easier to fix the problems in NavItem than to rip it out and replace it with a Nav (thanks to the still-unaddressed issues in Nav with SPA react-router-style links), so after fixing up the CSS and removing the unneeded button component, this was the result.

Task Item

Closes #2025
Closes #2040

Screenshots

image

@github-actions
Copy link

github-actions bot commented Apr 3, 2020

Coverage Status

Coverage increased (+0.03%) to 39.654% when pulling b03c2f8 on beyackle/navbar2 into 313a6b1 on master.

Copy link
Contributor

@a-b-r-o-w-n a-b-r-o-w-n left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The font size is larger now. I'm not sure if that is intentional or not, but it differs from master:

Image 2020-04-06 at 8 24 09 AM

@beyackle
Copy link
Contributor Author

beyackle commented Apr 6, 2020

Fixed the E2E tests, and adjusted the font size back to normal:
image

@a-b-r-o-w-n
Copy link
Contributor

The other thing I notice is that the active element is offset with respect to the other links.

image

@corinagum
Copy link
Contributor

corinagum commented Apr 8, 2020

@beyackle gentle ping :) Oops, I didn't see Chris had made changes. Will validate asap.

@cwhitten
Copy link
Member

cwhitten commented Apr 8, 2020

I changed the margin when active

@beyackle
Copy link
Contributor Author

beyackle commented Apr 8, 2020

Thanks for taking care of that - this slipped my mind while I was working on the labels thing.

@beyackle
Copy link
Contributor Author

beyackle commented Apr 8, 2020

That E2E failure is the exact same one I'm seeing on my other PR, too. The "SaveAs" task, which I haven't touched and which I was able to manually step through and it seems like it should work.

@corinagum
Copy link
Contributor

I pulled this and tested locally. LGTM.

Not sure about the failing test. @cwhitten is this related to the test failures you mentioned in our 1:1 yesterday?

@cwhitten
Copy link
Member

cwhitten commented Apr 8, 2020

Yea @a-b-r-o-w-n is fixing that

@cwhitten cwhitten merged commit aca7358 into master Apr 8, 2020
@cwhitten cwhitten deleted the beyackle/navbar2 branch April 8, 2020 22:35
lei9444 pushed a commit to lei9444/BotFramework-Composer-1 that referenced this pull request Jun 15, 2021
* fix NavItem a11y issues

* Update styles.ts

* fix NavItem a11y issues

* Update styles.ts

* Update styles.ts

* move data-testid

* Fix selected offset in left nav

Co-authored-by: Andy Brown <asbrown002@gmail.com>
Co-authored-by: Chris Whitten <christopher.whitten@microsoft.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants