Access Pledge - decide 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, and get the provision set decided - depth, captioning and interpretation, the request channel and the disability data it creates, economic access and the slot itself - then the one public accessibility page, the request form, and an answer to each request. Free in your browser: the funding pole's consequences, the venue criteria sheet (a signed venue deletes half of the depth menu), the four menus re-ranked with deleted rungs struck, the provision set sized, owned and funded with known needs first, the people attendees turn to, the WCAG 2.2 AA digital checklist, each pasted request classified against the set with its lead time, and Markdown, CSV and JSON exports. A metered run writes the plan, or the page, the form and the answers. It decides the bar, not delivery, is not the code-of-conduct response team, is not legal advice, and never repeats a diagnosis. Built on the SkillSafe skill @samber/event-accessibility-inclusion, from samber/dev-event-organizer-skills (MIT), by Samuel Berthe.
gpt-terra Every public app is built from a security-scanned skill and must pass a clean scan — skill and frontend — before it can be listed. Have a skill of your own? Turn it into an app — or read the step-by-step walkthrough.