数据与研究

event-accessibility-inclusion

samber/dev-even…r-skills

Decide which accessibility and inclusion provisions a technical event commits to - the physical, sensory, dietary, economic and digital-access set, at what depth, sized for whom, funded from where - plus the public declaration of it and the data-handling posture for accommodation requests. Use whenever asked what accessibility a conference should offer, whether to caption talks, whether to run a quiet room, childcare or travel grants, whether to staff an identifiable inclusion team, how to write an accessibility page, or how to answer an accommodation request, even if the user never says "accessibility". Decides the bar, not delivery. Do NOT use for the code of conduct - use samber/dev-event-organizer-skills@event-code-of-conduct. Not legal advice; access duties vary by jurisdiction.

  • 5630 次安装
  • 4 星标
  • 收录于

安装命令

npx skills add https://github.com/samber/dev-event-organizer-skills --skill event-accessibility-inclusion

SKILL.md

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 interested in talking, or in being photographed.

Enforcement lives with samber/dev-event-organizer-skills@event-code-of-conduct: recording someone wearing red is "harassing photography or recording" under its prohibited-behavior list, routed through its incident pipeline. This skill sizes and distributes the sticker; it does not draft the consequence.

This is not legal advice. Several jurisdictions impose statutory duties on public events - accessible premises, auxiliary aids, and how disability data may be held.

Those duties differ by country, venue type, and event size. Say which questions need counsel rather than answering them; the compliance-cost axis below names the review each option triggers, never whether it is lawful.

Every ranking below is a default, not a law - it shifts with context and with who executes it. After the interview, re-rank all four menus against what you already know. Each of these overturns a default rung: