Contact

What is genuinely useful to send

• A factual correction. If something written here about browser event timing, USB, operating-system input handling or display timing is wrong, imprecise or out of date, please say so. Corrections are the most valuable message this site gets, and pointing at a source makes them easy to act on.
• A test that misbehaves. A browser, operating system, keyboard or input device where a tool reports something obviously impossible, freezes, or fails to register keys that clearly work elsewhere.
• An accessibility problem. Anything unreachable by keyboard, unclear to a screen reader, or unreadable at high zoom or small screen sizes.
• A gap in the explanations. A question a page should have answered and did not.

What to include in a bug report

Three lines are usually enough to reproduce something:

• the page URL and the browser and version you used;
• your operating system, and the keyboard or input device if it is relevant;
• what you expected to happen and what happened instead.

The measurement environment panel on each test page lists the timer resolution and browser details the tool actually detected. Copying that line into your message removes most of the guesswork.

What this site cannot help with

We cannot diagnose an individual keyboard, tell you whether a switch has failed, handle a warranty claim, or recommend which model to buy. A browser can only observe events after the operating system has delivered them, which is explained in full on the methodology page. Questions about a specific product are best taken to its manufacturer.

What to expect

Messages are read, but no response time is promised and not every message gets a reply. Clear bug reports and corrections are prioritised, and a correction that turns out to be right will show up in the page itself — which is the point.

If you have not looked around yet, the keyboard latency test is the main tool, and the guides cover the concepts behind every result.