Map Keyboard Shortcut Collisions Across Explicit Action Scopes — Free
A shortcut alias can hide the same chord in two action descriptions. Normalize the modifier model and state which focus scopes can overlap before asking why one keypress sometimes triggers two actions.
The proof surface
Keyboard-navigation burden tools count repeated steps. This matrix instead builds a same-chord collision graph under a declared Ctrl/Meta model and explicit scope overlap rule. It never intercepts keys, executes shortcuts or certifies their accessibility.
InputAction code | modifier+key chord | global or named focus scope; primary modifier model: 0 ctrl, 1 meta
Rare deviceKeyboard-navigation burden tools count repeated steps. This matrix instead builds a same-chord collision graph under a declared Ctrl/Meta model and explicit scope overlap rule. It never intercepts keys, executes shortcuts or certifies their accessibility.
Output artifactUnique same-chord overlapping-scope pairs with row-by-row context
Cost$0 local calculation · no card, paid key, subscription or signup · proposed filing price is not for sale
Sample, not your facts: Illustrative inputs: Search action | Primary+K | global; Insert-link action | Ctrl+K | editor; Clear-filter action | Ctrl+L | filters. Primary modifier model: 0 Ctrl, 1 Meta = 0. Unique same-chord overlapping-scope pairs: 1 colliding action pairs. All records are invented.
Before using the shortcut-scope matrix
Primary is a source alias mapped only by the entered model: zero means Ctrl and one means Meta. Ctrl/Control and Meta/Cmd/Command are equivalent spellings; Alt and Shift remain separate modifiers. Chord modifier order is normalized, but duplicate modifiers after alias mapping are rejected as ambiguous source descriptions. The supported base keys are letters, digits, F1–F24 and the named keys listed in the guide. Scope names are case-insensitive codes; global overlaps every scope, while two different named scopes are assumed mutually exclusive. Actual browser event capture, bubbling, focus, nested widgets, remapping and reserved system or assistive-technology commands are not analyzed. Bare character keys receive a review note independent of collision count.
Why the flat version breaks
Comparing chord strings without normalizing aliases
Primary+K and Ctrl+K can mean the same thing under the Ctrl model, while Shift+Ctrl+K and Ctrl+Shift+K differ only in spelling order. Normalize the stated model first. Do not silently drop repeated modifiers: Primary+Ctrl under the Ctrl model is rejected so an ambiguous source description can be corrected.
Calling different widget labels nonoverlapping scopes
A component inside another component can share event propagation or global handlers. This model's different named scopes mean mutually exclusive activation, an assumption that requires actual testing. If that assumption is false, a zero graph edge is misleading even though the chord arithmetic is correct.
Treating zero listed collisions as accessibility approval
A chord may conflict with the browser, operating system or assistive technology even when the app's own list has no peer. A bare character shortcut also needs a separate accessibility review. The matrix never captures keys or verifies remapping and cannot issue a conformance verdict.
How to work the shortcut-scope matrix
Document action scope before the key chord
Identify whether an action is active globally or only inside one verified focus context. Distinct scope names in this model mean mutually exclusive contexts, not merely different component labels. If nested widgets can respond at the same time, use a shared scope or review that overlap separately. Keep the action code anonymous; user content is unnecessary.
Enter supported chords and choose the Primary model
Use modifiers joined by plus signs and one final base key. Supported named keys are Enter, Escape, Tab, Space, ArrowUp, ArrowDown, ArrowLeft, ArrowRight, Home, End, PageUp, PageDown, Delete, Backspace, Insert, Slash, Minus, Equal, Period and Comma, plus F1–F24. Letters and digits are case-normalized without inferring Shift. Choose Ctrl or Meta explicitly; the browser platform is not guessed.
Count graph edges, not repeated warnings
Normalize aliases and modifier order, then compare each action pair once. A collision requires the same normalized chord and either a global scope or matching named scopes. Each row lists its peer actions, while the summary counts unique pairs. Bare letters, digits and printable named character keys are marked for separate single-character-shortcut review even when no listed action collides.
Test actual keyboard behavior with a specialist
Inspect the application's real handlers, focus scopes, off/remap mechanisms and reserved shortcuts. Ask an accessibility specialist to review single-character behavior and assistive-technology interactions. A zero in this finite action list does not mean the keyboard system is safe or conformant; omitted actions and operating-system commands remain outside the graph.
What the shortcut-scope matrix separates
Question
Before
Inspect this instead
Comparing chord strings without normalizing aliases
Primary+K and Ctrl+K can mean the same thing under the Ctrl model, while Shift+Ctrl+K and Ctrl+Shift+K differ only in spelling order. Normalize the stated model first. Do not silently drop repeated modifiers: Primary+Ctrl under the Ctrl model is rejected so an ambiguous source description can be corrected.
Enter supported chords and choose the Primary model
Calling different widget labels nonoverlapping scopes
A component inside another component can share event propagation or global handlers. This model's different named scopes mean mutually exclusive activation, an assumption that requires actual testing. If that assumption is false, a zero graph edge is misleading even though the chord arithmetic is correct.
Count graph edges, not repeated warnings
Treating zero listed collisions as accessibility approval
A chord may conflict with the browser, operating system or assistive technology even when the app's own list has no peer. A bare character shortcut also needs a separate accessibility review. The matrix never captures keys or verifies remapping and cannot issue a conformance verdict.
Test actual keyboard behavior with a specialist
This shortcut-scope matrix replaces a manual count or calculation, not source verification or the responsible person’s review.
Run it on the samples, right here
FIRST-LOAD
HYPOTHESIS / PROTOTYPE — checkout unavailable. Calculation is local. A draft is saved automatically in this browser profile when storage is available; Reset to sample clears it. Optional Pro history stores only five summaries and has its own deletion control. State links encode your inputs and can remain in browser history, clipboard or recipients’ records; share only non-sensitive rows. Optional external AI formatting leaves this device. The required site analytics beacon reports page activity; shared URLs contain encoded inputs. Do not treat an encoded URL as private. The calculator has no input-collection endpoint.
Shortcut-description reconciliation only, not a WCAG conformance or reserved-key certificate. Test real focus and event handling, off/remap options and assistive-technology interactions with a qualified accessibility specialist before deploying shortcuts.
Data note: The shortcut-scope matrix processes Action code | modifier+key chord | global or named focus scope locally. Starter/sample selection and Run compute in this tab; no input is sent by the calculator. A local draft may be saved; explicit state-link sharing or optional external AI formatting can disclose inputs. Use non-sensitive labels.
Go deeper: the companion app files the same reading as a scored comparison matrix
The article demo above runs without limits. The companion app keeps a local history, exports the rows as CSV, prints the shortcut-scope matrix reading, and holds your drafts on this device — one complete free app run; the proposed $4 one-time filing layer is not for sale.
The shortcut-scope matrix answer stays complete for free. The proposed $4 one-time filing layer adds row CSV, print and five local reading summaries, not hidden answers. Checkout is unavailable; the article demo remains unlimited.
Shortcut-description reconciliation only, not a WCAG conformance or reserved-key certificate. Test real focus and event handling, off/remap options and assistive-technology interactions with a qualified accessibility specialist before deploying shortcuts.
What this is built on
Method: Normalize aliases and modifier order, then compare each action pair once. A collision requires the same normalized chord and either a global scope or matching named scopes. Each row lists its peer actions, while the summary counts unique pairs. Bare letters, digits and printable named character keys are marked for separate single-character-shortcut review even when no listed action collides.
All sample records, dates, quantities and labels are invented. No outside policy, contract, rate, clock offset, measurement or accessibility standard is represented as verified.
Google’s official pricing documentation, fetched 2026-10-01, says AI Studio is free in available regions. Optional formatting may require a Google account; manual local entry requires none. Limits can change and free-tier content may be used to improve products. Do not send private records.
Before: shortcut aliases and widget names hid overlapping key actions. After: a declared modifier model and explicit scope graph expose each colliding pair.
With Primary mapped to Ctrl, Search and Insert-link normalize to the same chord. Their scopes overlap because Search is global, so they form one colliding pair. Clear-filter has a different chord and does not collide in this list. The matrix counts each pair once even though both actions show a peer. This does not inspect browser or assistive-technology reserved shortcuts.
Sample B — changed plan
Play action | Space | player
Pause action | Space | player
Next-card action | Space | cards
Global-help action | Space | global
Play and Pause share both chord and scope, one pair. Global-help overlaps Play, Pause and Next-card, adding three pairs. Next-card does not overlap the player scope under this declared mutually exclusive focus-scope model. Total collision pairs are four. All bare Space actions also receive a single-character review note; the tool does not implement an off/remap or focus-only exception.
Under the Ctrl model both chords match, but panel and table are declared mutually exclusive named focus scopes, so no pair is counted. Scope separation must be verified against actual event handling; a bubbling global listener could invalidate the assumption. Switching to the Meta model also separates these chords, but neither model establishes that the browser or assistive technology permits them.
Optional AI formatting, never the calculation
Manual entry completes this shortcut-scope matrix for free without signup. If available to you, the free AI Studio interface linked in the sources may format fictional or non-sensitive notes; external access may require an account. No API key or AI call is built into this tool. Free-tier content may be used to improve products. Review each cell and transcribe it to the labeled row schema; do not paste the JSON object into the row box.
Format only these fictional or non-sensitive notes for a shortcut-scope matrix. Return strict JSON shaped as {"rows": [{"label": "string", "cells": ["string", "string"]}], "setting": "string"}. The columns are Action code | modifier+key chord | global or named focus scope; the setting is Primary modifier model: 0 Ctrl, 1 Meta. Keep all supplied strings and quantities exactly; do not calculate, infer missing entries, invent dates or add advice. If any required value is missing, return an empty rows array and ask me for it separately. I will verify every cell against my source and manually transcribe rows using vertical bars before running the local calculator.
An AI response is not executed, fetched or trusted as a result. Missing values remain questions; the strict local parser checks the rows you actually enter.