Motion Data Is Permission-Dependent
A gyroscope test is different from an ordinary button check because motion reports are not consistently exposed through the standard Gamepad API. Some controllers include gyro sensors, but the browser may only expose buttons and sticks unless optional APIs such as WebHID are available. This gyroscope test shows capability state clearly and requests HID permission only after a deliberate click.
The motion controller test includes a tilt model so the page remains understandable even when direct gyro reports are unavailable. In fallback mode, stick axes drive the model and the page labels that behavior. That keeps the visual useful for interface review while avoiding false claims that real sensor data is present.
For compatible controllers, HID access may reveal additional data, but device support is fragmented across browsers and operating systems. A controller gyro test should therefore set careful expectations: it can check permission, visualize motion paths when available, and identify unsupported states, but it cannot guarantee console-level motion features.