Add new accessibility-specific documentation

[steff456]

Motivation

This issue will be used to track the documentation writing work about accessibility resources that are scattered over multiple repositories. I know there’s a lot of material that we want to include that goes beyond this list, but I want to start moving the ball of accessibility-specific documentation on the Jupyter project.

Current status

Right now, the structure of the JupyterLab Accessibility documentation looks like this:

• Home
  • Jupyter accessibility
  • Accessibility docs page
• Accessibility efforts
  • Jupyter Accessibility Statement
• Community
  • Contribute to Jupyter Accessibility
  • Community calls and events
• Accessibility resources
  • Useful Jupyter accessibility resources
  • Mapping JupyterLab’s user interface to source code
• Funded accessibility work
  • Funding accessibility efforts
  • CZI EOSS cycle 4
    CZI EOSS cycle 4 - Completed items

New documentation

• Notebook authoring guide - as a new page under accessibility resources - WIP - Add Notebook Authoring Guide #127
• Audits - as a new section that will include the audits for 400% zoom and keyboard navigation - Add audits in the Jupyter ecosystem #133
  • 400% zoom audit: Type up requirements issue for Zoom fixes Quansight-Labs/jupyterlab-accessible-themes#34
  • JupyterLab audit: Accessibility Issues Needing Addressing for WCAG 2.1 compliance (As of Version 2.2.6) jupyterlab/jupyterlab#9399
  • Notebook 7 keyboard navigation review: Notebook 7 prerelease keyboard navigation review notebook#6595
  • Older review describing screen reader compatibility in JupyterLab. Screen reader with keyboard shortcuts jupyterlab/jupyterlab#6573
  • Notebook 7 audit: Accessibility Issues Needing Addressing for WCAG 2.1 compliance (As of Version 7.0.0a15) notebook#6800
• WCAG intro and links to resources - as a revamp of the existing page https://jupyter-accessibility.readthedocs.io/en/latest/resources/useful-resources.html - Add WCAG and ARIA intro #126

[isabela-pf]

Because it has come up as a request and is something we've built some resources about, I'd like to propose adding

• Tips on how to review PRs for accessibility considerations

to our list of new accessibility-specific documentation. I don't think it will be comprehensive, but it can consolidate work that already exists like alt text review tips, keyboard navigation tips, things I know I've commented on PRs when tagged, and some scoped high-stakes WCAG recommendations (ie. the threshold for flashing lights).

Since I'm suggesting this, I'll assign this part to me! I'd also be happy to work on the notebook authoring recommendations and WCAG intro contents, though they'd benefit from the input of others.