Join us for the Jupyter Accessibility Workshops (Part 2)
I’m happy to announce the next pair of Jupyter accessibility workshops happening this March! As a part of the third community workshop cycle, these workshops are designed to increase accessibility knowledge within the ecosystem and make Jupyter projects more usable for disabled people.
With community feedback as the inspiration, the following two events will open up discussions around general accessibility foundations and evaluating software with manual testing. If learning, contributing, and making connections in accessibility spaces sounds interesting to you, please join us. No previous experience needed.
What was part 1?
If you noticed the “Part 2” in the title, you might want to visit the blog post announcing the last two workshops for more context.
We also have resources from the last two events available!
- January 15: How to build inclusive data representations with Frank Elavsky recording
- January 22: Writing image descriptions for documentation sprint recording
What’s up next?
Part 2: March 12 and 19
On March 12, we’ll be joined by Eric Bailey as he introduces us to accessibility and inclusive design strategies. This event will provide some much-needed foundation and common language for our community as we continue to make accessibility a collective priority. People have often asked me how to get started in considering accessibility in their day-to-day work, so we are extremely fortunate to learn from one of the best!
On March 19, it’s sprint time. For this event, we’ll be focused on learning how to manually audit software for accessibility. This skill is great no matter what you spend your time on, whether testing your own work, reviewing someone else’s, or understanding expected accessibility experiences. We’ll practice testing methods as a group before contributing our review to projects across the Jupyter ecosystem. Don’t be intimidated, though, all are welcome at this event; no prior Git or GitHub knowledge is necessary!
To find these events in your timezone, please visit the Jupyter community calendar.
Who can attend these events?
As with the last two, Jupyter accessibility workshops are open to everyone! These events are also entirely remote, so all you need is to be online. Each event is stand-alone, so you can sign up to attend one or all depending on your availability and interest.
Ideally, these events will be attended by a mix of
- Jupyter contributors to provide specific insight about the community and projects
- People with accessibility skills to advise on the knowledge areas the Jupyter community currently lacks
- Newcomers willing to learn and give us feedback on how to make these learning curves better for everyone
Please consider attending if any of these descriptions sound like you!
How do I sign up?
You can sign up for a Jupyter accessibility workshop individually. You are welcome to attend both events, though you will need to sign up on both forms. Please note that attendance is limited to about 40 attendees per event to make sure we can provide a quality experience with a small event team. (But don’t despair! Recordings of speaking events and notes for all events will be available to all afterwards.)
- March 12: Intro to accessibility and inclusive design with Eric Bailey sign up form
- March 19: Auditing in open source sprint sign up form
Where can I get more information?
These events are planned publicly on GitHub; you can explore the accessibility workshop planning repository for more information.
Thanks!
Once again, these events would not be possible without a number of people across the Jupyter community. My thanks wouldn’t be complete without acknowledgement for all Jovyans who have already joined in accessibility efforts, like our wonderful attendees from the last two events whose spirit keeps me inspired every day!
Of course, many thanks to the Jupyter Community Building Committee for supporting funded community events and being a constant presence throughout all our planning adventures. And thank you to the original team that proposed these workshops and made them possible.
