Web4All Accessibility sprint

[jasongrout]

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.

[Ruv7]

Exciting! So great to see this happening...

[parente]

I've tweeted a link to this issue from my personal account to raise visibility: https://twitter.com/parente/status/1121115705183625221.

[Ruv7]

Ah good call, I've retweeted from the Jupyter account.

[vidartf]

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!

[ellisonbg]

@jasongrout can you post a summary or links to work done?

[jasongrout]

Yes, great idea.

[jasongrout]

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
jupyterlab/jupyterlab#6361
jupyterlab/jupyterlab#6369

CC @zorkow @ivanov

[isabela-pf]

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?

[Ruv7]

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.

[ryanlovett]

@isabela-pf Do you know if all issues and PRs from the forked repo were transferred over?

[isabela-pf]

@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.

[ryanlovett]

Oh that'd be awesome, thanks! I do recall that I a lot of folks seemed tremendously productive at the sprint.

[isabela-pf]

As promised, I've returned with a summary! In order of Jason's previous comment:

• Almost all issues in the forked repo were kindly transferred to the main JupyterLab repo by @clapierre. You can find them here.
• The issues and PRs not yet transferred to JupyterLab were note-based. I've opened a PR Add 2019 Web4All hackathon notes #41 to this repo (now that we are using it to store notes) to collect this and related links from the sprint. If you have more you want to add to it, please go ahead!
• #385 was broken up into other tickets a few times, but the results have finally made it into the main Lumino repo as jupyterlab/lumino #129, jupyterlab/lumino #131, and jupyterlab/lumino #132
• Since jupyterlab/jupyterlab #6360, #6361, and #6369 are all in the main JupyterLab repo and tagged accessibility, I am less worried about losing their information. #6369 is the only one still open in a draft state. There's also been related issues like jupyterlab/jupyterlab #4878 which we are still discussing.

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.

[ryanlovett]

Fantastic, thanks so much to you and @clapierre!