accessibility · local-first tool
Walk an Event Route and Record the Barriers You Find
Arrival, toilet access, seating, wayfinding, and leaving are separate parts of the same route.
Record a user's own barrier, location, impact, proposed fix, owner, and confirmation status across the event journey.
What changes the result: your event route, participant priorities, and the venue's actual layout.
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 open and received entries separately from verified entries. Missing source labels remain visible. The app cannot decide whether an agency, school, provider, or contract has received enough documentation.
Question to keep open: Should an organizer fix the highest-impact barrier first or remove a smaller barrier that blocks many people?
Boundary: This is a visitor checklist, not a professional accessibility audit or building-code assessment. Verify conditions with the venue and a qualified specialist where needed.
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.