Keyboard Tester

Contact

This is a static site with no backend and no contact form, so email is the only channel — which also means nothing you send passes through this website at all.

Email: rlaejrtn16@gmail.com

What to expect

The site is maintained by one person alongside other work. Replies usually take a few business days, sometimes longer. Reports of a key that behaves incorrectly in the tester get priority over feature requests, because those are bugs rather than wishes.

Reporting a key that does not register correctly

The single most useful thing you can include is the raw event data the tool already shows you. With those values a problem can usually be reproduced immediately; without them it is guesswork.

  • The event.code, event.key and keyCode shown in the "last key event" readout when you press the problem key.
  • Your browser and operating system, including the version if you know it.
  • Your keyboard model and layout (ANSI, ISO, JIS) and its size (full-size, TKL, 65%, laptop).
  • Whether the same key behaves the same way in another browser — that one line separates a site bug from a system-level issue.

Keys that exist on your board but are not drawn on the on-screen layout are a known and expected gap: the board rendered is US ANSI, and anything outside it is counted in the "extra keys" tally rather than lighting a cell. If a common key code is missing from that map entirely, that is worth reporting.

What cannot be answered here

Individual hardware repair advice is outside what an email exchange can sensibly do — whether a specific laptop needs a new top case, whether a particular switch is worth resoldering, or what a repair should cost in your country. The diagnostic pages describe how to narrow a fault down yourself, and a local repair shop with the machine in front of them will beat any remote guess. The tester is also not a warranty authority: it can produce evidence for a claim, but it cannot decide one.

Before writing

Many questions are already answered on the pages themselves: how the measurements are defined and what they cannot prove is set out on the about page, data handling and advertising cookies on the privacy page, and the frequent hardware questions — Fn keys, rollover limits, chatter thresholds — in the FAQ sections of the keyboard tester, rollover test and chatter test.