- From: Matthew Tylee Atkinson <matkinson@paciellogroup.com>
- Date: Tue, 11 Feb 2020 17:14:37 +0000
- To: public-immersive-web-wg@w3.org
- Cc: W3C WAI Accessible Platform Architectures <public-apa@w3.org>
Hello Immersive Web WG, We in the Accessible Platform Architectures WG have been reviewing the WebXR Gamepads Module - Level 1 from an accessibility perspective, and there were a couple of things we’d like to clarify. We’d be grateful if you could provide any info on the following. 0. From the spec itself, and its description on GitHub, we gather that the purpose of this spec is to give WebXR developers a familiar API (the Gamepad API) to use to query the state of XR-specific controller/input devices. (I.e. the purpose is _not_ to support general gamepads _as_ XR controllers.) Assuming that we understood this correctly... 1. Have you considered supporting non-XR-specific controllers as XR input devices? This may include devices such as general gamepads and the Xbox Adaptive Controller. Issue 392 [0] discusses pros and cons of using the Gamepad API, and mentions accessibility. I was wondering if there's been any related discussion since the Gamepad API approach was adopted in PR 499? Thanks for any info you may be able to provide on the above. best regards, Matthew [0] https://github.com/immersive-web/webxr/issues/392 -- Matthew Tylee Atkinson -- Senior Accessibility Engineer The Paciello Group https://www.paciellogroup.com A Vispero Company https://www.vispero.com/ -- This message is intended to be confidential and may be legally privileged. It is intended solely for the addressee. If you are not the intended recipient, please delete this message from your system and notify us immediately. Any disclosure, copying, distribution or action taken or omitted to be taken by an unintended recipient in reliance on this message is prohibited and may be unlawful.
Received on Tuesday, 11 February 2020 17:14:43 UTC