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 - Sep 28, 2022 #160

Closed
trallard opened this issue Sep 28, 2022 · 4 comments
Closed

Team update - Sep 28, 2022 #160

trallard opened this issue Sep 28, 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 Sep 28, 2022
@steff456
Copy link

Updates from last week ✔️

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

  • I'm ok

My availability for next week

  • I'll be here

Important items for discussion 💬

  • I don't have anything super important to discuss

@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 think I'm okay right now.

My availability for next week

  • I'll be here all week.

Important items for discussion 💬

  • Eventually the new mockups, but I think that doesn't fit as well in an update-focused meeting.

@trallard
Copy link
Member Author

  • @steff456
    • working on pygments - some pygments working there already 🎉 needs some polishing and bits here and there
    • will then move onto the hamburger/ellipsis fix issues

  • @gabalafou
    • will be moving to Colombia next week - so timezones will be slightly different from usual
    • 🎉 got his expect-axe-playwright PR merged after a while
    • learned about pa11y + CI

--

@gabalafou
Copy link
Contributor

Thanks I'd like to give 🙌

  • @isabela-pf for organizing the vote to elect a representative from the Jupyter Accessibility Subproject to the Jupyter Software Steering Council.

Updates from last week ✔️

I made a mistake this week and thought, maybe I'll use Monday and Tuesday to clear some small tasks from my plate, and then those ended up just taking up all my time. So the following bullet points are things I've worked on that are accessibility-related but not directly related to accessibility in Jupyter.

  • Good news: Finished upstreaming my changes to expect-axe-playwright. Bad news: not sure we'll use it, and it took too much of my time this week.
  • Rename toBeAccessible to toPassAxe Widen/expect-axe-playwright#24. Finished this PR, which felt like doing a little bit of public service. The aim here was to prevent unintentionally spreading the idea among developers that there's an automated tool out there that can stamp your page or app as "accessible" or not.
  • Allow matcher to accept Axe results object Widen/expect-axe-playwright#23. Finished this PR. It will allow us to stop using my fork of expect-axe-playwright.
  • Pa11y Quansight/Quansight-website#262. Worked some more on adding Pa11y-CI to the Quansight website. Discovered more obstacles, specifically the default configuration for Axe flags a bunch of elements on the site for contrast that might not have contrast issues. These elements either have a background image or otherwise overlap some other element, and for some reason, that makes Axe incapable of ascertaining the foreground/background contrast ratio. So I'm going to have to hide a bunch of elements during testing in order to get the site to pass the CI/CD run or figure out a way to configure Axe differently.

My availability for next week

  • I am taking Monday off.

@trallard trallard closed this as completed Oct 3, 2022
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