Date: Thursday, December 16th
Starts at 9AM PST (in your timezone)
Should end two hours later around 11 AM PST
Location: event zoom (global dial-in options)
jupyter is a tool for scientists, but doesn't yet meet the needs of all scientists. this event will increase the visibility and capabilities of accessibility within the jupyter development community.
name | org | username |
---|---|---|
tonyfast | quansight | @tonyfast |
Jason Weill | AWS | @jweill-aws |
Martha Cryan | IBM | @marthacryan |
Piyush Jain | AWS | @3coins |
Ely | Bloomberg | @ohrely |
Ahmed Fasih | Bloomberg | @fasiha |
Frederic Collonval | QuantStack | @fcollonval |
Gabriel Fouasnon | Quansight | @gabalafou |
the hands-on accessibility workshop will consider the intersections of accessibility and jupyter. we'll work together to share tools and experience with accessibility. we'll think about what we can do to improve quality of jupyter across the technical spectrum.
our primary theme at this event will be using your system's tools to measure the accessibility of jupyter's retrolab. retrolab's version 7.0 release is meant to improve the accessibility of jupyter, and is our closest offering to being accessible.
attendees will gain tools and confidence to advocate for accessibility concerns during the development of jupyter products.
current and aspiring jupyter contributors. all levels of accessiblity experience welcome.
numpy accessibility guidelines
mozilla digital accessibility overview
[:05-:10] (tony/ely) welcome
[:10-:17] (ely) intro to accessibility concepts (prereading recap)
[:17-:25] group digital accessibility quiz
[:25-:30] (tony) why are we here? an introduction the jupyter accessibility initiative
Learn More →
[:30-:35] (tony) using WAVE (the web accessibility evaluation tool)
[:35-:45] (gabriel) accessibility insight inspector and accessibility tree
[:45-1:40] breakout rooms identifying and testing common accessibility problems
[1:40-2:00] reconvene to share our experiences