-
-
Notifications
You must be signed in to change notification settings - Fork 4.3k
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: improve a11y-click-events-have-key-events message #9358
Conversation
🦋 Changeset detectedLatest commit: 097255c The changes in this PR will be included in the next version bump. This PR includes changesets to release 1 package
Not sure what this means? Click here to learn what changesets are. Click here if you're a maintainer who wants to add another changeset to this PR |
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.
Thank you, for taking the initiative in trying to tackle this.
While this is better, it unfortunately still has issues:
- The keyboard events will do nothing unless the element or one of the descendants is focused (by default, non-interactive elements will not be focusable)
- The message does not explain that the keyboard handlers should enable the user to perform equivalent actions via the keyboard.
Because this is a lot, I was wondering whether delegating to the documentation for further explanation might be an option.
Speaking of which, the documentation at /docs/05-misc/02-accessibility-warnings.md
should also be updated accordingly.
Thanks for the review! Updated as suggested! |
fixes #8001
closes #8273
it's longer message, but at least it's useful now