Re: [w3c/gamepad] Add a model section (PR #220)

@nondebug commented on this pull request.



> +        [=gamepad=]. The content is decided by the [=user agent=].
+      </p>
+      <section>
+        <h3>
+          Input control layout
+        </h3>
+      <p>
+        A [=gamepad=] may have an <dfn>input control layout</dfn> that describes the position, orientation and type of each [=input control=] on the [=gamepad=].
+        The [=user agent=] is responsible for recognizing when a [=gamepad=] <dfn data-lt="corresponds with">corresponds with a standard layout</dfn>, meaning the [=gamepad=] has an [=input control layout=] that enables it to be used interchangeably with other [=gamepads=] that correspond with the same standard layout.
+        The [=user agent=] SHOULD consider a layout to correspond with a standard layout if its [=input controls=] have approximately the same relative positions and orientations as [=input controls=] described in the standard layout.
+      </p>
+      <p>
+        The [=user agent=] typically cannot directly inspect the [=input control layout=] for a [=gamepad=] and MAY use heuristics to decide the layout.
+        The [=user agent=] SHOULD consider the device identifiers when deciding whether a [=gamepad=] [=corresponds with a standard layout=].
+        If the system assigns a label to each [=input control=] and the labels imply a particular layout then the [=user agent=] SHOULD consider the [=gamepad=] to have that layout.
+        When there is a standard model and an accessible model with the same [=input controls=], the [=user agent=] SHOULD consider the accessible model to have the same [=input control layout=] as the standard model.

I was thinking of gamepads like Xbox Adaptive Controller and PlayStation Access where the manufacturer's intent is a swap-in replacement for a gamepad with a standard layout. We should handle these accessibility-focused devices as if they the same input control layout as the non-accessible version of the gamepad (Xbox Wireless Controller or DualSense) even though the physical layout of of the input controls doesn't match the standard layout.

-- 
Reply to this email directly or view it on GitHub:
https://github.com/w3c/gamepad/pull/220#discussion_r2124620626
You are receiving this because you are subscribed to this thread.

Message ID: <w3c/gamepad/pull/220/review/2893644824@github.com>

Received on Tuesday, 3 June 2025 18:30:49 UTC