Support channel

Contact & Feedback

Send focused feedback about gamepad tester support, controller diagnostics feedback, browser compatibility, page copy, widgets, or reproducible controller test issues.

Useful Feedback Details

Include browser, operating system, controller model, connection type, page URL, and exact symptom.

What To Include In A Useful Report

Good gamepad tester support starts with details that can be reproduced. Include the controller model, connection type, browser name and version, operating system, page URL, whether `?demo=1` was active, and the exact symptom. A report that says the controller test failed is hard to act on; a report that says button 7 never changes over Bluetooth in a specific browser is useful. Focused controller diagnostics feedback lets support compare the same input path instead of guessing from a vague description.

For drift, include idle values from the stick drift test and whether the same result appears over USB and Bluetooth. For mapping, include the button index and label shown on the button mapping test. For vibration, include the support message from the vibration test. For widgets, include the iframe URL and the parent page environment.

Screenshots are helpful when they show the visual state, but do not send private account pages or unrelated personal information. The diagnostics are local, so the project cannot see your controller values unless you describe them. Focused reports help improve copy, browser caveats, and UI behavior.

Feedback Categories

Compatibility feedback is most useful when a specific browser or device behaves differently from the page guidance. For example, a controller may expose haptics in one browser but not another, or a specialty joystick may report axes in an unexpected order. Those details can improve controller diagnostics for future users. Gamepad tester support also benefits from reports about mobile browsers, adapters, and iframe behavior because those environments change quickly.

Content feedback should point to a page and a sentence or concept that is unclear. The site aims for accurate, practical language, so corrections about WebHID, Web MIDI, haptics, mapping, and device terminology are welcome. The best feedback explains why the current wording may mislead users.

Widget feedback should include iframe size, embed URL, and browser. Some permission behavior changes inside iframes, so the parent page context matters. A gamepad tester widget that works full-screen but fails embedded may need permission policy guidance rather than code changes.

Scope And Expectations

GamepadTesterOnline.org can improve browser diagnostics, copy, accessibility, and compatibility guidance. It cannot repair hardware, provide manufacturer warranty decisions, recover firmware, or debug private game projects without reproducible public details. The site is a diagnostic tool and educational resource, not a repair shop.

There is currently no user account and no ticket portal. Use the contact email placeholder in the site configuration for now: hello@gamepadtesteronline.org. If a production support address changes later, it should be updated centrally so gamepad tester support copy stays consistent across pages and controller test support reports keep reaching the right place.

Any test values included in a message are informational details from the user's own testing process. A reply, if provided, should not be treated as a repair diagnosis, warranty decision, safety clearance, competitive certification, or proof that a controller will behave the same way in a console, game, emulator, cloud session, or manufacturer utility.

For urgent hardware safety concerns, stop using the device and contact the manufacturer or seller. If a controller overheats, smells unusual, has battery swelling, or behaves electrically unsafe, a browser controller test is not the right next step.

Response Expectations And Sensitive Information

A message may help improve a page, clarify browser support, or reproduce a compatibility issue, but a response is not guaranteed. Reports are most useful when they stay focused on public technical details rather than private account, order, payment, address, or warranty information.

Do not send controller serial numbers, photos of receipts, account screenshots, personal addresses, payment details, or unrelated private data. If a screenshot is needed, crop it to the diagnostic page and remove anything that is not relevant to the controller test.

Values, screenshots, logs, and descriptions sent through contact are no longer only local browser data. Send only the details you are comfortable sharing for review, reproduction, and content improvement.

Questions Users Ask

Short answers for common diagnostic decisions on this page.

Can support see my controller data?

No. The site processes data locally, so include relevant values manually if you want help interpreting them.

Where should bug reports go?

Use the contact guidance and include reproducible browser, device, page, and connection details.

Can you fix my controller?

No. The project provides diagnostics and interpretation, not physical repair or warranty service.

Useful Next Checks

Read troubleshooting paths

Fix detection, Bluetooth, permission, browser, and mobile issues.

Open all tools

Choose the right diagnostic page for the controller symptom you see.

Configure a widget

Generate responsive iframe embeds for a small live tester.