Team update - Feb 09, 2022

[trallard]

This is a @Quansight-Labs/czi-a11y-grant team sync 🎉🎉🎉! This is a way for the Team Members to provide status reports on what they've been up to this week and request help and attention for things they are working on. This issue will be closed at the end of the day.

Copy and paste the template below, and answer questions as you wish!

Response Template

**Thanks I'd like to give 🙌**
- So-and-so helped me out a lot with XXX...
- Thanks for Jo's work on the XXX repo...

**Updates from last week :heavy_check_mark:**
- I worked towards deliverable: <link-to-deliverable>
- I had a meeting with ABC

**Challenges I faced and things I'd like assistance with 🙏**
- I had a hard time figuring out ...
- Could somebody take a look at ...

**My availability for next week**
- I'll be off on XXX day...
- I've got several meetings this week...

🔍 Needs Triage:

The Needs Triage issues require an initial assessment and labeling.

• Investigate accessibility statements

🎯 Project boards

Please make sure the boards reflect the current status of the project.

Jupyter a11y grant project

[isabela-pf]

Thanks I'd like to give 🙌

• Thanks to all of you for your patience in general. It helps my nerves.

Updates from last week ✔️

• Some issue chatting! Summary is yes to exploring JupyterLab theme configuration before contrast changes to the main theme, need to get more feedback from people, interest in a regular outreach/reminder of newest versions of these apps with a request for feedback. jupyter/accessibility #65 APCA over WCAG 2
• Captioner (almost) scheduled for March events! Just waiting for final contract things.
• The roadmap blog post is now a PR for cross-posting on the Labs blog.

Challenges I faced and things I'd like assistance with 🙏

My availability for next week

• I'll be off on February 10 and 11. So when you are reading this. 😊

[gabalafou]

Thanks I'd like to give 🙌

• Thanks to @isabela-pf for carrying forward all of the Jupyter Accessibility post-production work, including among other things, this PR: Add/update alt text in documentation jupyter/jupyter#607
• Double thanks to @isabela-pf for being so supportive and offering to intro my question at the JupyterLab team meeting
• Thanks to @trallard for pair programming with me. I can't believe I've gone this many years without knowing mkdir -p a/b/c/d/e/f/etc :)
• Thanks to @tonyfast also for pairing with me and imagining wide where we can take this work

Updates from last week ✔️

• A couple weeks ago I demoed using Playwright to produce axe reports. The code lives on the axe branch of the gabalafou/accessibility fork. Things I've added since then:
  • Now in JSON!
  • Now you can run it on your machine! in theory!
    • in theory just three steps after cloning the repo and cd accessibility/tests/retrolab:
      1. install mamba, then
      2. mamba install nox, then
      3. run nox -s test
• I stayed up wayyyyyy too late last night getting this up: http://gabalafou.com:8888/lab (password hints: starts with an i, name for jupyter predecessor, but in all lowercase for the password)
  • because bleepity bleep bleep computers and I couldn't get it to work on Binder or GitPod 🤬 😆

Challenges I faced and things I'd like assistance with 🙏

• Conda environments, continuous integration, consistent builds, help! :) I appreciate the help I've been getting from you all and I'm going to continue to need help on this for a while I think :)
• Would it make sense to allow me to create branches and pull requests directly against the jupyter/accessibility repo instead of my fork gabalafou/accessibility?
• Group discussion: where should we put reports?

My availability for next week

• Normal availability

[trallard]

@gabalafou - where do we put the a11y tests reports

• for now, we can put into artefacts
• later on, we can think about a hosted approach