event-accessibility-inclusion

It depends on funding, venue status, known attendee needs, and staffing. The default for a community budget is a published accessibility page plus a staffed request channel; funded provisions like childcare or grants require a legal entity able to contract and disburse money.

With no budget line, publish that live captioning or interpretation is available on request with a stated lead time. Post-event corrected captions help recordings but never answer an in-room need, and production capability alone is not a captioning provision.

Route requests to a named person with a stated reply turnaround, and decide retention, access, and deletion rules before the channel opens. Make walk-up provisions like quiet rooms and reserved seating require no request at all.

Complimentary childcare reaches more families because any published fee filters out exactly the people the program serves. Subsidized childcare costs more organizer effort in fee handling and only wins when the budget line, not organizer hours, is the binding constraint.

Target WCAG 2.2 level AA on the event's own digital surfaces: website, registration and CFP forms, schedule, and livestream. A perfect automated score is not conformance, so exercise the registration flow end to end by keyboard alone.

No established seat-to-attendee ratio or square-footage rule exists in sourced practice. One unconference series observed roughly 5% of attendees in the quiet room at a time, but treat any sizing figure as self-set against the actual room available.