exporting notebooks with modifications from the python library

[tonyfast]

@Jenneh @isabela-pf i've set up the stages of publishing notebooks using the tooling we have been building.

there is now a github pages for this project @ https://iota-school.github.io/notebooks-for-all/ on this page, there is a list of content that we can modify to your liking. at the moment, we are comparing the baseline jupyterlab rendering to our accessible version of it. and, we already have good news!

improvements to readability mode

if y'all are using firefox then you'll get that little readability button in the url status bar. that shows up by a cursory measure of the content in the page. one of the things that it explicitly looks for are the main, article, section tags.

it turns out our changes activate readability mode. this is a nice outcome because the readability could provide a modern accessible alternative. the images below show the status bars for the baseline and accessible exports, respectively.

you'll notice the option for readability mode avaiable for our current progress. yay.

good seeing y'all today. :zzz: :cookie:

[tonyfast]

i've included that automatically exports the axe results for each of the views. i haven't elevated this on the webpage yet, but the results can be found in the data folder https://github.com/Iota-School/notebooks-for-all/tree/gh-pages/data

[tonyfast]

i've updated this pull request to include the new notebook content in #32 from the html source @eteq provided i was able to apply remediations directly to the html content. this version contains eric's notebook content with main, article, section, aside applied to various elements.

[tonyfast]

i can't merge this work us we close #32

[tonyfast]

To dos short term (in next month)

• Surface more metadata from notebook

• Add labels to cells

  • Label Markdown cell
  • Label Code cell
  • Label Error (or maybe display or error for this one)
    • Also add an error icon or word at the beginning of the message

• Make new workflow discoverable

  • Cells registered to tab navigation
  • Tell people how to navigate by regions / labels if in unexpected way
    • Potentially have a notebook that teaches you how to use its self
    • Tell people to look for regions bc they aren’t expecting to use them

• Async AB design testing with Beth

• Improve color contrast on in[] & out[]

  • Other potential styling improvements, full opacity, font, size, etc? (Isabela and Jenn can help)

• Tighter right margins so fewer characters of text per line

  • Add margins when media query is larger than an (ipad) so they are invoked when the screen is wider than a certain width

• Patrick writeup of how he would want landmark navigation to work in perfect world

 

To dos long term (after new year)

• Run Workshop with screen reader users to decide desired screen reader behavior
• Can we do larger scale async testing With Abhisar People Patrick knows * CS Email lists
• Write blog posts outlining the plotting library output alt text complex issue