Game Input Readiness Scan

How to use: Game Input Readiness Scan

Choose the platform, game type and primary input method.

Run the browser scan, interact with the selected device and complete the manual checks.

Export the local report or open the exact follow-up lab selected from the findings.

What the result actually measures

The scan inventories browser-exposed gamepad, keyboard, pointer, touch, motion, vibration and screen capabilities. It combines that inventory with your platform and intended input method to produce explicit passed, manual-check and unavailable states.

Measurement boundary: Capability detection shows what this browser exposes, not whether a specific game supports the device or whether hardware meets a laboratory latency specification.

How to interpret the output

Ready

The browser exposes the required API and received the expected interaction in this session.

Manual check

The browser cannot decide the condition automatically; the report keeps the unresolved step visible.

Unavailable

The capability is absent or blocked in this context. This does not alone prove a device fault.

Troubleshooting unexpected results

Controller stays hidden

Press a controller button, keep the tab focused, try wired mode and close software that may hold exclusive access.

Motion is unavailable

Use a secure mobile context, request permission from the tool button and test a current mobile browser.

Frequently asked questions

Does the readiness score certify my setup?

No. It summarizes browser-observed capabilities and completed checks with every unresolved limitation shown.

Is the report uploaded?

No. The scan and JSON export are created in the browser.

Why does a console selection still use browser tests?

The browser screens the connected hardware; the target console and game still require their own compatibility check.