How to get in touch
Email [email protected]. Every message is read; replies are not guaranteed, and bug reports get priority over general questions.
Reporting a problem with a tool
Keyboard behaviour varies enormously between models, firmware versions and operating systems, so a report is only actionable with the surrounding detail. Please include:
- Which tool — the page URL is enough.
- What you expected and what happened — for example, “held W, A and Space; A stayed dark in the panel.”
- Keyboard make and model, and whether it’s connected by USB, a 2.4GHz dongle, or Bluetooth.
- Browser and version, and your operating system.
- Whether another browser behaves differently — this single detail separates a tool bug from a hardware or driver fault more often than anything else.
Before reporting a dark key, it’s worth checking it against the list of keys browsers can never see — PrintScreen, Fn, Touch ID and Windows key shortcuts are all intercepted by the OS, and no web page is told about them.
Corrections to a guide
If a repair step is wrong, out of date, or risks damaging hardware, say so — that’s the most valuable kind of message this site receives. Quote the sentence and explain what happens in practice, and it will be corrected or removed.
What this site can’t help with
- Individual repair diagnosis — there’s no way to assess hardware that isn’t in front of you. Run the relevant test, then follow the guide that matches your result pattern.
- Warranty and returns — those go to the manufacturer or the seller. A screenshot of a failed test is useful evidence to attach to that claim.
- Data recovery or account issues — this site stores nothing and has no accounts, so there’s nothing on this end to recover.
Privacy of your message
Email you send is stored in the mailbox it arrives in and is not used for anything other than replying to you. It is never sold or passed to third parties. The privacy policy covers this along with everything else.
Usually not. PrintScreen, Fn, Touch ID and Windows key combinations are intercepted by the operating system before the browser is notified, so no browser-based tester can see them. If the key is not one of those and it works elsewhere but never lights up here, that is worth reporting — include your browser, OS and keyboard model.
Not reliably, and a confident answer without seeing the hardware would be worse than no answer. What the tests can tell you is the failure pattern — one dead key, an adjacent cluster, a whole row, or chatter — and the repair-or-replace guide maps each pattern to the realistic options.
Possibly. Layout requests are more useful with specifics: the exact model, the region, and which keys the current layouts get wrong. ISO vs. ANSI differences and regional key placement are the most common gaps.