Direct answer
What these Gamepad & Touch browser tests can tell you
Use these tests to visualize browser gamepad button and axis values or touch contacts inside a bounded surface. Comparing centered values, full ranges and repeated contacts gives useful evidence without uploading controller or touch input.
Useful starting points
- A controller button, trigger or axis is not detected
- A stick does not return consistently to its center value
- A touchscreen area or multi-touch combination needs checking
Evidence shown in the browser
- Gamepad connection, mapping, button and axis values
- Repeated resting samples and observed axis ranges
- Pointer contacts, trails, pressure and simultaneous touch count
Important limit
Browser mappings and system gestures vary; the readings do not set a game deadzone, calibrate hardware or determine warranty or repair status.
For a clearer comparison, repeat the same action, change one relevant condition at a time, and record the browser, operating-system family, date and exact visible result. Use the page title and canonical URL when sharing the observation; do not describe a browser result as hardware certification.
Read the testing methodology or review our source and correction standards.
Focused tests
Choose a Gamepad & Touch test
Open the page that matches the observation you want to reproduce.
Gamepad Test
Visualize connected controller buttons, triggers, axes, D-pad, mapping and optional vibration through the Gamepad API.
Open test →GTController Stick Drift Test
Watch analog-stick values around center and compare them with an adjustable reference deadzone.
Open test →GTGamepad Button Test
Focus on controller button, trigger and D-pad activation values.
Open test →GTTouchscreen Test
Draw touch points and trails inside a bounded test surface while reporting pointer type, pressure and contact count.
Open test →GTMulti-Touch Test
Count simultaneous browser touch contacts and compare them with navigator.maxTouchPoints.
Open test →