accessibility · local-first tool
Write an Event Access Request in the Format the Host Can Act On
A specific access request is easier to route when it says what, where, and by when—without requiring a diagnosis.
Draft a short, user-controlled request with requested format or arrangement, event, contact, and confirmation status.
What changes the result: the access detail you choose to share, event contact, and reply date.
Privacy: Calculations run in this browser tab. This tool has no input-upload, account, or AI endpoint. The site may send a page-view signal to Cloudflare; this tool does not add form entries to that signal. A draft is stored only if you choose “Save draft on this device”; that browser storage is not encrypted. Avoid identifiers or sensitive details, and delete saved drafts when finished.
Your entries
The starting rows below are fictional examples. Edit them, replace them with non-sensitive labels and values, or load the sample again. The result is not advice or a source verification.
Amount fields use the same units you enter; the app does not choose a currency. Dates are the ones you provide. Up to 100 rows per run.
Calculated output
What the calculation does
Count short labels that lack a source, location, review date, or confirmed status, depending on the row type. The tool stores pointers, not the underlying documents, meter accounts, access codes, or proof that a record is current.
Question to keep open: Should an access request describe a diagnosis or the specific arrangement that would make participation possible?
Boundary: This card does not determine legal duties or guarantee an accommodation. Share only the information you choose; confirm arrangements with the event organizer.
Copy includes the headline, aggregate metrics, and boundary—not the row-by-row input. The CSV contains entries you choose to download. Review it before sharing.