Low Vision Accessibility

The excellent accessibility audit provided for Jupyter Notebook is primarily is limited to WCAG 2.0 issues. It does not address many 2.1 issues, especially the extensions that were made for low vision.

The primary deficit for Jupyter Notebook is the inability to enlarge to 400% with full word wrapping.

I believe this is a CSS issue primarily, and it is easily solved. Structurally the Jupyter interface is extremely good, that is why the audit turned up so little. Having done audits professionally, I can say this is a good first audit report for Jupyter.

I am a member of the Accessibility Working Group and the Low Vision Task Force of the W3C, and I am very interested in seeing your work succeed. Also as one of the very few people to earn a PhD in Mathematics with congenital low vision I am thrilled to see STEM opened to young people like me.

I will be making a presentation this spring at the CSUN Assistive Technology Conference in Anaheim. My goal is to pull together as many people as possible to address accessibility tools for scientists with low vision.

I will follow soon with and extension of your fine accessibility audit that includes WCAG 2.1 extensions.

Best, Wayne Dick

2 Likes

Thanks for getting involved in this. Having more people with experience with this topic is (I think) one of the things needed to make progress.

Could you explain a bit more what this means or link to an example of “good” and “bad” behaviour to look at (doesn’t have to be a notebook any kind of example will do)? For me it sounds like the way to work on this is to open a notebook, set the zoom to 400% in your browser and look for text that is cut off instead of line wrapped. Is that it? What about having to scroll horizontally to read the text?

I tried to explore a bit and started a notebook server, then kept upping the zoom in my browser but it maxed out at 300%. Do you know if there is a way to enable higher zoom levels (I use OSX and Firefox)?

Another question that you might know an answer to: is there a good tutorial to work through to learn more about the issues, fixes, etc? As someone who knows a little about web development and nothing about accessibility that would be super useful for getting started. Right now reading things like a WCAG audit or guidelines is tough work because they are written for people who aren’t new to the topic. Any pointers, examples, blog posts, etc would be super useful. Right now my experience is limited to what tools like https://khan.github.io/tota11y/ show and recommend as fixes.

It will take a few days to work out a complete answer, but the attached pdf should explain the reflow criterion (1.4.10) of WCAG 2.1.

Best, Wayne

(Attachment TheReflowSuccessCriterion.pdf is missing)

The PDF attachment is missing. Is the content here similar to the missing PDF?

Oops I forgot the important thing

(Attachment Reflow.pdf is missing)

I think it gets removed by the discourse system due to security concerns.

The following link will explain the Reflow Criterion: Reflow.PDF

Best, Wayne Dick

2 Likes