Mac Keyboard Test

Test a Mac keyboard one key at a time to see which standard keyboard events the browser recognizes and find keys that are not tested or captured.

Test settings

Mac keyboard layout
Test scope

The common full scope includes F1–F12, the main section, modifier keys, and arrow keys; it excludes Fn, media keys, and the numeric keypad.

Focus this area, then press keys one by one Pressed keys are marked in the target key map below. Tab records the key and leaves the test area; focus it again to continue.
Ready. Focus the test area and press keys one by one; Tab records that key and leaves the area.
Result overview Waiting for test
Target key coverage — Ready. Focus the test area and press keys one by one; Tab records that key and leaves the area.
Current key
—
Last key
—
Untested keys
—

The result only represents standard keyboard events received by this browser. System-reserved shortcuts, Fn, media keys, or hardware electrical problems cannot be diagnosed from this page alone.

Target key status

Untested Tested Currently pressed
View untested key codes 0

    Key coverage and remaining keys

    Tested and untested key positions

    • After testing, this area shows a diagram synchronized with the current result.

    No test has started. After pressing keys, this area compares the target positions that were tested with those that remain.

    Learn more

    Method, formula, and result definition

    KeyboardEvent.code identifies the physical key position and KeyboardEvent.key adds the current layout meaning. Tested keys are stored in a de-duplicated set; coverage = matched target keys ÷ current target keys × 100%. The active set is updated by keydown and keyup and cleared on blur or when the page is hidden.

    Tested and target key counts use integers. Coverage uses the unrounded ratio and is displayed to one decimal place. Completion is true only when the raw tested target count equals the target count.

    Automated tests cover ANSI, ISO, and JIS target counts, 0% and 100% boundaries, duplicate-key removal, out-of-scope key filtering, and invalid inputs. Browser acceptance should also check key capture, Tab exit, focus cleanup, copy, and reset.

    How to use and limitations

    The common full scope includes F1–F12, the main section, modifier keys, and arrow keys, but not Fn, media keys, or the numeric keypad. Fn and some media keys may not produce a standard KeyboardEvent. Command+Tab and Command+Space may be intercepted by macOS. Remote desktops, virtual machines, input methods, assistive technology, and browser extensions can alter key events. A mobile device without a physical keyboard is not supported.

    How do I test a Mac keyboard key by key?

    Choose the ANSI, ISO, or JIS layout closest to the physical keyboard, focus the test area, and press the target keys one at a time. Each detected physical key position is recorded once.

    Why do the Command or Fn keys not respond?

    Some system shortcuts are intercepted by macOS before they reach the page. Fn and some media keys are also not guaranteed to produce a standard KeyboardEvent, so this page cannot use that result alone to diagnose hardware damage.

    What is the difference between ANSI, ISO, and JIS keyboards?

    They mainly differ in the physical positions of the Return key, left Shift, extra character keys, and Japanese input keys. The target key count changes with the selected layout.

    Tool information and sources

    All key events, text, and statistics are processed locally in this browser. Nothing is uploaded, no remote API is called, and personal input is not stored.

    This tool uses no third-party runtime code or assets. The algorithm and interface are independently implemented; external links only explain browser event standards.

    Standards and method sources