Inside the Input Readiness Score: Evidence, Limits and Weighting

The score summarizes states, not hardware quality

A ready state means the required browser capability exists or an expected interaction reached the page. A manual state means the browser cannot decide the condition automatically. Unavailable means the API or signal is absent in this context.

Relevant checks are weighted equally in the current score: ready contributes one point, manual contributes less than half and unavailable contributes zero. Motion is excluded from non-touch paths. The labels remain visible so the total cannot hide unresolved conditions.

Device-specific relevance changes the denominator

A mouse-and-keyboard setup does not fail because a gamepad is disconnected. A touch setup does need its touch and motion states shown. The selected primary input determines which checks affect the score and which remain informational.

The target platform does not make a browser test run on a console automatically. It describes the intended destination and routes the player to a separate compatibility check when needed.

Protocol checklist

• Choose the actual primary input
• Interact with the device
• Resolve every manual state

Export preserves evidence and limitations

The local JSON includes the selected platform, input, use case, check states, creation time and user-agent context. It does not include raw key sequences, pointer trails or controller samples.

The report is useful for repeating the same environment or sending a concise support note. It is not a warranty certificate, benchmark rank or promise that a particular game implements the input.