How InputAnalyzer measures

Each tool reads standard browser APIs after you explicitly start a test. Calculations run locally and work from timestamps, state transitions and value samples exposed to the page.

• Gamepad axes and button values from the Gamepad API
• Keyboard press, release and repeat metadata from UI Events
• Pointer, click and wheel events from Pointer and Wheel Events

A raw event log is easy to misread. Guided steps ask for one controlled action at a time, pause when focus is lost and reject samples that are too short or interrupted.

Drift, jitter, circularity and regularity thresholds are conservative starting points, versioned with the algorithms. They classify observed browser signals as reassuring, worth reviewing or inconclusive — never as proof that hardware is physically defective.

Repeat an unexpected result, reconnect the device, compare another browser or computer and check the same behaviour in the application where the problem occurs.