🏃🏽‍♀️ - Start planning for next cycle

[trallard]

• @isabela-pf to transfer the notes for the upcoming sprint planning
• @trallard to open the sprint planning issue

[isabela-pf]

Based on out discussion of what we thought could happen in the next work cycle…

There's a big question we haven't answered around what the focus should be. Basically,

• Do we want to build immediately off this sprint and continue testing efforts until we are at a preferred stopping point?
• Or do we switch work topics to make progress on another area of the grant next (ex. making fixes in JupyterLab)?

It seems like we're open to either, really, and I also see a middle ground. For example, we could switch to making fixes in JupyterLab focused on the errors we currently see in the testing efforts. This could give us a chance to test the tests and addressing other parts of our goals, but this example is more my opinion.

More specific tasks that came up during the discussion:

• Imagine test reporting options, possibly start developing (probably involves everyone)
• Bring one of the brainstormed events out of development and start testing it in the wild (@isabela-pf)
• "Curate extreme themes" (quoting @tonyfast) in jupyter/accessibility for JupyterLab. For example, high contrast theme, grayscale, and similar accessibility-oriented prompts. (probably involves everyone)
• Fix tab traps in the Lumino menu bar and then in JupyterLab if more adjustments are needed (@gabalafou)

cc: @tonyfast and @gabalafou please correct me if I've misrepresented your ideas.

[gabalafou]

Thanks @isabela-pf for accurately representing our ideas :)
(or mine at least, since I can't speak for Tony)

Imagine test reporting options, possibly start developing (probably involves everyone)

Can you elaborate on this one? I've somewhat already forgotten.

[isabela-pf]

Imagine test reporting options, possibly start developing (probably involves everyone)
Can you elaborate on this one? I've somewhat already forgotten.

This was to start thinking about how we want to report test results to the community, which I think could be a lot of things and depends more on what we decide. For example

• How do we communicate that these tests are not the end-all-be-all for accessibility?
• Where do these reports live in relation to the main projects? What info do they include?
• What would a website with a list of reports include? What ways would we want people to interact with it?
• Is there a way to tie this into some kind of social media updates for accountability?

All this kind of big picture stuff we haven't considered since you all have been doing the very hard work of having tests at all. Did that help?

[isabela-pf]

Based on our discussion, I'll open or append the above comments to issues with the sprint-candidate tag so they don't get lost in the planning.

Edit: here are the issues added.

• Imagine test reporting options #131
• Test out a new contribution event! #132
• Curate JupyterLab themes #133
• Fix tab traps in JupyterLab #134

[trallard]

Re grant's milestones I would like to add to the discussion:

• [DEL] - Adequate colour contrast for interactive regions. #8 - feed into the themes bit
• [GOAL] - Support for 400% zoom. #7
• [DEL] - JupyterLab should be navigable by keyboard alone. #6 - this tackles the tab traps I think...
• WCAG 2.2. compliance updates/planning and other guidelines? [GOAL] - Align efforts for WCAG 2.2 compliance #9
• [TEST] - Add automated accessibility tests to Jupyterlab's documentation theme #14 - seems now like a low-hanging fruit 🍎 with the acquired knowledge and complexity vs a full fledged app like JLab
• [Phase 2] - WCAG 2.2/2.1 compliance for blind users #15 what would be needed here? - this is for @isabela-pf mostly

Not in an issue but:

1. Follow up on governance
2. Repo - compass/testing tools (discussed with Isabela not sure if we followed through)
3. Updates to a11y repo: templates (issues, audits, re-structure)

[trallard]

Since we had this chat + @isabela-pf created all the issues I will close this now 👍🏽