Budget Shortcut Collisions Before Users Hit Them
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.
1 · screen | shortcuts audited | collisions found
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.
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.
Perspective: 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.
2 · Read the collision budget slate
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.
Paid layer: collision budget slate print and history
one-time step · the free reading above stays complete
Free tier
- one complete collision budget slate run in the app
- three samples plus unlimited article-demo runs
- unwatermarked result text and an explicit, user-triggered state link
What $4 one-time adds
- print the collision budget slate with its row workings
- CSV of collisions over budget and row explanations
- last five reading summaries saved in this browser profile
$4 once for repeated filing of the collision budget slate, not for a better answer. Illustrative time basis: avoiding one five-minute manual reformat per saved reading; no market-price or guaranteed-savings claim.
Local history (this device)
- No saved runs yet — your first run files here.
Checkout is unavailable until a payment link is configured. The optional unlock is browser-local, profile-scoped and best-effort, not server-verified access. Clearing browser data can remove it; there is no account or cross-device recovery.
Boundary and sources
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.
- 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.
Mechanism: competence-autonomy-loop
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.