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

Address accessibility issues #92

Open
npm1 opened this issue Aug 11, 2020 · 0 comments
Open

Address accessibility issues #92

npm1 opened this issue Aug 11, 2020 · 0 comments

Comments

@npm1
Copy link
Collaborator

npm1 commented Aug 11, 2020

Based on #91 (comment). Assistive devices could trigger synthetic input events while skipping the hardware input events that this API cares about. This means that we may not be exposing performance data for users of those devices. The tricky part is exposing meaningful information (for instance, is the Event timeStamp still representative of the time in which the user interacted with the page, or would some other timestamp need to be used instead)? We should dig some data about how often this occurs, what kinds of events are triggered this way, and based on that update the spec.

In the interim, we could add an a11y section and link to this issue.

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

No branches or pull requests

1 participant