deploy: 27ee383

_sources/workflow/accessibility.md

@@ -1,6 +1,6 @@
 # Creating Accessible Notebook Experience
 
-Improving the accessibility of the notebook experience has consistently been a key priority for the Datahub infrastructure team. This focus stems from the fact that notebooks have presented significant accessibility challenges, including limited compatibility with screen readers and keyboard navigation, difficulties in interpreting content due to color contrast issues, and non-compliance with the [WCAG 2.0 AA](https://www.ucop.edu/electronic-accessibility/standards-and-best-practices/levels-of-conformance-a-aa-aaa.html) standards mandated by the University.
+Improving the accessibility of the notebook experience has consistently been a key priority for the Datahub infrastructure team. This focus stems from the fact that notebooks have presented significant accessibility challenges, including limited compatibility with screen readers and keyboard navigation, difficulties in interpreting content due to color contrast issues, and non-compliance with the [WCAG 2.0 AA standards](https://www.ucop.edu/electronic-accessibility/standards-and-best-practices/levels-of-conformance-a-aa-aaa.html) mandated by the University.
 
 Enhancing the accessibility of the notebook experience involves addressing multiple dimensions:
 
@@ -9,7 +9,7 @@ Enhancing the accessibility of the notebook experience involves addressing multi
 
 ## Enhancing the accessibility of the notebook interface:
 
-The Datahub team constantly collaborates with Jupyter developers to incorporate accessibility enhancements into both the Notebook and Lab interfaces. In that spirit, We encourage instructors to integrate Lab 4 and Notebook 7 into their teaching workflows, as these releases include the latest accessibility enhancements. 
+The Datahub team constantly collaborates with Jupyter developers to incorporate accessibility enhancements into both the Notebook and Lab interfaces. In that spirit,we encourage instructors to integrate Lab 4 and Notebook 7 into their teaching workflows, as these releases include the latest accessibility enhancements.
 
 ### JupyterLab 4.0: 
 
@@ -30,7 +30,7 @@ Sharing couple of resources from the [Iota School](https://github.com/Iota-Schoo
 
 #### Export notebook to html format:
 
-The editable notebook format (.ipynb) is inaccessible for screen readers and keyboard navigation. Lot of effort has been made to Lab 4 and Notbook 7 to overcome some of the barriers to accessibility. However, it is still not 100% accessible at the moment. To improve the readability of the notebooks, It is recommended that .ipynb files are converted to .html files which are largely designed for webinterface and has a more accessible experience. PDFs are generally inaccessible in comparison to html format from a readability standpoint.
+The editable notebook format (.ipynb) is inaccessible for screen readers and keyboard navigation. Much effort has been made to Lab 4 and Notbook 7 to overcome some of the barriers to accessibility. However, it is still not 100% accessible at the moment. To improve the readability of the notebooks, It is recommended that .ipynb files are converted to .html files which are largely designed for web interface and has a more accessible experience. PDFs are generally inaccessible in comparison to html format from a readability standpoint.
 
 [Nbconvert](https://github.com/jupyter/nbconvert) is a  tool that converts notebooks to various formats including html which improves readability. The command for converting notebooks from .ipynb to html is
 

workflow/accessibility.html

@@ -401,15 +401,15 @@ <h2> Contents </h2>
 
   <section class="tex2jax_ignore mathjax_ignore" id="creating-accessible-notebook-experience">
 <h1>Creating Accessible Notebook Experience<a class="headerlink" href="#creating-accessible-notebook-experience" title="Permalink to this heading">#</a></h1>
-<p>Improving the accessibility of the notebook experience has consistently been a key priority for the Datahub infrastructure team. This focus stems from the fact that notebooks have presented significant accessibility challenges, including limited compatibility with screen readers and keyboard navigation, difficulties in interpreting content due to color contrast issues, and non-compliance with the <a class="reference external" href="https://www.ucop.edu/electronic-accessibility/standards-and-best-practices/levels-of-conformance-a-aa-aaa.html">WCAG 2.0 AA</a> standards mandated by the University.</p>
+<p>Improving the accessibility of the notebook experience has consistently been a key priority for the Datahub infrastructure team. This focus stems from the fact that notebooks have presented significant accessibility challenges, including limited compatibility with screen readers and keyboard navigation, difficulties in interpreting content due to color contrast issues, and non-compliance with the <a class="reference external" href="https://www.ucop.edu/electronic-accessibility/standards-and-best-practices/levels-of-conformance-a-aa-aaa.html">WCAG 2.0 AA standards</a> mandated by the University.</p>
 <p>Enhancing the accessibility of the notebook experience involves addressing multiple dimensions:</p>
 <ul class="simple">
 <li><p>Ensuring the accessibility of the interface, as exemplified by Lab 4 and Notebook 7.</p></li>
 <li><p>Enhancing the accessibility of the content within notebooks.</p></li>
 </ul>
 <section id="enhancing-the-accessibility-of-the-notebook-interface">
 <h2>Enhancing the accessibility of the notebook interface:<a class="headerlink" href="#enhancing-the-accessibility-of-the-notebook-interface" title="Permalink to this heading">#</a></h2>
-<p>The Datahub team constantly collaborates with Jupyter developers to incorporate accessibility enhancements into both the Notebook and Lab interfaces. In that spirit, We encourage instructors to integrate Lab 4 and Notebook 7 into their teaching workflows, as these releases include the latest accessibility enhancements.</p>
+<p>The Datahub team constantly collaborates with Jupyter developers to incorporate accessibility enhancements into both the Notebook and Lab interfaces. In that spirit,we encourage instructors to integrate Lab 4 and Notebook 7 into their teaching workflows, as these releases include the latest accessibility enhancements.</p>
 <section id="jupyterlab-4-0">
 <h3>JupyterLab 4.0:<a class="headerlink" href="#jupyterlab-4-0" title="Permalink to this heading">#</a></h3>
 <p>A number of accessibility improvements have been made in JupyterLab 4.0, including improved screen reader and keyboard navigation, more ARIA roles and labels, and a hamburger menu that collapses if there is not enough space to display all items. You can read more about the features of Lab 4 in the blogpost titled <a class="reference external" href="https://blog.jupyter.org/jupyterlab-4-0-is-here-388d05e03442">“JupyterLab 4.0 is here”</a>. Lab 4 has undergone extensive testing with Data 100 summer 23 instructors within a new hub, and the overall experience has been positive, with the exception of real-time collaboration, which may require further attention.</p>
@@ -429,7 +429,7 @@ <h2>Enhancing the accessibility of the content within Jupyter notebooks:<a class
 </ul>
 <section id="export-notebook-to-html-format">
 <h3>Export notebook to html format:<a class="headerlink" href="#export-notebook-to-html-format" title="Permalink to this heading">#</a></h3>
-<p>The editable notebook format (.ipynb) is inaccessible for screen readers and keyboard navigation. Lot of effort has been made to Lab 4 and Notbook 7 to overcome some of the barriers to accessibility. However, it is still not 100% accessible at the moment. To improve the readability of the notebooks, It is recommended that .ipynb files are converted to .html files which are largely designed for webinterface and has a more accessible experience. PDFs are generally inaccessible in comparison to html format from a readability standpoint.</p>
+<p>The editable notebook format (.ipynb) is inaccessible for screen readers and keyboard navigation. Much effort has been made to Lab 4 and Notbook 7 to overcome some of the barriers to accessibility. However, it is still not 100% accessible at the moment. To improve the readability of the notebooks, It is recommended that .ipynb files are converted to .html files which are largely designed for web interface and has a more accessible experience. PDFs are generally inaccessible in comparison to html format from a readability standpoint.</p>
 <p><a class="reference external" href="https://github.com/jupyter/nbconvert">Nbconvert</a> is a  tool that converts notebooks to various formats including html which improves readability. The command for converting notebooks from .ipynb to html is</p>
 <p><code class="docutils literal notranslate"><span class="pre">$</span> <span class="pre">jupyter</span> <span class="pre">nbconvert</span> <span class="pre">--to</span> <span class="pre">html</span> <span class="pre">mynotebook.ipynb</span></code></p>
 <p>One can also customize the themes, font types, sizes etc. as part of the notebook inorder to improve the accessibility.</p>