-
Notifications
You must be signed in to change notification settings - Fork 39
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
Accessibility: Installing Jupyter Notebook Alpha version 7.0.0.a7 in one of our hubs! #3885
Comments
That's awesome! If showcasing these sorts of things on binder is insufficient, maybe there could be a test.datahub.berkeley.edu for testing and showcasing new technologies. |
@ryanlovett That sounds great! I am open to creating a new hub with a generic focus or specific focus (like accessibility.datahub.xx). Open to your perspectives on the best way forward. |
Would love to hear @shaneknapp's opinion too. |
@balajialg This is such a helpful thing to see. What did you use to generate the results, I'd love to be able to check results as I make updates to code and I'm sure there are other people working on these projects that feel the same way. Is this something we could fold into our workflows? Thanks so much! cc: @SylvainCorlay |
@afshin Thanks for your interest! I am copy-pasting my email conversation with Sylvain as that might throw light on your question. Please let me know if you need more information. We tested the binder link for Notebook 7.0 alpha shared on this page using the Axe Deque tool for which I have a professional edition. Shared below are the general issues highlighted by the automated checker. I have also attached a spreadsheet export from Axe that details all these issues in depth. I highlighted the critical and serious issues in yellow so that it may help you with prioritization hub.gke2.mybinder.org-Jupyter-Notebook-7.0-Alpha-Audit-2022-11-04.csv |
Thanks, @ryanlovett and the team for your support in deploying the a11y hub with the latest notebook version. I am closing this github issue as I am able to launch the latest Jupyter notebook using a11y hub. Thanks! |
Summary
I have been performing accessibility tests on the latest alpha version of Jupyter Notebook 7.0 which was released in the last couple of weeks . The latest version has a ton of accessibility changes including Code Mirror 6.0 + other UI updates which have improved the accessibility of the editor. To validate this claim by gathering concrete data, I opened Data 8 Project 3 Notebook in both Data 8 hub and the binder link showcasing v7.0.0.a7. Data 8 hub has retro version 0.3.21 which was released almost 6 months ago and the version in binder link was released in the last couple of weeks.
Results from Data 8 RetroLab audit:
Results from Jupyter Notebook v7.0.0.a7 audit:
Lots and lots of accessibility issues highlighted by the automated checker in v0.3.21 of the retro lab have been fixed in Jupyter Notebook vv7.0.0.a7. I realize that we may not be comfortable installing the alpha version as a stable release in our regularly used hubs. However, @ericvd-ucb and I would like our team to install the latest version in one of our hubs which is not regularly used like a workshop hub or high school hub, or even create a new hub focused on showcasing accessibility upgrades. That way, campus leadership is also aware of the progress made by the Jupyter ecosystem over the past year through concrete data and can do an apple-to-apple comparison (one hub having retro lab vs another having notebook v7.0) while doing an accessibility audit with Web Access.
If interested, Here are the results from the automated check with VSCode enabled in Datahub and Google Colab. The latest version had fewer "critical" and "serious" issues compared to the other tools.
Results from VSCode Audit:
Results from Google Colab Audit:
The above results are not comprehensive and need additional tests to validate my hypothesis. If you are curious to know more about the results of Keyboard and Screen Reader tests then please refer here.
User Stories
Acceptance criteria
Important information
Tasks to complete
Decision about installing the alpha version?
If yes to the above question, Installing the version in old hubs or new hubs?
The text was updated successfully, but these errors were encountered: