Budget Shortcut Collisions Before Users Hit Them — Free
Every shortcut an assistive technology already owns is a trap. Count collisions per screen against a budget you set, and see which screens need remapping first.
The proof surface
Keyboard burden tools time repeated navigation. This audits the shortcut layer itself: collisions found in an audit you conduct, measured against a per-screen budget, not a timing.
Why the flat version breaks
Auditing against one AT only
Different tools own different keys.
Treating the budget as compliance
It is your planning line, not a standard.
Counting shortcuts instead of collisions
A large shortcut set is fine if nothing is stolen.
How to work the collision budget slate
List each screen’s shortcuts and test them with the assistive technologies your audience uses — command sets differ between tools and versions. Enter what you verified, not what the manual implies.
The sample tolerates one collision per screen while remapping is planned; zero is the honest long-term target. The budget is a planning knob, not a permission slip.
The editor found three collisions against a budget of one — two over, flagged. The list view sits exactly at its budget and adds nothing. Collisions cannot exceed the shortcuts audited; the tool rejects that row.
The summary totals the over-budget collisions so the queue has a size. Record which AT command each collision steals in your own notes — the tool only counts, and a low count never proves a screen is usable.
What the collision budget slate replaces
| Question | Before | Visible working |
|---|---|---|
| Auditing against one AT only | Different tools own different keys. | Set a budget you can defend |
| Treating the budget as compliance | It is your planning line, not a standard. | Count only what is over budget |
| Counting shortcuts instead of collisions | A large shortcut set is fine if nothing is stolen. | Remap the worst screen first |
A local arithmetic aid replaces hand calculation, not expert review. No paid AI service is needed.
Run it on the samples, right here
FIRST-LOAD
Input is processed locally and a draft is saved automatically in this browser profile when storage is available. Reset to sample clears that draft; Pro history has its own clear button. A state link encodes your inputs in its URL: share only non-sensitive rows. Browser history, clipboard and anyone receiving the link may retain it. Optional AI use below leaves this device; it is not required.
Audit arithmetic on collisions you verified by hand. Not an accessibility certification; command sets vary by assistive technology and version — test with real AT and real users.
Data note: Everything runs in this browser tab on the collision budget slate: your screen | shortcuts audited | collisions found stays on this device, nothing is uploaded, and the reading is rebuilt only when you press run.
Go deeper: the companion app files the same reading as a triage clipboard with three lanes
The article demo above runs without limits. The companion app keeps a local history, exports the rows as CSV, prints the collision budget slate reading, and holds your drafts on this device — one free run, then $ 4 one-time for the layer that keeps filing.
The collision budget slate reading is complete for free. The optional $4 layer adds print, row CSV and the last five local reading summaries; it does not add hidden answers. Checkout is not configured yet; the article demo remains unlimited.
Open the budget shortcut collisions before users hit them companionBoundary
Audit arithmetic on collisions you verified by hand. Not an accessibility certification; command sets vary by assistive technology and version — test with real AT and real users.
What this is built on
- Method: The editor found three collisions against a budget of one — two over, flagged. The list view sits exactly at its budget and adds nothing. Collisions cannot exceed the shortcuts audited; the tool rejects that row.
- All sample records are invented examples. The app does not fetch measurements, policies, files or personal records.
- Google’s official pricing page, fetched 2026-09-28, lists free-tier access including AI Studio. Optional formatting only; limits and availability can change. Free-tier content may be used to improve products. Never paste private records there.
Before: Different tools own different keys. After: the collision budget slate shows the working beside each named row so the reader can change the assumption and inspect the consequence.
Optional AI formatting, not calculation
For this collision budget slate, use the free AI Studio interface only if available to you, with no paid API key. Manual entry completes the same workflow for free. Supply only fictional or non-sensitive notes. Review its output against the source; never paste unresolved questions into the numeric rows.
Format my non-sensitive notes for a collision budget slate. Return plain rows only: screen | shortcuts audited | collisions found. Preserve supplied quantities exactly. Do not guess missing values; list questions separately. Do not calculate or add advice. I will check every row before pasting into the local tool.
Accepted schema: screen | shortcuts audited | collisions found. No AI response is executed as code.