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

Security feature blocks accessibility: Can't enter VR mode with fuse button #27

Open
DougReeder opened this issue Oct 29, 2020 · 1 comment

Comments

@DougReeder
Copy link

Use Case: Users with limited dexterity can use a headset, but not buttons, either on the headset or on controllers. (For example, users with Parkinson's, or who do not currently have use of their hands.)

UI both outside and inside VR can be implemented with fuse buttons (where the user places the pointer on a button for some predetermined length of time). This can be implemented with JavaScript, wherein the code creates a click event at the appropriate time. Unfortunately, this runs afoul of the security requirement that requestPresent() be called in a user-interaction handler, like a click handler.

For the immersive web to be accessible to all, there needs to be an approach to allow users who can only control their head to enter VR mode, and other transitions that require user assent, like starting audio play.

A narrow solution would be a browser flag to disable this security requirement.

A broader solution would a mechanism to extend the browser. Such a mechanism may already exist for the flat web.

@DougReeder
Copy link
Author

The narrow solution exists for Firefox Reality: setting the configuration flag dom.vr.require-gesture to false allows this.

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