One direction is not detected
Retry it, compare another browser, and use the main test to see whether nearby keys produce events. An unobserved key is not automatically failed.
Directional key diagnostic
Arrow Keys Test
Verify Up, Down, Left, and Right individually, inspect simultaneous holds, then use a short sequence to confirm the browser differentiates every direction.
Direction history remains temporary and local.
Four-direction test
Test every arrow direction
Focus the directional pad, then press each physical arrow key. Page scrolling is suppressed only while this test surface has focus.
↑Up
→Right
↓Down
←Left
UpNot tested0 completed presses
RightNot tested0 completed presses
DownNot tested0 completed presses
LeftNot tested0 completed presses
Currently detectedNoneLast arrow: —
Optional sequence
↑ → ↓ ←
Progress: 0 / 4. Next expected: Up.
Continue with the expected directionAn untested direction is not classified as failed.
Four separate positions
How to test all four arrow keys
Focus the directional pad and press each arrow normally. The sequence ↑ → ↓ ← adds a differentiation check: an incorrect direction remains a valid detected key, but it does not advance the sequence.
Arrows work here but not in a game
Inspect the game's bindings, input mode, focus, and remapping utilities. Some games map movement to WASD instead of arrow codes.
Input context matters
Why arrow behavior can differ
WASD and arrows are different codes
ArrowUp is physically distinct from KeyW. Software can bind either group independently.
Laptop Fn layers
Compact laptops may share arrow positions with other functions. Firmware or an Fn layer can change which event reaches the browser.
Scrolling behavior
Arrow keys normally scroll pages. Default scrolling is prevented only while the focused arrow test surface is active, never on links or normal controls.
Combinations vary
The live combination display reports what reached this page. It does not claim every keyboard must support every opposing or diagonal combination.
Browser limits and privacy
Observed direction is not hardware certification
Operating-system shortcuts, accessibility tools, remote sessions, remapping, and focus can affect arrow events. Current holds, tested directions, counts, and sequence progress stay in memory and clear on reset or reload.