CTRLCHK

CTRLCHK DIAGNOSTICS

Controller Button Test

Press every button and see exactly what your browser receives.

No downloadNo accountRuns locally

Device

No controller detected

Waiting
Live controller input visualization

Waiting for controller. Connect via USB or Bluetooth, then press any controller button.

Button test

Press every button and see exactly what your browser receives.

Controls responded0 of 0 controls responded

How controller button testing works

The live controller visual and the status table both read the same mapped Gamepad frame. A press lights the matching control and latches Responded. Press counts increment on the rising edge. Reset clears the session without claiming a hardware fault.

What “Not tested” means

Not tested means this visit has not seen that input. It is not Broken, Defective, or failed. If a button never lights up after a firm press, the mapping may be incomplete, or the control may not be exposed to the browser.

Why browser button numbers sometimes differ

Standard mapping is the high-confidence path. Profile layouts are applied when CTRLCHK recognizes a known stick/button order. Heuristic mappings keep generic Button N labels so a guess cannot look like a certainty. Compare with the trigger test if bumpers work and analog triggers do not — those are different Gamepad fields.

FAQ

Questions people actually ask

How does controller button testing work?

CTRLCHK reads the Gamepad API each animation frame. When a button’s pressed flag becomes true, that control is marked Responded and the press count increments. Nothing is treated as broken just because you have not pressed it yet.

What does “Not tested” mean?

The control exists on the device mapping, but this session has not seen a press. Press it to mark Responded, or ignore it if you do not care about that input.

Why do browser button numbers sometimes differ?

The W3C standard mapping uses fixed indexes (0 = A / Cross). Some browsers expose an empty mapping. CTRLCHK applies a known layout when it can; otherwise it labels Button 0, Button 1, and so on instead of guessing Xbox or PlayStation names.

Can an unpressed button fail the test?

No. Unpressed controls stay Not tested. Unavailable is reserved for indexes the browser did not expose.