From 7e3ac6aa6188493f64e6130bd7d646971a2ca031 Mon Sep 17 00:00:00 2001 From: isabela-pf Date: Wed, 18 May 2022 20:22:16 -0700 Subject: [PATCH 01/10] Create draft accessibility statement --- statement.md | 84 ++++++++++++++++++++++++++++++++++++++++++++++++++++ 1 file changed, 84 insertions(+) create mode 100644 statement.md diff --git a/statement.md b/statement.md new file mode 100644 index 00000000..bc1cb472 --- /dev/null +++ b/statement.md @@ -0,0 +1,84 @@ +# JupyterLab Accessibility Statement + +## Edited from the [W3C accessibility statement generator](https://www.w3.org/WAI/planning/statements/generator/#create) + + +## ⚠️ Draft Accessibility Statement for JupyterLab + +This is an accessibility statement from Jupyter accessibility contributors. + +### Measures to support accessibility + +Jupyter accessibility contributors take the following measures to ensure accessibility of JupyterLab: + +* Include accessibility as part of our mission statement. +* Provide continual accessibility training for our community. +* Assign clear accessibility goals and responsibilities. +* Employ formal accessibility quality assurance methods. + +### Conformance status + +The Web Content Accessibility Guidelines (WCAG) defines requirements for designers and developers to improve accessibility for people with disabilities. It defines three levels of conformance: Level A, Level AA, and Level AAA. JupyterLab is non conformant with WCAG 2.1 level AA. Non conformant means that the content does not conform the accessibility standard. + +### Feedback + +We welcome your feedback on the accessibility of JupyterLab. Please let us know if you encounter accessibility barriers on JupyterLab: + +* [Write an issue on jupyter/accessibility](https://github.com/jupyter/accessibility/issues/new) +* [Write an issue on jupyterlab/jupyterlab](https://github.com/jupyterlab/jupyterlab/issues/new) and request it be labeled [tag:accessibility](https://github.com/jupyterlab/jupyterlab/labels/tag%3AAccessibility) + +### Compatibility with browsers and assistive technology + +JupyterLab is designed to be compatible with the following technologies: + +* Windows, macOS, iOS, Android; Firefox, Chrome, Safari, Chromium browsers (mobile and desktop). + +JupyterLab is not compatible with: + +* Internet Explorer, Edge; JAWS, NVDA, VoiceOver, Narrator, Orca screen readers; voice control technology. + +### Technical specifications + +Accessibility of JupyterLab relies on the following technologies to work with the particular combination of web browser and any assistive technologies or plugins installed on your computer: + +* HTML +* WAI-ARIA +* CSS +* JavaScript + +These technologies are relied upon for conformance with the accessibility standards used. + +### Limitations and alternatives + +Despite our best efforts to ensure accessibility of JupyterLab, there may be some limitations. Below is a description of known limitations, and potential solutions. Please contact us if you observe an issue not listed below. + +Known limitations for JupyterLab: + +1. **Documents**: Documents writen by the community may not include accessible content because we do not and cannot review every document that can be opened in JupyterLab. To support accessible documents, we are drafting guidelines for accessible document content with an emphasis on Jupyter notebooks. Please report the issue to the author and [open an issue on jupyter/accessibility](https://github.com/jupyter/accessibility/issues/new) describing the problem and the behavior you expect so we may integrate it into our content guidelines. + +2. **JupyterLab extensions**: JupyterLab extensions writen by the community may not be accessible because JupyterLab extensions can be written by anyone in the community and have no required review process. We do not and can not review every JupyterLab extension. To support accessible extensions, we encourage extension authors to use existing, accessible JupyterLab components for their extension. We also provide periodic opportunities for community education on accessibility. Please report the issue to the author and let them know the [jupyter/accessibility](https://github.com/jupyter/accessibility/) community may be able to provide guidance. + +### Assessment approach + +Jupyter accessibility contributors assessed the accessibility of JupyterLab by the following approaches: + +* Self-evaluation +* Regular automated testing to monitor for regressions (can be found at [jupyter/accessibility](https://github.com/jupyter/accessibility) +* User feedback + +### Evaluation report + +An evaluation for JupyterLab is available at: [jupyterlab/jupyterlab/issues/9399](https://github.com/jupyterlab/jupyterlab/issues/9399). + +### Evaluation report + +User reports on JupyterLab's accessibility are available at:[the jupyterlab/jupyterlab label `tag:accessibility`](https://github.com/jupyterlab/jupyterlab/labels/tag%3AAccessibility). + +### Formal complaints + +* [Write an issue on jupyter/accessibility](https://github.com/jupyter/accessibility/issues/new) +* [Write an issue on jupyterlab/jupyterlab](https://github.com/jupyterlab/jupyterlab/labels/tag%3AAccessibility) and request it be labeled tag:accessibility. + +### Date + +This statement was created on 16 May 2022 using the [W3C Accessibility Statement Generator Tool](https://www.w3.org/WAI/planning/statements/). \ No newline at end of file From 88aac588d54b4854507b5ab8016ee5cb07213006 Mon Sep 17 00:00:00 2001 From: Isabela Presedo-Floyd <50221806+isabela-pf@users.noreply.github.com> Date: Fri, 27 May 2022 13:22:42 -0700 Subject: [PATCH 02/10] Apply suggestions from @trallard Co-authored-by: Tania Allard --- statement.md | 11 +++++------ 1 file changed, 5 insertions(+), 6 deletions(-) diff --git a/statement.md b/statement.md index bc1cb472..60c729ff 100644 --- a/statement.md +++ b/statement.md @@ -3,7 +3,7 @@ ## Edited from the [W3C accessibility statement generator](https://www.w3.org/WAI/planning/statements/generator/#create) -## ⚠️ Draft Accessibility Statement for JupyterLab +## :construction: Draft Accessibility Statement for JupyterLab This is an accessibility statement from Jupyter accessibility contributors. @@ -52,11 +52,11 @@ These technologies are relied upon for conformance with the accessibility standa Despite our best efforts to ensure accessibility of JupyterLab, there may be some limitations. Below is a description of known limitations, and potential solutions. Please contact us if you observe an issue not listed below. -Known limitations for JupyterLab: +**Known limitations for JupyterLab:** -1. **Documents**: Documents writen by the community may not include accessible content because we do not and cannot review every document that can be opened in JupyterLab. To support accessible documents, we are drafting guidelines for accessible document content with an emphasis on Jupyter notebooks. Please report the issue to the author and [open an issue on jupyter/accessibility](https://github.com/jupyter/accessibility/issues/new) describing the problem and the behavior you expect so we may integrate it into our content guidelines. +1. **Documents**: Documents written by the community may not include accessible content because we do not and cannot review every document that can be opened and edited in JupyterLab. To support accessible documents, we are drafting guidelines for accessible document content with an emphasis on Jupyter notebooks. Please report the issue to the author and [open an issue on jupyter/accessibility](https://github.com/jupyter/accessibility/issues/new) describing the problem and the behavior you expect so we may integrate it into our content guidelines. -2. **JupyterLab extensions**: JupyterLab extensions writen by the community may not be accessible because JupyterLab extensions can be written by anyone in the community and have no required review process. We do not and can not review every JupyterLab extension. To support accessible extensions, we encourage extension authors to use existing, accessible JupyterLab components for their extension. We also provide periodic opportunities for community education on accessibility. Please report the issue to the author and let them know the [jupyter/accessibility](https://github.com/jupyter/accessibility/) community may be able to provide guidance. +2. **JupyterLab extensions**: JupyterLab extensions written by the community may not be accessible because JupyterLab extensions can be written by anyone in the community and have no standard review process. We do not and can not review every JupyterLab extension. To support accessible extensions, we encourage extension authors to use existing, accessible JupyterLab components for their extensions. We also provide periodic opportunities for community education on accessibility. Please report the issue to the author and let them know the [jupyter/accessibility](https://github.com/jupyter/accessibility/) community may be able to provide guidance. ### Assessment approach @@ -64,13 +64,12 @@ Jupyter accessibility contributors assessed the accessibility of JupyterLab by t * Self-evaluation * Regular automated testing to monitor for regressions (can be found at [jupyter/accessibility](https://github.com/jupyter/accessibility) -* User feedback +* User feedback ### Evaluation report An evaluation for JupyterLab is available at: [jupyterlab/jupyterlab/issues/9399](https://github.com/jupyterlab/jupyterlab/issues/9399). -### Evaluation report User reports on JupyterLab's accessibility are available at:[the jupyterlab/jupyterlab label `tag:accessibility`](https://github.com/jupyterlab/jupyterlab/labels/tag%3AAccessibility). From 28a1a9133882a3f68c5f144a1e0944a34e4050b3 Mon Sep 17 00:00:00 2001 From: isabela-pf Date: Fri, 27 May 2022 14:05:17 -0700 Subject: [PATCH 03/10] Apply suggestions from @trallard and @gabalafou --- statement.md | 20 +++++++++++--------- 1 file changed, 11 insertions(+), 9 deletions(-) diff --git a/statement.md b/statement.md index 60c729ff..74facf10 100644 --- a/statement.md +++ b/statement.md @@ -5,7 +5,7 @@ ## :construction: Draft Accessibility Statement for JupyterLab -This is an accessibility statement from Jupyter accessibility contributors. +This is an accessibility statement from Jupyter accessibility contributors. ### Measures to support accessibility @@ -15,18 +15,25 @@ Jupyter accessibility contributors take the following measures to ensure accessi * Provide continual accessibility training for our community. * Assign clear accessibility goals and responsibilities. * Employ formal accessibility quality assurance methods. +* Document changes, approaches, and improvements to the above methods and to JupyterLab itself. ### Conformance status -The Web Content Accessibility Guidelines (WCAG) defines requirements for designers and developers to improve accessibility for people with disabilities. It defines three levels of conformance: Level A, Level AA, and Level AAA. JupyterLab is non conformant with WCAG 2.1 level AA. Non conformant means that the content does not conform the accessibility standard. +The [Web Content Accessibility Guidelines (WCAG)](https://www.w3.org/WAI/standards-guidelines/wcag) defines requirements for designers and developers to improve accessibility for people with disabilities. It defines three levels of conformance: Level A, Level AA, and Level AAA. JupyterLab is non conformant with WCAG 2.1 level AA. Non conformant means that the content does not meet the accessibility standard. -### Feedback +[Picture accessibility compliance levels as mountains. The first peak to reach is AA. This includes both A and AA criteria. Behind it, in the mist, there is a larger peak, AAA. That one is not always completely reachable--Marie Guillaumet, Access42](https://stephaniewalter.design/wp-content/uploads/2022/05/stephaniewalter-sommets-de-l-accessibilite.jpg) -We welcome your feedback on the accessibility of JupyterLab. Please let us know if you encounter accessibility barriers on JupyterLab: +*By [Stéphanie Walter](https://stephaniewalter.design) ([Source](https://stephaniewalter.design/blog/5-illustrations-to-understand-and-promote-accessibility/))* + +### Feedback and Formal complaints + +We welcome your feedback and formal complaints on the accessibility status of JupyterLab. Please let us know if you encounter accessibility barriers on JupyterLab: * [Write an issue on jupyter/accessibility](https://github.com/jupyter/accessibility/issues/new) * [Write an issue on jupyterlab/jupyterlab](https://github.com/jupyterlab/jupyterlab/issues/new) and request it be labeled [tag:accessibility](https://github.com/jupyterlab/jupyterlab/labels/tag%3AAccessibility) +At the time of writing, there is no non-public way to contact us for JupyterLab accessibility issues. + ### Compatibility with browsers and assistive technology JupyterLab is designed to be compatible with the following technologies: @@ -73,11 +80,6 @@ An evaluation for JupyterLab is available at: [jupyterlab/jupyterlab/issues/9399 User reports on JupyterLab's accessibility are available at:[the jupyterlab/jupyterlab label `tag:accessibility`](https://github.com/jupyterlab/jupyterlab/labels/tag%3AAccessibility). -### Formal complaints - -* [Write an issue on jupyter/accessibility](https://github.com/jupyter/accessibility/issues/new) -* [Write an issue on jupyterlab/jupyterlab](https://github.com/jupyterlab/jupyterlab/labels/tag%3AAccessibility) and request it be labeled tag:accessibility. - ### Date This statement was created on 16 May 2022 using the [W3C Accessibility Statement Generator Tool](https://www.w3.org/WAI/planning/statements/). \ No newline at end of file From 8be4051b32b0c7f314d34c1938f5e7fb03e88640 Mon Sep 17 00:00:00 2001 From: isabela-pf Date: Fri, 27 May 2022 14:26:26 -0700 Subject: [PATCH 04/10] Apply suggestions from @trallard and @gabalafou --- statement.md | 8 ++++++-- 1 file changed, 6 insertions(+), 2 deletions(-) diff --git a/statement.md b/statement.md index 74facf10..5a782813 100644 --- a/statement.md +++ b/statement.md @@ -17,11 +17,13 @@ Jupyter accessibility contributors take the following measures to ensure accessi * Employ formal accessibility quality assurance methods. * Document changes, approaches, and improvements to the above methods and to JupyterLab itself. +For more information on current efforts to improve JupyterLab's accessibility, visit the [JupyterLab accessibility grant roadmap](https://jupyter-a11y.netlify.app/roadmap/intro.html). + ### Conformance status The [Web Content Accessibility Guidelines (WCAG)](https://www.w3.org/WAI/standards-guidelines/wcag) defines requirements for designers and developers to improve accessibility for people with disabilities. It defines three levels of conformance: Level A, Level AA, and Level AAA. JupyterLab is non conformant with WCAG 2.1 level AA. Non conformant means that the content does not meet the accessibility standard. -[Picture accessibility compliance levels as mountains. The first peak to reach is AA. This includes both A and AA criteria. Behind it, in the mist, there is a larger peak, AAA. That one is not always completely reachable--Marie Guillaumet, Access42](https://stephaniewalter.design/wp-content/uploads/2022/05/stephaniewalter-sommets-de-l-accessibilite.jpg) +![Picture accessibility compliance levels as mountains. The first peak to reach is AA. This includes both A and AA criteria. Behind it, in the mist, there is a larger peak, AAA. That one is not always completely reachable--Marie Guillaumet, Access42](https://stephaniewalter.design/wp-content/uploads/2022/05/stephaniewalter-sommets-de-l-accessibilite.jpg) *By [Stéphanie Walter](https://stephaniewalter.design) ([Source](https://stephaniewalter.design/blog/5-illustrations-to-understand-and-promote-accessibility/))* @@ -34,6 +36,8 @@ We welcome your feedback and formal complaints on the accessibility status of Ju At the time of writing, there is no non-public way to contact us for JupyterLab accessibility issues. +Please note that JupyterLab is an open-source project and that Jupyter accessibility contributors are a group defined on a voluntary basis. Like many other open-source projects, we cannot guarantee how long it may take to respond to and resolve an issue, though we do make an effort to do it as quickly as is possible with our resources. + ### Compatibility with browsers and assistive technology JupyterLab is designed to be compatible with the following technologies: @@ -82,4 +86,4 @@ User reports on JupyterLab's accessibility are available at:[the jupyterlab/jupy ### Date -This statement was created on 16 May 2022 using the [W3C Accessibility Statement Generator Tool](https://www.w3.org/WAI/planning/statements/). \ No newline at end of file +This statement was created on 16 May 2022 using the [W3C Accessibility Statement Generator Tool](https://www.w3.org/WAI/planning/statements/) with additions and edits from the Jupyter accessibility contributors community. \ No newline at end of file From 75f2ff393365054d2340770ab044dd2c93442e76 Mon Sep 17 00:00:00 2001 From: isabela-pf Date: Fri, 27 May 2022 14:27:45 -0700 Subject: [PATCH 05/10] Move statement to docs/resources --- docs/{ => resources}/statement.md | 0 1 file changed, 0 insertions(+), 0 deletions(-) rename docs/{ => resources}/statement.md (100%) diff --git a/docs/statement.md b/docs/resources/statement.md similarity index 100% rename from docs/statement.md rename to docs/resources/statement.md From 4935fbce2280e95202c42a53610f182c3dc83518 Mon Sep 17 00:00:00 2001 From: Isabela Presedo-Floyd <50221806+isabela-pf@users.noreply.github.com> Date: Mon, 30 May 2022 10:21:08 -0700 Subject: [PATCH 06/10] Apply suggestions from @trallard Co-authored-by: Tania Allard --- statement.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/statement.md b/statement.md index 5a782813..c28411b6 100644 --- a/statement.md +++ b/statement.md @@ -3,7 +3,7 @@ ## Edited from the [W3C accessibility statement generator](https://www.w3.org/WAI/planning/statements/generator/#create) -## :construction: Draft Accessibility Statement for JupyterLab +## 🚧 Draft Accessibility Statement for JupyterLab This is an accessibility statement from Jupyter accessibility contributors. @@ -86,4 +86,4 @@ User reports on JupyterLab's accessibility are available at:[the jupyterlab/jupy ### Date -This statement was created on 16 May 2022 using the [W3C Accessibility Statement Generator Tool](https://www.w3.org/WAI/planning/statements/) with additions and edits from the Jupyter accessibility contributors community. \ No newline at end of file +This statement was created on 16 May 2022 using the [W3C Accessibility Statement Generator Tool](https://www.w3.org/WAI/planning/statements/) with additions and edits from the Jupyter accessibility contributors community. From 906e6a6ea8fcacd0af5a38ead65a3e35760a01ad Mon Sep 17 00:00:00 2001 From: isabela-pf Date: Mon, 30 May 2022 10:42:05 -0700 Subject: [PATCH 07/10] Add research and intertwined ecossytem notes --- statement.md | 3 +++ 1 file changed, 3 insertions(+) diff --git a/statement.md b/statement.md index c28411b6..80adee3b 100644 --- a/statement.md +++ b/statement.md @@ -27,12 +27,15 @@ The [Web Content Accessibility Guidelines (WCAG)](https://www.w3.org/WAI/standar *By [Stéphanie Walter](https://stephaniewalter.design) ([Source](https://stephaniewalter.design/blog/5-illustrations-to-understand-and-promote-accessibility/))* +JupyterLab's accessibility does not exist in isolation. JupyterLab inherits much from the many projects it is built upon and its accessibility conformance may impact projects built off of JupyterLab or its components. The accessibility of this ecosystem is interlinked, so conformance may need to be resolved at different levels in order to impact JupyterLab positively. + ### Feedback and Formal complaints We welcome your feedback and formal complaints on the accessibility status of JupyterLab. Please let us know if you encounter accessibility barriers on JupyterLab: * [Write an issue on jupyter/accessibility](https://github.com/jupyter/accessibility/issues/new) * [Write an issue on jupyterlab/jupyterlab](https://github.com/jupyterlab/jupyterlab/issues/new) and request it be labeled [tag:accessibility](https://github.com/jupyterlab/jupyterlab/labels/tag%3AAccessibility) +* If you are interested in being part of any potential research or organized feedback initiatives, please ___. Gauging community interest in user research participation helps us gain the support to make it happen. At the time of writing, there is no non-public way to contact us for JupyterLab accessibility issues. From a0d03550d12f459e674dab08b419d79e6dfa0459 Mon Sep 17 00:00:00 2001 From: isabela-pf Date: Thu, 2 Jun 2022 11:07:17 -0700 Subject: [PATCH 08/10] Add feedback contact and reorder based on @gabalafou's feedback --- statement.md | 58 ++++++++++++++++++++++++++-------------------------- 1 file changed, 29 insertions(+), 29 deletions(-) diff --git a/statement.md b/statement.md index 80adee3b..bc6171c6 100644 --- a/statement.md +++ b/statement.md @@ -1,23 +1,10 @@ -# JupyterLab Accessibility Statement +# 🚧 Draft Accessibility Statement for JupyterLab -## Edited from the [W3C accessibility statement generator](https://www.w3.org/WAI/planning/statements/generator/#create) - - -## 🚧 Draft Accessibility Statement for JupyterLab +Edited from the [W3C accessibility statement generator](https://www.w3.org/WAI/planning/statements/generator/#create) This is an accessibility statement from Jupyter accessibility contributors. -### Measures to support accessibility - -Jupyter accessibility contributors take the following measures to ensure accessibility of JupyterLab: - -* Include accessibility as part of our mission statement. -* Provide continual accessibility training for our community. -* Assign clear accessibility goals and responsibilities. -* Employ formal accessibility quality assurance methods. -* Document changes, approaches, and improvements to the above methods and to JupyterLab itself. - -For more information on current efforts to improve JupyterLab's accessibility, visit the [JupyterLab accessibility grant roadmap](https://jupyter-a11y.netlify.app/roadmap/intro.html). +## The current state of JupyterLab ### Conformance status @@ -29,18 +16,6 @@ The [Web Content Accessibility Guidelines (WCAG)](https://www.w3.org/WAI/standar JupyterLab's accessibility does not exist in isolation. JupyterLab inherits much from the many projects it is built upon and its accessibility conformance may impact projects built off of JupyterLab or its components. The accessibility of this ecosystem is interlinked, so conformance may need to be resolved at different levels in order to impact JupyterLab positively. -### Feedback and Formal complaints - -We welcome your feedback and formal complaints on the accessibility status of JupyterLab. Please let us know if you encounter accessibility barriers on JupyterLab: - -* [Write an issue on jupyter/accessibility](https://github.com/jupyter/accessibility/issues/new) -* [Write an issue on jupyterlab/jupyterlab](https://github.com/jupyterlab/jupyterlab/issues/new) and request it be labeled [tag:accessibility](https://github.com/jupyterlab/jupyterlab/labels/tag%3AAccessibility) -* If you are interested in being part of any potential research or organized feedback initiatives, please ___. Gauging community interest in user research participation helps us gain the support to make it happen. - -At the time of writing, there is no non-public way to contact us for JupyterLab accessibility issues. - -Please note that JupyterLab is an open-source project and that Jupyter accessibility contributors are a group defined on a voluntary basis. Like many other open-source projects, we cannot guarantee how long it may take to respond to and resolve an issue, though we do make an effort to do it as quickly as is possible with our resources. - ### Compatibility with browsers and assistive technology JupyterLab is designed to be compatible with the following technologies: @@ -84,9 +59,34 @@ Jupyter accessibility contributors assessed the accessibility of JupyterLab by t An evaluation for JupyterLab is available at: [jupyterlab/jupyterlab/issues/9399](https://github.com/jupyterlab/jupyterlab/issues/9399). - User reports on JupyterLab's accessibility are available at:[the jupyterlab/jupyterlab label `tag:accessibility`](https://github.com/jupyterlab/jupyterlab/labels/tag%3AAccessibility). +## What the community is doing + +### Measures to support accessibility + +Jupyter accessibility contributors take the following measures to ensure accessibility of JupyterLab: + +* Include accessibility as part of our mission statement. +* Provide continual accessibility training for our community. +* Assign clear accessibility goals and responsibilities. +* Employ formal accessibility quality assurance methods. +* Document changes, approaches, and improvements to the above methods and to JupyterLab itself. + +For more information on current efforts to improve JupyterLab's accessibility, visit the [JupyterLab accessibility grant roadmap](https://jupyter-a11y.netlify.app/roadmap/intro.html). + +## Feedback and Formal complaints + +We welcome your feedback and formal complaints on the accessibility status of JupyterLab. Please let us know if you encounter accessibility barriers on JupyterLab: + +* [Write an issue on jupyter/accessibility](https://github.com/jupyter/accessibility/issues/new) +* [Write an issue on jupyterlab/jupyterlab](https://github.com/jupyterlab/jupyterlab/issues/new) and request it be labeled [tag:accessibility](https://github.com/jupyterlab/jupyterlab/labels/tag%3AAccessibility) +* If you are interested in being part of any potential research or organized feedback initiatives, please [send an email with the subject line `Jupyter Accessibility Feedback` here](ipresedo@quansight.com). Gauging community interest in user research participation helps us gain the support to make it happen. + +At the time of writing, there is no non-public way to contact us for JupyterLab accessibility issues. + +Please note that JupyterLab is an open-source project and that Jupyter accessibility contributors are a group defined on a voluntary basis. Like many other open-source projects, we cannot guarantee how long it may take to respond to and resolve an issue, though we do make an effort to do it as quickly as is possible with our resources. + ### Date This statement was created on 16 May 2022 using the [W3C Accessibility Statement Generator Tool](https://www.w3.org/WAI/planning/statements/) with additions and edits from the Jupyter accessibility contributors community. From 77319f7ba73dfe53c8d670b74e7c838bbc7908a2 Mon Sep 17 00:00:00 2001 From: isabela-pf Date: Thu, 9 Jun 2022 11:45:38 -0700 Subject: [PATCH 09/10] Move statement to existing file location --- docs/resources/statement.md | 101 ++++++++++++++++++++++++++++++++++-- statement.md | 92 -------------------------------- 2 files changed, 98 insertions(+), 95 deletions(-) delete mode 100644 statement.md diff --git a/docs/resources/statement.md b/docs/resources/statement.md index eab7ee18..5b12a7b8 100644 --- a/docs/resources/statement.md +++ b/docs/resources/statement.md @@ -1,11 +1,106 @@ # `jupyter` accessibility statement -As of Jan 31, 2022, `jupyterlab` nor `retrolab` meet WCAG 2.1 Level A compliance. - ## `jupyter` audits This section includes audits from different stakeholders on `jupyter` products. * [JupyterLab v2.2.6 WCAG 2.1](https://github.com/jupyterlab/jupyterlab/issues/9399) -* [Jupyter Notebook WCAG 2.0](https://github.com/jupyter/accessibility/issues/7) \ No newline at end of file +* [Jupyter Notebook WCAG 2.0](https://github.com/jupyter/accessibility/issues/7) + +## Accessibility Statement for JupyterLab + +Edited from the [W3C accessibility statement generator](https://www.w3.org/WAI/planning/statements/generator/#create) + +This is an accessibility statement from Jupyter accessibility contributors. + +### The current state of JupyterLab + +#### Conformance status + +The [Web Content Accessibility Guidelines (WCAG)](https://www.w3.org/WAI/standards-guidelines/wcag) defines requirements for designers and developers to improve accessibility for people with disabilities. It defines three levels of conformance: Level A, Level AA, and Level AAA. JupyterLab is non conformant with WCAG 2.1 level AA. Non conformant means that the content does not meet the accessibility standard. + +![Picture accessibility compliance levels as mountains. The first peak to reach is AA. This includes both A and AA criteria. Behind it, in the mist, there is a larger peak, AAA. That one is not always completely reachable--Marie Guillaumet, Access42](https://stephaniewalter.design/wp-content/uploads/2022/05/stephaniewalter-sommets-de-l-accessibilite.jpg) + +*By [Stéphanie Walter](https://stephaniewalter.design) ([Source](https://stephaniewalter.design/blog/5-illustrations-to-understand-and-promote-accessibility/))* + +JupyterLab's accessibility does not exist in isolation. JupyterLab inherits much from the many projects it is built upon and its accessibility conformance may impact projects built off of JupyterLab or its components. The accessibility of this ecosystem is interlinked, so conformance may need to be resolved at different levels in order to impact JupyterLab positively. + +#### Compatibility with browsers and assistive technology + +JupyterLab is designed to be compatible with the following technologies: + +* Windows, macOS, iOS, Android; Firefox, Chrome, Safari, Chromium browsers (mobile and desktop). + +JupyterLab is not compatible with: + +* Internet Explorer, Edge; JAWS, NVDA, VoiceOver, Narrator, Orca screen readers; voice control technology. + +#### Technical specifications + +Accessibility of JupyterLab relies on the following technologies to work with the particular combination of web browser and any assistive technologies or plugins installed on your computer: + +* HTML +* WAI-ARIA +* CSS +* JavaScript + +These technologies are relied upon for conformance with the accessibility standards used. + +#### Limitations and alternatives + +Despite our best efforts to ensure accessibility of JupyterLab, there may be some limitations. Below is a description of known limitations, and potential solutions. Please contact us if you observe an issue not listed below. + +**Known limitations for JupyterLab:** + +1. **Documents**: Documents written by the community may not include accessible content because we do not and cannot review every document that can be opened and edited in JupyterLab. To support accessible documents, we are drafting guidelines for accessible document content with an emphasis on Jupyter notebooks. Please report the issue to the author and [open an issue on jupyter/accessibility](https://github.com/jupyter/accessibility/issues/new) describing the problem and the behavior you expect so we may integrate it into our content guidelines. + +2. **JupyterLab extensions**: JupyterLab extensions written by the community may not be accessible because JupyterLab extensions can be written by anyone in the community and have no standard review process. We do not and can not review every JupyterLab extension. To support accessible extensions, we encourage extension authors to use existing, accessible JupyterLab components for their extensions. We also provide periodic opportunities for community education on accessibility. Please report the issue to the author and let them know the [jupyter/accessibility](https://github.com/jupyter/accessibility/) community may be able to provide guidance. + +#### Assessment approach + +Jupyter accessibility contributors assessed the accessibility of JupyterLab by the following approaches: + +* Self-evaluation +* Regular automated testing to monitor for regressions (can be found at [jupyter/accessibility](https://github.com/jupyter/accessibility) +* User feedback + +#### Evaluation report + +An evaluation for JupyterLab is available at: [jupyterlab/jupyterlab/issues/9399](https://github.com/jupyterlab/jupyterlab/issues/9399). + +User reports on JupyterLab's accessibility are available at:[the jupyterlab/jupyterlab label `tag:accessibility`](https://github.com/jupyterlab/jupyterlab/labels/tag%3AAccessibility). + +### What the community is doing + +#### Measures to support accessibility + +Jupyter accessibility contributors take the following measures to ensure accessibility of JupyterLab: + +* Include accessibility as part of our mission statement. +* Provide continual accessibility training for our community. +* Assign clear accessibility goals and responsibilities. +* Employ formal accessibility quality assurance methods. +* Document changes, approaches, and improvements to the above methods and to JupyterLab itself. + +For more information on current efforts to improve JupyterLab's accessibility, visit the [JupyterLab accessibility grant roadmap](https://jupyter-a11y.netlify.app/roadmap/intro.html). + +### Feedback and Formal complaints + +We welcome your feedback and formal complaints on the accessibility status of JupyterLab. Please let us know if you encounter accessibility barriers on JupyterLab: + +* [Write an issue on jupyter/accessibility](https://github.com/jupyter/accessibility/issues/new) +* [Write an issue on jupyterlab/jupyterlab](https://github.com/jupyterlab/jupyterlab/issues/new) and request it be labeled [tag:accessibility](https://github.com/jupyterlab/jupyterlab/labels/tag%3AAccessibility) +* If you are interested in being part of any potential research or organized feedback initiatives, please [send an email with the subject line `Jupyter Accessibility Feedback` here](ipresedo@quansight.com). Gauging community interest in user research participation helps us gain the support to make it happen. + +At the time of writing, there is no non-public way to contact us for JupyterLab accessibility issues. + +Please note that JupyterLab is an open-source project and that Jupyter accessibility contributors are a group defined on a voluntary basis. Like many other open-source projects, we cannot guarantee how long it may take to respond to and resolve an issue, though we do make an effort to do it as quickly as is possible with our resources. + +### Date + +This statement was created on 16 May 2022 using the [W3C Accessibility Statement Generator Tool](https://www.w3.org/WAI/planning/statements/) with additions and edits from the Jupyter accessibility contributors community. + +## Accessibility Statement for Jupyter Notebook + +Pending \ No newline at end of file diff --git a/statement.md b/statement.md deleted file mode 100644 index bc6171c6..00000000 --- a/statement.md +++ /dev/null @@ -1,92 +0,0 @@ -# 🚧 Draft Accessibility Statement for JupyterLab - -Edited from the [W3C accessibility statement generator](https://www.w3.org/WAI/planning/statements/generator/#create) - -This is an accessibility statement from Jupyter accessibility contributors. - -## The current state of JupyterLab - -### Conformance status - -The [Web Content Accessibility Guidelines (WCAG)](https://www.w3.org/WAI/standards-guidelines/wcag) defines requirements for designers and developers to improve accessibility for people with disabilities. It defines three levels of conformance: Level A, Level AA, and Level AAA. JupyterLab is non conformant with WCAG 2.1 level AA. Non conformant means that the content does not meet the accessibility standard. - -![Picture accessibility compliance levels as mountains. The first peak to reach is AA. This includes both A and AA criteria. Behind it, in the mist, there is a larger peak, AAA. That one is not always completely reachable--Marie Guillaumet, Access42](https://stephaniewalter.design/wp-content/uploads/2022/05/stephaniewalter-sommets-de-l-accessibilite.jpg) - -*By [Stéphanie Walter](https://stephaniewalter.design) ([Source](https://stephaniewalter.design/blog/5-illustrations-to-understand-and-promote-accessibility/))* - -JupyterLab's accessibility does not exist in isolation. JupyterLab inherits much from the many projects it is built upon and its accessibility conformance may impact projects built off of JupyterLab or its components. The accessibility of this ecosystem is interlinked, so conformance may need to be resolved at different levels in order to impact JupyterLab positively. - -### Compatibility with browsers and assistive technology - -JupyterLab is designed to be compatible with the following technologies: - -* Windows, macOS, iOS, Android; Firefox, Chrome, Safari, Chromium browsers (mobile and desktop). - -JupyterLab is not compatible with: - -* Internet Explorer, Edge; JAWS, NVDA, VoiceOver, Narrator, Orca screen readers; voice control technology. - -### Technical specifications - -Accessibility of JupyterLab relies on the following technologies to work with the particular combination of web browser and any assistive technologies or plugins installed on your computer: - -* HTML -* WAI-ARIA -* CSS -* JavaScript - -These technologies are relied upon for conformance with the accessibility standards used. - -### Limitations and alternatives - -Despite our best efforts to ensure accessibility of JupyterLab, there may be some limitations. Below is a description of known limitations, and potential solutions. Please contact us if you observe an issue not listed below. - -**Known limitations for JupyterLab:** - -1. **Documents**: Documents written by the community may not include accessible content because we do not and cannot review every document that can be opened and edited in JupyterLab. To support accessible documents, we are drafting guidelines for accessible document content with an emphasis on Jupyter notebooks. Please report the issue to the author and [open an issue on jupyter/accessibility](https://github.com/jupyter/accessibility/issues/new) describing the problem and the behavior you expect so we may integrate it into our content guidelines. - -2. **JupyterLab extensions**: JupyterLab extensions written by the community may not be accessible because JupyterLab extensions can be written by anyone in the community and have no standard review process. We do not and can not review every JupyterLab extension. To support accessible extensions, we encourage extension authors to use existing, accessible JupyterLab components for their extensions. We also provide periodic opportunities for community education on accessibility. Please report the issue to the author and let them know the [jupyter/accessibility](https://github.com/jupyter/accessibility/) community may be able to provide guidance. - -### Assessment approach - -Jupyter accessibility contributors assessed the accessibility of JupyterLab by the following approaches: - -* Self-evaluation -* Regular automated testing to monitor for regressions (can be found at [jupyter/accessibility](https://github.com/jupyter/accessibility) -* User feedback - -### Evaluation report - -An evaluation for JupyterLab is available at: [jupyterlab/jupyterlab/issues/9399](https://github.com/jupyterlab/jupyterlab/issues/9399). - -User reports on JupyterLab's accessibility are available at:[the jupyterlab/jupyterlab label `tag:accessibility`](https://github.com/jupyterlab/jupyterlab/labels/tag%3AAccessibility). - -## What the community is doing - -### Measures to support accessibility - -Jupyter accessibility contributors take the following measures to ensure accessibility of JupyterLab: - -* Include accessibility as part of our mission statement. -* Provide continual accessibility training for our community. -* Assign clear accessibility goals and responsibilities. -* Employ formal accessibility quality assurance methods. -* Document changes, approaches, and improvements to the above methods and to JupyterLab itself. - -For more information on current efforts to improve JupyterLab's accessibility, visit the [JupyterLab accessibility grant roadmap](https://jupyter-a11y.netlify.app/roadmap/intro.html). - -## Feedback and Formal complaints - -We welcome your feedback and formal complaints on the accessibility status of JupyterLab. Please let us know if you encounter accessibility barriers on JupyterLab: - -* [Write an issue on jupyter/accessibility](https://github.com/jupyter/accessibility/issues/new) -* [Write an issue on jupyterlab/jupyterlab](https://github.com/jupyterlab/jupyterlab/issues/new) and request it be labeled [tag:accessibility](https://github.com/jupyterlab/jupyterlab/labels/tag%3AAccessibility) -* If you are interested in being part of any potential research or organized feedback initiatives, please [send an email with the subject line `Jupyter Accessibility Feedback` here](ipresedo@quansight.com). Gauging community interest in user research participation helps us gain the support to make it happen. - -At the time of writing, there is no non-public way to contact us for JupyterLab accessibility issues. - -Please note that JupyterLab is an open-source project and that Jupyter accessibility contributors are a group defined on a voluntary basis. Like many other open-source projects, we cannot guarantee how long it may take to respond to and resolve an issue, though we do make an effort to do it as quickly as is possible with our resources. - -### Date - -This statement was created on 16 May 2022 using the [W3C Accessibility Statement Generator Tool](https://www.w3.org/WAI/planning/statements/) with additions and edits from the Jupyter accessibility contributors community. From 33cde064dd84814c0e6a3e4941e9dcf251922fe7 Mon Sep 17 00:00:00 2001 From: isabela-pf Date: Thu, 16 Jun 2022 12:22:48 -0700 Subject: [PATCH 10/10] Update document based on meeting feedback --- docs/resources/statement.md | 43 ++++++++++++++++++++++++++++++------- 1 file changed, 35 insertions(+), 8 deletions(-) diff --git a/docs/resources/statement.md b/docs/resources/statement.md index 5b12a7b8..0f502938 100644 --- a/docs/resources/statement.md +++ b/docs/resources/statement.md @@ -1,4 +1,4 @@ -# `jupyter` accessibility statement +# `jupyter` accessibility statements ## `jupyter` audits @@ -16,6 +16,10 @@ This is an accessibility statement from Jupyter accessibility contributors. ### The current state of JupyterLab +Jupyter accessibility statements are living documents. This statement was created on 16 May 2022 using the [W3C Accessibility Statement Generator Tool](https://www.w3.org/WAI/planning/statements/) with additions and edits from the Jupyter accessibility contributors community. + +This statement was last updated 16 June 2022. + #### Conformance status The [Web Content Accessibility Guidelines (WCAG)](https://www.w3.org/WAI/standards-guidelines/wcag) defines requirements for designers and developers to improve accessibility for people with disabilities. It defines three levels of conformance: Level A, Level AA, and Level AAA. JupyterLab is non conformant with WCAG 2.1 level AA. Non conformant means that the content does not meet the accessibility standard. @@ -28,13 +32,40 @@ JupyterLab's accessibility does not exist in isolation. JupyterLab inherits much #### Compatibility with browsers and assistive technology -JupyterLab is designed to be compatible with the following technologies: +JupyterLab is designed to be compatible with the following + +Operating systems: -* Windows, macOS, iOS, Android; Firefox, Chrome, Safari, Chromium browsers (mobile and desktop). +* Windows +* macOS +* Linux +* iOS +* Android + +Browsers (mobile and desktop): + + * Firefox + * Chrome + * Safari + * Chromium browsers JupyterLab is not compatible with: -* Internet Explorer, Edge; JAWS, NVDA, VoiceOver, Narrator, Orca screen readers; voice control technology. +Operating systems: + +Browsers (mobile and desktop): + +* Internet Explorer +* Edge + +Assistive technology: + +* JAWS +* NVDA +* VoiceOver +* Narrator +* Orca screen readers +* voice control technology #### Technical specifications @@ -97,10 +128,6 @@ At the time of writing, there is no non-public way to contact us for JupyterLab Please note that JupyterLab is an open-source project and that Jupyter accessibility contributors are a group defined on a voluntary basis. Like many other open-source projects, we cannot guarantee how long it may take to respond to and resolve an issue, though we do make an effort to do it as quickly as is possible with our resources. -### Date - -This statement was created on 16 May 2022 using the [W3C Accessibility Statement Generator Tool](https://www.w3.org/WAI/planning/statements/) with additions and edits from the Jupyter accessibility contributors community. - ## Accessibility Statement for Jupyter Notebook Pending \ No newline at end of file