What Controller Checker reads from your browser
Controller Checker reads the controller state exposed by the browser's standard Gamepad API. That state can include a device label, connection status, button values, analog axes, timestamps, mapping information, and a compatible vibration actuator. The live values are processed on the current device and are not uploaded as controller telemetry.
The browser and operating system decide which hardware signals are available. A value missing from this site can therefore reflect a web-platform, driver, firmware, permission, or connection limitation rather than failed controller hardware.
How the controller diagnostics are calculated
Button and trigger checks display the normalized values reported by the active controller. Stick drift checks compare each resting X/Y coordinate with the neutral center. Range and circularity checks record the outer positions reached while the stick is moved. Polling rate is estimated from browser-observed update intervals and timestamps rather than raw USB packets.
Vibration checks send only effects supported by the actuator exposed to the browser. Model-specific features such as DualSense adaptive resistance, Switch HD rumble, battery state, firmware details, and complete force feedback are not consistently available through the standard API.
How to obtain a repeatable result
- Connect by a known data-capable USB cable first, then compare wireless separately.
- Place the controller on a stable surface and leave the sticks untouched before reading center offset.
- Repeat an unexpected result after reconnecting and in another current browser.
- Compare browser findings with the console, operating-system panel, manufacturer utility, or a supported game.
What can change a browser controller result
Controller model, firmware, USB or Bluetooth mode, driver, remapping software, browser version, operating system, animation-frame scheduling, background tabs, and display refresh can all affect the visible result. Because those variables are outside a single web page, the site describes drift, latency, polling, range, and vibration results as diagnostic estimates rather than certification.
Standards and browser references
These sources define the browser interfaces and their current implementation guidance. They support the terminology and technical boundaries on this page; they do not validate a particular Controller Checker result or endorse this site.
- W3C Gamepad specification
The current published interface for gamepad buttons, axes, mappings, timestamps, and haptic output.
- MDN Gamepad API
Browser-facing documentation, usage guidance, security requirements, and compatibility notes.
- MDN GamepadHapticActuator
Documentation for the browser haptic actuator used by supported vibration tests.
Review and correction policy
Guidance is reviewed when the tester, browser behavior, compatibility information, or site structure changes. The current methodology version was reviewed on 2026-08-14. Reproducible corrections can be submitted through the contact page with the controller model, connection, operating system, browser version, page URL, expected behavior, and observed result.
Controller Checker does not publish invented ratings, laboratory claims, or author credentials. Where this browser test cannot establish a hardware fact, the page states the limitation and points users toward an independent comparison.