[react-events] Support screen reader virtual clicks#16584
Merged
trueadm merged 3 commits intofacebook:masterfrom Aug 27, 2019
Merged
[react-events] Support screen reader virtual clicks#16584trueadm merged 3 commits intofacebook:masterfrom
trueadm merged 3 commits intofacebook:masterfrom
Conversation
Details of bundled changes.Comparing: 0da7bd0...7a8b04f react-events
Generated by 🚫 dangerJS |
necolas
reviewed
Aug 27, 2019
necolas
approved these changes
Aug 27, 2019
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This PR aims to address issues around using screen reader tooling (VoiceOver, NVDA, JAWS) with the
Pressevent responder. We previously relied on "press" events firing when coming from a valid pointer/mouse/touch sequence of events. We also supported "Enter" and "Space" keyboard events. However, we did not take into account that screen reader tooling can also fire virtualclickevents to specific DOM nodes.Screen reader virtual click events have a pattern that makes them somewhat easy to detect. They seem to also have
0as thenativeEvent.detail, rather than1and they also never provide screen co-ordinates (they are all always0).Testing URL: https://m9zxnyvpj9.csb.app/