Secure connection
Required by several browser device features.
Input path check · one decision report
Game Input Readiness Scan
Runs the quick checks together and tells you what to look at first.
Readiness field scanCapabilities + manual evidence · local only
0/100 observed
Evidence not collected
The score counts only browser-observed capabilities and confirmed manual checks. Missing APIs remain visible.
Pointer events
Mouse and multi-touch event path.
Keyboard interaction
Press any non-reserved key after scanning.
Gamepad connection
Connect a pad and press a button.
Touch surface
Browser-reported touch points and coarse pointer.
Motion API
Availability only; permission is tested in the mobile lab.
Next action
Run the scan to receive a device-specific path.
Polling rate (Hz)
How many times per second the mouse tells the computer where it is. 1000 Hz means once every millisecond. The browser can only see what the operating system passes on, which is often less than the hardware sends.
Input latency
The delay between your action and the result appearing. What a browser can see is one slice of it: the event arriving and the next frame being drawn.
Stick drift
The controller reporting movement while you are not touching the stick. A worn or badly calibrated stick never returns to exactly zero.
Rollover / NKRO
How many keys a keyboard can report at once. 6KRO handles six plus modifiers; NKRO means every key can be pressed together.
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.
KEYMAP / NEXT
Related labs
Move from observation to a narrower diagnostic without losing context.
01
Gaming Input Problem Solver
Turn “my controls feel wrong” into a reproducible decision tree for controller, keyboard, mouse or touch problems.
02Gamepad Tester
Watch every button, stick and trigger light up on a drawn PS5, Xbox or Switch pad, then test vibration, report rate and stick circularity — nothing to install, nothing uploaded.
03Keyboard Tester
See every press, release, repeat and simultaneous key on a live keyboard map — ANSI, ISO or JIS, labelled with your own layout where the browser allows — and find the combinations your board drops.
04Mouse Tester
Check primary, secondary, middle and auxiliary buttons, wheel direction and press duration in one focused test surface.
