What these tests can tell you
Understandable observations, with their context and limits.
Make a useful comparison
Choose a symptom and make a deliberate input in the test area. Repeat before changing a setting. Then compare one condition: another application, connection or device. A result describes that run; it is neither a repair nor a hardware certificate.
Different states mean different things
- Detected
- The page received that position or button at least once.
- Held down
- The last received state indicates a press is still held. Losing context ends that observation.
- Not observed
- No matching input reached this run. The key may be untested, absent or intercepted.
- Excluded by you
- You marked a position absent from your hardware. It does not become a tested key.
- Interrupted or inconclusive
- The context or signals do not allow the check to be interpreted fully. Restart the protocol deliberately.
Keyboard: positions, cycles and combinations
The drawing follows reference physical positions. Received characters depend on software layout, Shift, AltGr and remapping. The references offered are US QWERTY, French AZERTY and Belgian Windows AZERTY. The Belgian reference follows Microsoft KLID 0000080C; its mapping was checked against that source and through software tests, not a physical keyboard. It does not reproduce every Belgian variant. Mac modifier labels do not reproduce every Apple keyboard.
Free testing shows the positions received. A single-key check separates press, release, hold and new cycles. Native repeat during a hold is distinct from new closely spaced presses. A repetition threshold is exploratory; the browser cannot see electrical contacts or firmware filtering.
Combination testing covers only the groups actually tried. A maximum observed count never certifies universal NKRO. Fn, media keys and reserved shortcuts may not reach the page. Tab and Escape leave the test. Clicking the drawing never validates a physical key.
Mouse: logical buttons, holding and scrolling
Primary and secondary describe logical assignments. Left-handed settings can swap them. Mouse or trackpad is your chosen setup: the browser cannot reliably distinguish every device.
Read a hold alongside its presses, releases and interruptions. Leaving the area or switching applications interrupts the observation; it does not establish contact failure. Scrolling records directions and changes in direction. Browser units and trackpad inertia are not universal physical wheel notches.
Repeated clicks: read a series in context
Make intentional single presses and release fully between them. The count describes received presses, not the number of gestures you intended. Your threshold identifies close intervals; it is not a universal boundary between a healthy and faulty mouse.
Intervals use event timestamps, whose precision depends on the browser. They do not measure electrical latency. Repeat a series interrupted or affected by uninterpretable timing. Statistics describe only comparable intervals and the stated sample.
The browser’s own double-click signal is separate from presses and never increases the press total. An intentional double-click demonstrates the display, not detection of an intermittent fault. To compare two series, keep the button and threshold the same and change one condition.
A controlled example
Software simulation: two presses created 200 ms apart may wait in a queue while JavaScript is busy, then be handled only a few milliseconds apart. Version 2 uses their event timestamps to avoid interpreting that delay as an unwanted double-click. This check tests our software; it does not reproduce every physical switch fault.
Verified configurations
8 September 2026 · software verification. Tests run with Playwright on macOS 26.6.2 (Apple silicon), using automated input. These are browser-engine checks, not tests of physical keyboards or mice. The checks cover keyboard protocols, mouse cycles, click series, interruptions and text reports.
| Engine | Version | Result |
|---|---|---|
| Chromium | 145.0.7632.6 | Passed |
| Firefox | 146.0.1 | Passed |
| WebKit | 26.0 | Passed |
WebKit here is an automated engine, not a physical iPad Safari test. English and French pages were also checked at simulated widths of 320, 390, 768 and 1440 pixels. Printable reports and the equipment checklist were rendered and visually checked as Chromium PDFs. Browser automation does not exercise every operating-system shortcut, device driver or physical input path.
Not yet tested on physical equipment: Windows keyboards and mice, Apple keyboards and trackpads, iPad Safari with external input, and Android Chrome with external input. No healthy or faulty switch has been certified. A useful next validation compares the same deliberate gesture on known working and suspect hardware, with the device, connection, system and browser recorded.
Privacy and reports
Positions, counters and test statistics stay in bounded page memory. They disappear when you leave or reload. Reports are created locally at your request and contain your selected context and observations, not typed characters, a hardware identifier or text history. Your browser can save the print view as a PDF.
The site retains its existing Google Analytics for visits and a few broad actions: first use, report review, export and related navigation. No key, coordinate, input sequence or raw interval is attached to those events. Disabling or blocking measurement does not block the tools, and past interactions are not replayed when measurement becomes enabled.
Method changes
Version 2 · 8 September 2026. Event timestamps, keyboard protocols, comparable click series and reports that distinguish interruptions. Software checks and physical hardware tests remain separate evidence categories. Version 1 introduced keyboard coverage, logical buttons and the initial exploratory threshold.