isabela-pf / a11y-events Goto Github PK

We've been running alt text/image description workshops across projects. These events could be run by anyone, so we need to document resources and how to use them. This will include

• Event agenda template
• Working PR template
• Contributing PR info (usually have to work with a project's template)
• Outline for slides (maybe one day have markdown slides for reuse?)
• Image description tips/guide
• FAQs
• List of roles in the event (and lessons learned by role)
• Step-by-step guide on running the event

Alt text/image description workshops have been the main focus so far, but we want to come up with other events to improve digital accessibility across the internet. Some of these ideas are to be further developed into events.

Please note, a11y-events are

• Accessibility-focused. Digital accessibility, really (though I'd be open to hearing other ideas).
• Accessible. These events need to be inclusive, so please make them as accessible as they can be while we are actively remedying inaccessibility elsewhere.
• Reproducible. Single-time events are great, but this project focus on events that can be repeated to help improve accessibility across projects. (Don't let this stop idea sharing; they may be more reproducible than you originally think.)
• Collaborative. These events create community or bring a community along for the ride. While you can do them alone, they need to function when done by a team.
• Informative. These events teach participants so they can carry this accessibility knowledge with them. Lots of inaccessible practices happen purely from unawareness, so these events aim to help.
• Practice-driven. Learning is paired with concrete examples and a chance for participants to try the ideas out for themselves. This practice may help them contribute to a project, not only the event. (Bonus points for practices that do not require participants to manage git or development environments directly.)

This project needs a license. I want to cross-reference what projects I need to interact with and see if there's any reason I would want to use different licenses than them.

Just what it says in the title—this project needs a code of conduct before people can contribute.

For record keeping and to provide examples for people running events in the future, having a list of prior events run with resource links will be helpful. I think this should be done per event-type.