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’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Team update - Oct 26, 2022 #165

Closed
trallard opened this issue Oct 26, 2022 · 4 comments
Closed

Team update - Oct 26, 2022 #165

trallard opened this issue Oct 26, 2022 · 4 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 Oct 26, 2022
@isabela-pf
Copy link
Contributor

Thanks I'd like to give 🙌

Updates from last week ✔️

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

  • I'm surviving.

My availability for next week

  • I'll be out on October 31 and November 4. 🎃

Important items for discussion 💬

  • I don't think I have anything right now. I'm still trying to get feedback on zoom for JupyterLab, but I'm not sure how we call that done.

@steff456
Copy link

Thanks I'd like to give 🙌

  • @isabela-pf for addressing the comments of the blog post

Updates from last week ✔️

  • I added two new themes for the accessible-pygments package - PR: Add gotthard light and dark theme accessible-pygments#14
  • Started investigating the status of jupyterlab accessible themes repo:
    • The repo right now is very similar to the output of the jupyterlab's cookie cutter
    • The contents cannot be installable, so I'm not sure what's inside of it - all the readme instructions don't work
    • For future tasks inside the repo, I think we need to do a big cleanup and fix the repo
  • Realized that pygments isn't used as a backend for syntax highlighting in Jupyterlab
    • Right now jupyterlab uses marked.js which defaults to highlight.js, so we are not going to be able to use the accessible pygments extension
    • There's some issues regarding how to use pygments for the output of the cells

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

  • Defining what to do with accessible-pygments and next steps for color issues.

My availability for next week

  • I'll be here

Important items for discussion 💬

  • Next steps for the theme issue,
    • Do we want Jupyter themes with the colors of the themes available in accessible-pygments?

@gabalafou
Copy link
Contributor

Thanks I'd like to give 🙌

Updates from last week ✔️

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

  • I had a hard time figuring out what to do with the internship blog post, but @isabela-pf helped me out.
  • I need to do contrast ratio checking in the Playwright tests but I'm not sure what library or algorithm to use.

My availability for next week

  • Here all week!

Important items for discussion 💬

  • I'm not sure how I should stage and sequence my work on keyboard navigability. There are a lot of small changes I want to make. Each small change should be its own PR, but they should probably all ship together to avoid UX churn. For example, one of the changes I want to make is to put a visible focus indicator around each UI element that can receive focus. This would result in visible focus rings around the file names in the file browser. However, in another PR, I want to remove the files from the tab index. I don't want each individual file to be navigable by the tab key; rather, the user should tab into the file list and then use the up/down arrow keys to select individual files.
  • I have questions about color contrast and the new WCAG 2.2 guidelines for the focus indicator

@isabela-pf
Copy link
Contributor

Follow up notes:

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

4 participants