You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We have reviewed the WebXR Gamepads Module - Level 1, and we have a concern that OS- or UA-level button remapping would be important for accessibility support. Whilst remapping is generally better done within an app/game, users need to have a fallback in case the app/game doesn't support it. (We note that there is a "Remapping" section in the related Gamepad spec from the WebApps WG, but it doesn't seem to cover user-controllable remapping.)
This could be discussed in an "Accessibility Considerations" section, but we believe you might find it preferable to add such a section to the parent API specification (WebXR Device API) rather than to this module document. If you prefer to address Accessibility Considerations in the parent API specification, we would note that there may be additional concerns we would want to have addressed before the API is finalized, but starting that process now would satisfy our concern with the current module. We are open to your proposal for a resolution to our concern.
from w3c/a11y-request#30 (comment)
We have reviewed the WebXR Gamepads Module - Level 1, and we have a concern that OS- or UA-level button remapping would be important for accessibility support. Whilst remapping is generally better done within an app/game, users need to have a fallback in case the app/game doesn't support it. (We note that there is a "Remapping" section in the related Gamepad spec from the WebApps WG, but it doesn't seem to cover user-controllable remapping.)
This could be discussed in an "Accessibility Considerations" section, but we believe you might find it preferable to add such a section to the parent API specification (WebXR Device API) rather than to this module document. If you prefer to address Accessibility Considerations in the parent API specification, we would note that there may be additional concerns we would want to have addressed before the API is finalized, but starting that process now would satisfy our concern with the current module. We are open to your proposal for a resolution to our concern.
Link to the decision on the call for consensus, on the APA-admin mailing list
The text was updated successfully, but these errors were encountered: