GratisAI accessibility · map keyboard shortcut collisions across explicit action scopes · local-first FREE TIER 1 Free Run Available
shortcut-scope matrix · scored comparison matrix

Map Keyboard Shortcut Collisions Across Explicit Action Scopes

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.

1 · Action code | modifier+key chord | global or named focus scope

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.

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.

Perspective: Before: shortcut aliases and widget names hid overlapping key actions. After: a declared modifier model and explicit scope graph expose each colliding pair.

2 · Read the shortcut-scope matrix

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.

Optional filing controls are a local prototype.

Checkout is unavailable. The reading above is complete; print, CSV and five local summaries are optional enhancements, not hidden answers.

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.

Boundary and sources

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.

Mechanism: competence-autonomy-loop

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.