Team update - May 24, 2023

[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.

No issues need triage! 🎉

🎯 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 @trallard for help wrapping up testing logistics!

Updates from last week ✔️

• JupyterLab user testing for common workflows #184 Finishing logistics and payment.
• Rendered notebook user testing - Round 2 #147 (and also [DOC] - Add a11y documentation to the JupyterLab's contributor docs #18) test 2 results updated with issues found during the test. I also finished writing test 2 related issues finally.
• Reviewed @steff456's open PRs on jupyter/accessibility.

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

• I don't have anything right now.

My availability for next week

• I'll be here all week.

Important items for discussion 💬

• I don't think I have anything right now.

[gabalafou]

Thanks I'd like to give 🙌

• @isabela-pf for timely and thoughtful encouragement
• @steff456 also for team spirit and support at JupyterCon

Updates from last week ✔️
This week I worked on finishing the accessibility test I introduced at JupyterCon (focus visible):

• Focus visible test jupyter-a11y-testing#33

I spent most of my time this week trying to fix focus issues in the Lumino MenuBar class (PR forthcoming)

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

• A little under the weather this week, so a bit slower going than normal

My availability for next week

• I'll be off tomorrow / Friday! (May 26)

[trallard]

@isabela-pf
* For the Notebook Authoring Guide - needs some work; there are improvements needed in terms of structure
* Right now, it only seems like it will serve people proactively thinking about accessibility - since it is under "Jupyter", this would need to follow a comprehensive approach
* Link to Space telescope checklist https://iota-school.github.io/notebooks-for-all/exports/resources/event-hackathon/notebook-authoring-checklist/ (markdown version)
* Idea: maybe it could be reorganised around some principles
* Idea: contextualise some of the content to make it easier to follow
* Idea: @gabalafou could lead a sprint/breakout section at Camp Quansight to work on a notebook (or some notebooks) with some of the practices in the authoring notebooks 🎉 (some of the NumPy tutorials are pretty well written)

---

@gabalafou
* Gabriel has been in the focus world now - as a follow-up from his presentation at JupyterCon
* Reflections from JupyterCon - "intertwining code + narrative" is a very "academic centric" view of notebooks where a lot of folks tend to have laaaarge blocks of code instead
* Noting that JupyterCon is not entirely representative of the whole population using notebooks