WebXR Gamepads Module Level 1 2021-05-23 > 2021-07-23

[himorin]

In the issue title above add the document name followed by the date of this request, then the date of your proposed deadline for comments.

• name of spec to be reviewed: WebXR Gamepads Module - Level 1

• URL of spec: https://www.w3.org/TR/2022/WD-webxr-gamepads-module-1-20220426/

• What and when is your next expected transition? as soon as HR finished

• What has changed since any previous review? first a11y review

• Please point to the results of your own self-review (see https://w3c.github.io/apa/fast/checklist.html) a11y short check list immersive-web/webxr-gamepads-module#55

• Where and how to file issues arising? https://github.com/immersive-web/webxr-gamepads-module/issues

• Pointer to any explainer for the spec? https://github.com/immersive-web/webxr-gamepads-module/blob/main/gamepads-module-explainer.md

Other comments:

[michael-n-cooper]

@Matatak to review. Also see https://www.w3.org/WAI/APA/wiki/WebXR_Gamepads_Module_-_Level_1

[himorin]

hi @Matatak , if there is any update, we are really appreciated.

Sorry for late catch, but it seems I've wrote wrong year at the title... 2021 should be 2022

[himorin]

hi @Matatak @michael-n-cooper , we are really appreciated if there is any update on this HR request. thank you.

[michael-n-cooper]

@himorin, @Matatak will take a look by next weeek

[matatk]

Hi @himorin. I'm sorry for the delay in my review! We discussed the spec on our APA WG call today, and are running a call for consensus on some proposed feedback (we do expect to have some feedback, though it is not huge in scope). We will update you on Monday with the result. Again, apologies for the delay.

[matatk]

Hi @himorin. Here's APA's comment, following our review:

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