Why this answer matters
A browser key-rollover test can validate observable combinations, while a claimed 1,000 Hz specification should not be inferred from typing feel alone.
2 requirements3 verification steps1 primary source
Requirements
What has to be true
- Wired USB connection.
- Browser/OS must receive standard keyboard events for DeviceOK tests.
Verify it yourself
Use this test sequence
Change one variable at a time so you know which requirement made the difference.
- 1
Run the NKRO/ghosting test with the combinations that fail in-game.
- 2
Run chatter/repeat tests before changing iCUE profiles.
- 3
If raw keys work here but not in a game, inspect mappings/profile/game input next.
Limits
What this answer does not prove
- Browser keyboard events are not a laboratory polling-rate measurement.
- OS/browser shortcut interception can prevent some combinations from reaching a page.
Relevant DeviceOK checks
Test the part you can observe
Keyboard TestPress keys and verify that the browser receives the expected keyboard events.
→NKRO Keyboard TestCheck how many simultaneous key presses your browser receives.
→Keyboard Ghosting TestTest key combinations for missed or phantom keyboard events.
→Keyboard Chatter TestLook for duplicate key presses that may indicate switch chatter.
→