-
Notifications
You must be signed in to change notification settings - Fork 33
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
Web4All Accessibility sprint #2
Comments
Exciting! So great to see this happening... |
I've tweeted a link to this issue from my personal account to raise visibility: https://twitter.com/parente/status/1121115705183625221. |
Ah good call, I've retweeted from the Jupyter account. |
I'll not be able to go, but if there is any work I can join in from remote, I'll try to contribute as best I can! |
@jasongrout can you post a summary or links to work done? |
Yes, great idea. |
The JupyterLab forked repo has some issues and PRs that need to be transferred to the main JLab repo: issues, PRs For phosphor, we have a work-in-progress PR open that we are discussing with @sccolbert: phosphorjs/phosphor#385 Additionally, there are some issues and PRs opened by participants in jlab itself: jupyterlab/jupyterlab#6360 |
Would it be okay to close this issue since the sprint has happened, there has been no discussion here in a few years, and we have followed up on some of the outcomes of the event in more current notes and PRs? |
Go for it, we can always reopen if someone disagrees or wants to discuss further. The only thing I would add is to say that if you want to link to any relevant materials you may be aware of that may help anyone who comes across this issue that could be good. It may help those who may not be as familiar with the other places to go for info. |
@isabela-pf Do you know if all issues and PRs from the forked repo were transferred over? |
I'll double check if we caught all of them. I know we've done some PRs to Lumino and JupyterLab in the past few months that did adapt this work, but I'll go track everything down and record it here before closing. |
Oh that'd be awesome, thanks! I do recall that I a lot of folks seemed tremendously productive at the sprint. |
As promised, I've returned with a summary! In order of Jason's previous comment:
Progress on all of this can also be found in our accessibility project though sometimes I'm delayed updating it. This is meant to gather everything still needing to be done to meet WCAG 2.1 compliance and more problems identified. Hope that helps! #41 should close this issue when it is merged. |
Fantastic, thanks so much to you and @clapierre! |
@ryanlovett & @jasongrout, you are all welcome and I for one am thrilled to see the progress you all have made on Jupyter to make it accessible. Actually I plan on highlighting this as one of our success stories to OSEP with the work the DIAGRAM Center has done in the community to help with making educational materials and tools accessible for students! |
Co-authored-by: Tania Allard <[email protected]>
The Web4All conference in San Francisco is planning a hackathon around JupyterLab accessibility issues on May 15 and 16.
Signup form is at https://docs.google.com/forms/d/e/1FAIpQLSfn4f-qdLHD4UQ0QeeJpHKul1KIcjGeamVyfSWSpBEqT8uR8g/viewform and closes April 30.
The text was updated successfully, but these errors were encountered: