Why a Chromebook Needs Its Own Keyboard Test
A Chromebook keyboard is not a Windows laptop keyboard with different stickers. Three differences matter enough that testing it on a generic layout gives you misleading results.
First, the Search key — the magnifying glass or Launcher circle where Caps Lock lives on other machines — reports itself to the browser as MetaLeft, the same code a Windows key sends. On a generic tester it lights up a key labelled "Win" in the wrong position, which makes it look like something is wrong when nothing is.
Second, the top row is browser actions, not F-keys. Back, Forward, Reload, Fullscreen and Show-windows send their own codes (BrowserBack, BrowserRefresh, ZoomToggle and so on) rather than F1 through F5. Brightness, volume and the lock key are handled by ChromeOS itself and never reach a web page at all — this test draws them greyed out and leaves them out of the progress count, because no browser-based tool can see them.
Third, there is no Delete key and no Caps Lock keyon most models. If you came here because Delete "does not work", that is the likely answer: it does not exist. The table below lists what to press instead.
One thing to be clear about: this test tells you whether a key sends its signal to the browser. It cannot tell you whether the fault is the switch, the ribbon cable, or the ChromeOS keyboard remapper. What it does give you is a definite answer to "is it the keyboard or the app I was using", which is the question that decides whether you need a repair. If several keys in a row fail together, that pattern points at the ribbon connector rather than individual switches.
If your Chromebook has an external USB or Bluetooth keyboard plugged in, test that separately — it may use a standard Windows layout, in which case the Windows keyboard test is the better fit. For built-in keyboards on non-ChromeOS laptops, use the laptop keyboard test.