Contact

The fastest way to reach us is email: hello@keyboardtestertool.com. We usually reply within two business days, and every message is read by the person who builds the site rather than a support queue.

Reporting a key that does not test correctly

This is the most useful thing you can send us, and it is also the easiest to get wrong. A report saying a key does not work is difficult to act on, because the tester deliberately shows a key as untested when the browser never received it, and that is often correct behaviour rather than a bug.

Please include:

Before sending, it is worth checking the guide that matches the symptom. Keys that never report are often keys the operating system takes first, and a key that types the wrong character is nearly always a layout setting rather than a fault in the tester or the hardware.

Asking for a layout we do not draw

Six layouts ship today: full size, tenkeyless, 65 percent, 60 percent, ISO for the UK and Europe, and Mac. If your board is a shape none of those match, tell us the model and we will look at adding it. Split, ortholinear and 40 percent boards are the most common requests and are the most likely additions.

In the meantime, any key you press is named in the readout even when the drawn layout has no cap for it, so an unusual keyboard can still be tested completely. Nothing is discarded just because it is not on screen.

Embedding the tester

Repair shops, IT teams and keyboard communities are welcome to embed the tester on their own pages, and there is a ready-made snippet on the embed page. No account, no attribution requirement and no tracking of your visitors. If you need a different height or a specific layout to load by default, email and we will tell you how.

What we cannot help with

We cannot diagnose a specific keyboard remotely, recommend a repair shop, or tell you whether a particular model is worth buying. The tester reports what your browser received, and the guides explain what the patterns usually mean, but the physical inspection has to happen at your end.