-
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
Adding a11y tests and moving from whitelist to blacklist + misc fixes #3502
Conversation
Preview documentation changes for this PR: https://eui.elastic.co/pr_3502/ |
The title of this PR could be more specific.
I think this is fine and agree that it's not correct for all implementations. I think we should also then add some accessibility guidelines to their docs page around what to add if:
🙏 Thank you! This makes way more sense and I'm definitely in the group of people who forget to add to this list. |
😆 The title of the PR was terrible. My bad, it's better now.
I added a note about what to do if it's a bunch of links but I couldn't think of any good broad guidelines that I could give about the buttons use case. Anything I could think of had plenty of exceptions so I just didn't mention it. I don't think anything should be super broken if they don't do anything but it could be if they do the wrong thing so I thought rather overly simplified is better than misleading. |
Preview documentation changes for this PR: https://eui.elastic.co/pr_3502/ |
@@ -87,7 +87,7 @@ describe('EuiKeyPadMenuItem', () => { | |||
</EuiKeyPadMenuItem> | |||
); | |||
|
|||
$button.simulate('click'); | |||
$button.find('button').simulate('click'); |
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.
To make the test read more appropriately can you change the const name to $item
instead of $button
?
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.
This also might break downstream app tests, do we then consider this a breaking change @chandlerprall ?
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.
This was reverted by moving the <li>
wrapping element to the parent component
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.
Somehow it still exists as changed?
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.
@myasonik Can you remove this change, it shouldn't be necessary anymore.
Co-authored-by: Caroline Horn <549577+cchaos@users.noreply.github.com>
Preview documentation changes for this PR: https://eui.elastic.co/pr_3502/ |
Preview documentation changes for this PR: https://eui.elastic.co/pr_3502/ |
Preview documentation changes for this PR: https://eui.elastic.co/pr_3502/ |
Preview documentation changes for this PR: https://eui.elastic.co/pr_3502/ |
Preview documentation changes for this PR: https://eui.elastic.co/pr_3502/ |
Looks like there's another/new a11y issue:
Probably my bad... |
Preview documentation changes for this PR: https://eui.elastic.co/pr_3502/ |
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.
Thanks! LGTM!
Summary
This PR does 2 things.
menu
andmenuitem
roles from KeyPadMenu and KeyPadMenuItem.Checklist
- [ ] Check against all themes for compatibility in both light and dark modes- [ ] Checked in mobile- [ ] Checked in IE11 and Firefox- [ ] Props have proper autodocs- [ ] Added documentation examples