-
Notifications
You must be signed in to change notification settings - Fork 841
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
(Accessibility) Fix EuiNavDrawerFlyout using <h5>
by replacing with <div>
#2040
Conversation
<h5>
by replacing with <div>
jenkins, test this |
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.
Checked this out locally and it looks good.
It does make me wonder if we're offering a subpar experience for screenreader users given our lack of proper headings, generally speaking. Then again, we don't have control of content and each app is quite different, so I don't see how we could keep that organized enough to be accessible and useful.
One other thought, @snide should we be labeling the EuiNavDrawer
as a main navigation region in Kibana?
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 agree with @ryankeairns that more thought should be put into the full accessibility (screen-reader) experience of the nav drawer in association with the application it sits within.
Co-Authored-By: Caroline Horn <549577+cchaos@users.noreply.github.com>
Fixes #2039
Associated issue: elastic/kibana#34995
Summary
This PR replaces
<h5>
with<div>
and that's it.Checklist
This was checked in mobileThis was checked in IE11This was checked in dark modeAny props added have proper autodocsDocumentation examples were addedThis was checked for breaking changes and labeled appropriatelyJest tests were updated or added to match the most common scenariosThis required updates to Framer X components