Keyboard Shortcut Inventory: Scope, Ownership, and Change History Across Apps

A cross-app shortcut inventory should answer three questions for every assignment: what action owns the keys, where the shortcut can trigger, and whether another active assignment can intercept the same combination. A list of key combinations alone is not enough. The useful record includes platform, scope, status, source, and ownership so that duplicate-looking shortcuts can be separated from safe reuse.

This is a documentation problem before it is a remapping problem. Build the inventory first, then change keys only after the overlap has been classified. HotkeyRadar can store project shortcut sets and a separate library in the browser, but it cannot determine the business meaning of an assignment or inspect every installed application.

Define one record for each active assignment

Use one row per action. If the same action has different bindings on Windows and macOS, keep separate platform records rather than compressing them into one ambiguous value.

Normalize notation before you compare anything

Control-K, Ctrl+K, and K + Ctrl can describe the same Windows-style combination. Pick one internal notation and normalize modifier order, spacing, and key aliases before looking for duplicates. Keep platform-specific modifiers distinct: Command on macOS should not be silently converted to Ctrl, and keyboard-layout differences can change the physical keys required for some characters.

A useful inventory can keep both a normalized comparison value and a display value. That lets the checker compare consistently while documentation still uses the notation familiar to each audience.

Classify an overlap before deciding it is a conflict

Keep the project map separate from the outside world

HotkeyRadar uses two stores for a reason. Shortcut Sets are for the assignments inside one project or product. My Shortcuts is for combinations already used elsewhere. That separation avoids treating every external reuse as if it were an internal project duplicate.

When a project grows, create one set per coherent scope rather than one giant list containing unrelated apps. A video editor, a browser extension, and an internal web app may all use Ctrl + Shift + P legitimately if their active contexts never overlap. The inventory should preserve that context instead of forcing a single global answer.

Add a change ledger, not just a final state

Shortcut maps drift when documentation is overwritten in place. Keep a small change record with the old assignment, new assignment, reason, date, and owner. A simple CSV-style record is enough:

action,old_shortcut,new_shortcut,scope,status,reason
Open palette,Ctrl+P,Ctrl+Shift+P,app-wide,active,Avoid browser print command
Quick search,Alt+K,,project-only,retired,Feature removed

Do not store passwords, API keys, customer data, or unrelated confidential notes in the shortcut inventory.

Use HotkeyRadar for repeatable checks, not as a universal scanner

For a candidate assignment, the checker can compare the normalized combination with its documented browser and operating-system records, the active Shortcut Set, and relevant items saved in My Shortcuts. It does not enumerate every installed desktop app, extension, keyboard remapper, input method, or custom system setting.

The current tool also lets you export a full JSON backup and CSV/reference outputs. Export a backup before clearing browser site data or moving the inventory to another device. The JSON backup is the recovery format; a CSV is useful for review but does not replace the full structured backup.

Separate ownership from documentation

A vendor-controlled shortcut and a project-controlled shortcut should not be changed through the same process. Record the source of truth for each row:

• Vendor-controlled: current official documentation or the product's own shortcut settings.
• Project-controlled: the project configuration and named owner.
• User-customized: local preference, extension setting, or remapper configuration.
• Unknown: keep it flagged until the assignment can be reproduced or sourced.

This makes later audits faster. A source date also matters because browser and application shortcuts can change, and Firefox now supports customization for many shortcuts in current releases.

Review character-only shortcuts separately

W3C guidance for web content treats character-only shortcuts as an accessibility risk because speech input or accidental key presses can trigger them. If a web interface uses a printable character by itself, provide a way to turn the shortcut off, remap it with a non-character modifier, or limit it to the component while that component has focus.

The inventory should record which control applies. “Active only while the canvas has focus” is more useful than a generic accessibility checkbox.

A practical handoff package

A shortcut map is ready for handoff when another person can answer what is active, where it applies, who owns it, which source was checked, and how to restore the current state. Keep a dated backup with the project documentation and include unresolved overlaps instead of hiding them.

For one proposed combination rather than a full inventory, use Keyboard Shortcut Conflicts: What to Check Before Assigning a Hotkey. For character-only commands that need a separate accessibility review, use Single-Key Keyboard Shortcuts: Avoid Accidental Triggers from Speech Input.

Reference points used in this guide

• Mozilla — Customize keyboard shortcuts in Firefox
• W3C — Understanding Character Key Shortcuts