Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We鈥檒l occasionally send you account related emails.

Already on GitHub? Sign in to your account

Team update - May 31, 2023 #215

Closed
trallard opened this issue May 31, 2023 · 2 comments
Closed

Team update - May 31, 2023 #215

trallard opened this issue May 31, 2023 · 2 comments
Labels
type: internal-pm Items related to how we manage the project internally type: team-update

Comments

@trallard
Copy link
Member

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

@trallard trallard added type: internal-pm Items related to how we manage the project internally type: team-update labels May 31, 2023
@gabalafou
Copy link
Contributor

gabalafou commented Jun 1, 2023

Thanks I'd like to give 馃檶

  • I'd like to give thanks to Tania for all the behind-the-scenes work in putting the accessibility team together.
  • I'd also like to give thanks to Isabela for listening to and answering my questions on Monday's call.

Updates from last week 鉁旓笍

  • I worked towards deliverable: TEST - Write test that verifies that each "tab-able" element on the initial page has a visible focus indicator聽#199
    • Draft PR: Focus visible test聽jupyter-a11y-testing#33
    • I'm working on a PR for Lumino (not up yet) to fix an issue in the Lumino menubar that causes the test to fail (there are a couple different ways to move focus away from the menubar without the focus styling changing)
  • I've watched recordings for a number of Phosphor mentor sessions from 2019:
    • 2019.02.08
    • 2019.02.15
    • 2019.03.22
    • 2019.05.17
    • 2019.07.29 - interesting tidbit at 42:15, Chris talks about how the menubar is not ARIA conformant because of the exact focus issue that I'm working on right now:

    "by the ARIA standard what should be happening is these particular items, menu items, should be gaining focus as we're moving up and down but instead we're tagging them with a p-mod-active attribute. And there were some subtle focus handling issues that made it really difficult to do that, to basically make each individual menu item focusable, and still have clean event handling when we do this because focus events don't propagate the same way on all platforms, so that's something we'll have to go back and look at"

    • 2019.08.05 - menu accessibility and focus discussed at 53:25. Important note: Chris said fixing the focus issue would be harding the Menu class than in the MenuBar class. (I'm not sure why yet.)

I plan to also watch the videos that cover the following: Widget class (part 2), FocusTracker, TabBar.

Before the end of this week, before Camp Quansight, I would like to accomplish the following goals:

Challenges I faced and things I'd like assistance with 馃檹

  • I'm okay.

My availability for next week

  • Camp Quansight

Important items for discussion 馃挰

  • Camp Quansight accessibility reference notebook sprint? What should we name the notebook? Where should it live? I'm thinking jupyter/accessibility.

@isabela-pf
Copy link
Collaborator

Thanks I'd like to give 馃檶

Updates from last week 鉁旓笍

  • I've had to spend more time on other projects this week, so I haven't completed anything substantial for this one this week. I commented on the Notebook 7 release discussion per request.

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
type: internal-pm Items related to how we manage the project internally type: team-update
Projects
Status: Done 馃挭馃従
Development

No branches or pull requests

3 participants