Quick answer
What this guide helps you determine
Connect a controller, activate it, then check every button, trigger, stick and D-pad value.
Begin with the observable browser result, repeat it under the same conditions, and change one connection, setting or application at a time. A browser result narrows likely causes but does not certify hardware or decide a repair.
Scope of this check
A controller test should confirm connection, browser activation, button and axis coverage, center behavior and disconnect handling. Gamepad numbering and mapping are browser abstractions, so the page can show received values without guaranteeing that a particular game uses the same labels.
Step-by-step method
- Connect by USB or Bluetooth, focus the page and press a controller button so the browser exposes it. Select the expected controller if more than one is listed and note the local mapping status.
- Press every button slowly, move triggers through their range, rotate each stick around the edge and return it gently to center. Test the D-pad as separate directions and use vibration only after a deliberate action if supported.
- Disconnect and reconnect once, then compare the actual game or system controller panel. If a control is missing everywhere, check connection, firmware and manufacturer support; if only one game differs, review its mapping.
What to check first
Use these checkpoints to keep the comparison focused. Record the visible behavior rather than assigning a fault label too early.
- Press a button to expose the controller
- Move axes through their full range
- Test wired and wireless modes separately
How to read what you see
| Observation | What it can suggest | Useful next check |
|---|---|---|
| All controls change and return normally | The browser received the tested input range in this mapping. | Use the game’s own calibration/mapping next. |
| Controller appears only after a button press | This is normal privacy/activation behavior in many browsers. | Press once after loading before diagnosing detection. |
| A control has another index than expected | Browser/vendor mapping differs. | Map by observed control rather than a universal number. |
Common mistakes to avoid
- Do not share the controller ID if it is not needed.
- Do not force sticks or triggers past their stops.
- Do not assume a browser vibration test is safe for a damaged controller.
Build evidence another person can use
Write down the exact action, visible result and whether it repeats. Include the browser family, operating-system family, connection type and the single comparison that changed the result. Quote the observation directly—for example, “All controls change and return normally”—then add where it occurred and which comparison changed it.
Change one condition per comparison and return settings that have no effect. Follow model-specific manufacturer instructions before firmware changes, cleaning, disassembly or warranty action.
When to seek qualified support
If the same problem remains in multiple applications and on another compatible connection or computer, collect the repeatable observations and contact the manufacturer or a qualified technician. Stop using equipment that is physically damaged, unusually hot, wet, sparking or unsafe. Device Test Bench cannot inspect electrical condition or make a repair decision.
Privacy during testing
Our public tests process key events, pointer values, media streams and controller input locally. Do not send private recordings, complete typed text or device identifiers when asking for help. A short description of the behavior, browser and page URL is normally enough.
Questions readers ask
Why is my controller not listed immediately?
Browsers often expose gamepads only after user activation, usually a button press while the page is focused.
Does a successful browser test guarantee every game works?
No. Games have their own supported devices, mappings, deadzones and platform layers.
Primary technical references
The following specifications define the browser APIs discussed in this guide. They are primary web-platform references, not product repair manuals.