Team update - Apr 13, 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 foo...

**Updates from last week :heavy_check_mark:**
- I worked towards deliverable: <link-to-deliverable>

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

**My availability for next week**
- I'll be off on foo day...

**Important items for discussion 💬**
- I have a question about goal <link-to-goal>
- Can @foo give a comment on issue #NN ?
- I opened #NN for discussion, please chime in
- I need to discuss foo

🔍 Needs Triage

The Needs Triage issues require an initial assessment and labeling.

• Create proposal for 2022 summer internship

🎯 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 🙌

Updates from last week ✔️

• Started Add Workshop materials to compass #93. PR for event resource templates on my working, non-project specific repo. Right now I am putting in my generalized resources I've been developing them here so they can be edited publicly before contributing a more project-specific set to Jupyter.
• Started Scoping automated testing steps #95. I have a work in progress spreadsheet to track what tests we can get from and which WCAG standards don't seem relevant to JupyterLab at all (for example, video captions). This is the list I'll then help prioritize and figure out a list of JupyterLab configurations we'll want to set up for testing. I also checked in with Gabriel about what axe-core brings us since that's what has been in use so far.
• Followed up on Develop pathways for participatory community engagement #3. I now have an issue (on the previously mentioned a11y-events repo, but I'm happy to move it here if wanted) to list some of the ideas for future contributing events. Please add to it if you have ideas!
• Followed up on the Jupyter governance discussion. Since it came up at the last JupyterLab accessibility meeting, there is now a voting issue to determine where jupyter/accessibility will be within Jupyter governance (at least for now).
• Followed up on a community lead hoping to get feedback on JupyterLab accessibility fixes thus far. Nothing to show there yet.

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

• Nothing comes to mind immediately.

My availability for next week

• I'll be out of office on April 15.

Important items for discussion 💬

• We have a new PR for the jupyter/accessibility contributing guide. I'm going to review it, but I'd appreciate review from at least one other person.
• I'm not sure what a normal request for decision timeline is, but I think we should check in about @gabalafou's testing summary.

[gabalafou]

Thanks I'd like to give 🙌

• @tonyfast for listening and giving me advice on next steps with my JupyterLab PR

Updates from last week ✔️

• Updated my checkboxes PR with screen shots showing cross-platform compatibility
• Tried to fix merge conflict on that PR but ran into issue with git hook. Sent message on Gitter; waiting for reply.
• Had chats with Isabela and Tony re: axe-core
• Wrote an "RFD" (in scarequotes because I don't think it's reallly a RFD)

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

• Challenge: My checkboxes PR is not getting any movement on it. But I'm not sure I want assistance yet. Tony suggested that I ping a few people when it's ready. However, question for the group: should I raise an issue like "I'm having trouble with git hooks in the team meeting?" That meeting is big and busy, so I'm a little unsure if "help me on this potentially newb issue" is appropriate or not.

My availability for next week

• I'm available all next week, but taking three days the week after that (April 27-29)

Important items for discussion 💬

• My RFD

[tonyfast]

Thanks I'd like to give 🙌

• @gabalafou for his patience working through testing stuff.

Updates from last week ✔️

• I worked towards deliverable: Integrate playwright in jupyter/accessibility #92

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

• I had a hard time figuring playwright in conda

[gabalafou]

Action item from above:

• Think about way to avoid recurring pitfall (npx playwright vs conda playwright)

[trallard]

• @isabela-pf
  1. Thanks for opening the jupyter/accessibility voting issue Vote on jupyter/accessibility's status in the new Jupyter governance jupyter/accessibility#81
     Side note - maybe for future voting things, we can use the new polls on GH discussions https://github.blog/2022-04-12-whats-new-in-github-discussions-organization-discussions-polls-and-more/
  2. Scoping automated testing steps #95 started - can you please link to the spreadsheet there?
• @gabalafou

1. RFD deadline for comments & decision 19-04-2022 RFD - A11y Testing Phase 1 #97

• @tonyfast :
  1. Working on Integrate playwright in jupyter/accessibility #92 🎉 - got past the weird conda env and playwright issues
  2. Need to find a way to add decorators instead of the current templating -> separating concerns Python vs node
     🔑 learnings - if you have two different versions of JLab you only need to run the playwright tasks in the correct environment, and it should work across multiple JLab/retroLab versions

@tonyfast and @gabalafou will work on unifying their POCs in the upcoming weeks 🌱

RFD

• Can be found in: RFD - A11y Testing Phase 1 #97

---

Up for grabs tasks 🤚🏽

• Review https://github.com/jupyter/accessibility/pull/82/files