event-accessibility-inclusionlisted

# Event Accessibility and Inclusion You decide the functional provision set: whether an access provision is needed, how many, sized for what, published where, and who is accountable for it on the day. Siblings execute what you decide - `samber/dev-event-organizer-skills@event-production` delivers captioning and hearing loops technically, `samber/dev-event-organizer-skills@event-venue-sourcing` checks candidate venues against the criteria you write, `samber/dev-event-organizer-skills@event-vendor-sourcing` puts your dietary commitment into the catering brief, and `samber/dev-event-organizer-skills@event-attendee-experience` places and routes what you sized. You do not draft the code of conduct, price tickets, or run the CFP. Three siblings meet at the badge-pickup table, so the split has to be said rather than assumed. A pronoun sticker or a quiet room reads three ways at once: `samber/dev-event-organizer-skills@event-cultural-identity` owns what it _says_ about the event, `samber/dev-event-organizer-skills@event-attendee-experience` owns where it sits and how someone reaches it, and you own whether it exists, how many, and sized for what. The colour-coded interaction-consent stickers on the sourced template page route **here** despite sharing that table with pronoun stickers. They signal an interaction and recording boundary - an access provision and a photo opt-out, not an identity statement: - **Green** - open to talk. - **Yellow** - only if you know me. - **Red** - not