For organizers deciding what accessibility their event commits to
Access PledgeDecide your event's accessibility provisions, publish them on one page, and answer every request.
Enter who funds it, whether the venue is signed, the needs already known, who owns accessibility and when the set must be published. Free in your browser, in the order the skill sets: the venue criteria first (a signed venue deletes half of the depth menu for good), the four menus re-ranked for your answers with every ruled-out rung struck - provision depth, captioning and interpretation, the request channel and the disability data it creates, and economic access after the slot check - then every provision sized, owned and funded, known needs first. A run writes the plan, or the one public page, the request form and an answer to each request. This decides the bar, not delivery, it is not the code-of-conduct response team, and it is not legal advice: what a jurisdiction requires is a question for counsel. It never invents a provision, a budget or a date, never asks for or repeats a diagnosis, and labels every number of its own self-set.
The event free
Blank means today. It is also the page's last-updated date.
The interview free
The skill's eleven questions, Q3 (the needs already known) in the next card. Each answer re-ranks the menus below; every move names the answer behind it.
Known needs and the building free
For example: Live captions | asked at last edition's desk | captioning in the main room. Describe each need by what it asks for - never a diagnosis.
The request flow and the requests free
Start a block with "received: YYYY-MM-DD" when it did not arrive today. Each is read against the set; the answer never repeats a diagnosis it mentions.
The provision set, worked out free
What the page flags
Who funds it (Q1) and the venue (Q2)
The four menus - re-ranked for your answers, deleted rungs struck
Before menu 4: the slot itself (Q10)
The provision set - known needs first, each sized, owned and funded
Known needs (Q3) and what answers each
The venue criteria sheet
The people attendees turn to (Q11)
The request channel and the data it creates (menu 3)
Each pasted request against the set
The digital layer - the event's own website, forms, schedule and stream
Hand-offs to the sibling skills, and the stated gaps
The files free
The criteria sheet for venue sourcing, the provision set as a spreadsheet, the draft page skeleton and everything the page worked out.
The plan metered
Pricing as soon as the session is ready...
Sign inThe reply could not be read. Here it is as it came back:
Caveats
The page's check of this reply
Saved pledges
How it works - and what is sourced
The order is the skill's: the interview first; who funds the provision line (it moves the depth, captioning and economic menus, never the request channel - once someone discloses, a volunteer team and a foundation hold the same duty of care); the venue (unsigned, the criteria sheet goes to venue sourcing first; signed, what the building lacks is deleted and stated, never promised around); the four menus re-ranked for the answers, every move named and every ruled-out rung deleted rather than demoted - an accessibility page describing provisions not yet secured, production capability read as captioning, an unvetted automatic feed announced as coverage, requests routed to a registration desk with no owner, an unbudgeted hardship promise; the slot checked before any childcare rung; the provision set sized, owned and funded with known needs first; the people attendees turn to (a briefed, identifiable inclusion team at a large event, the organizers at a small one - never the code-of-conduct response team's intake); the request channel with its owner, lead time and retention stated on the form; every request answered, declines included; and the digital layer, which covers the event's own website and stream only.
Sourced from the skill's references, each with its provenance: the depth range across published events (one foundation's templated page, a 2019 community conference's pages - historical, FOSDEM 2026's short page, a hackathon guide), the quiet-space siting rules and the one sourced sizing figure (about 5% of attendees at once - an observation, not a standard), the interaction-consent stickers, the dietary categories and fallbacks, the childcare ratios and vetting checklist, the subsidy ratio, the grant's access limit, and WCAG 2.2 AA for the digital layer. Self-set, and said so wherever used: the hard publish-by line, the volume and size thresholds, the low effort ceiling, the reserved seats per room, and your own lead time, turnaround and retention. The page reads needs and requests by keywords - read them yourself when it says the owner decides.