PadTest is a small independent site. The most valuable thing you can send is a correction — a claim on a page that does not match what your controller actually does, or a source citation that does not hold up.
Reporting a wrong fact
Tell us which page, which sentence, and what you observed instead. If the claim cites a
specification section or a browser source file, say whether you checked it — a report that
says "the table is wrong for my pad" is a good start, and one that says "index 8 is Options
on mine, not Share, and here is the id string" is immediately actionable.
Reporting a controller that behaves oddly
Four lines from the device panel make almost any report solvable:
- the
idstring, in full — it identifies the device the browser thinks it has; - the
mappingvalue, which decides whether any index table applies at all; - the button and axis counts;
- your browser and operating system, and whether the pad was wired or wireless.
Please include the connection type. A great many "my controller is mapped wrongly" reports
turn out to be a pad reporting an empty mapping over one connection and
"standard" over another, which is genuinely useful to know but is not a fault
in the tester.
What we cannot help with
We cannot diagnose hardware remotely, recommend a repair, or tell you whether a controller is worth buying. The site reports what your device sends the browser; what to do about it is yours to decide. We also cannot make a browser expose something it does not. Gyros, adaptive trigger resistance and LED control have no representation in the Gamepad interface at all; touchpad coordinates do have a defined form in the specification, but Chromium keeps it behind an experimental runtime flag, so a browser running default settings does not deliver them either. Neither case is something work on this page could change.
Privacy of a report
The site itself collects nothing — there is no form on this page for exactly that reason,
and no input you make in the tester is transmitted anywhere. If you send us a controller
id string, be aware it can be reasonably specific about your hardware, though
not about you. We use such reports only to fix the page they concern.
Reaching us
Plainly: this site publishes no address yet, and rather than send you to a page where one is supposed to be, we would rather say so. Until one appears here, the route that works is to raise the correction wherever you found the link to this tool — a forum thread, a repair guide, a comment — and quote the sentence you are disputing. We would rather receive a rough report than none: a screenshot of the device panel with one line of context is enough to start from.