From e641aa355d2c9d76aad18f81998067367613eeb7 Mon Sep 17 00:00:00 2001 From: Michail Yasonik Date: Fri, 7 Feb 2020 15:24:46 -0500 Subject: [PATCH 1/3] adding accessibility statement to docs --- docs/accessibility.asciidoc | 46 +++++++++++++++++++++++++++++++++++++ docs/index.asciidoc | 2 ++ 2 files changed, 48 insertions(+) create mode 100644 docs/accessibility.asciidoc diff --git a/docs/accessibility.asciidoc b/docs/accessibility.asciidoc new file mode 100644 index 00000000000000..2b136475a68fd5 --- /dev/null +++ b/docs/accessibility.asciidoc @@ -0,0 +1,46 @@ +[[accessibility]] += Accessibility Statement for Kibana +Elastic is committed to ensuring digital accessibility for people with disabilities. We are continually improving the user experience for everyone, and strive towards meeting relevant accessibility standards. + +== Measures to support accessibility +Elastic takes the following measures to ensure accessibility of Kibana: +Provides continual accessibility training for our staff. +Employs a 3rd-party audit. +Maintains and incorporates an accessible shared UI component library. + +== Conformance status +Initially, Kibana set out to meet https://www.w3.org/WAI/WCAG21/quickref/?currentsidebar=%23col_customize&levels=aaa&technologies=server%2Csmil%2Cflash%2Csl[WCAG 2.1 level AA] compliance. While we can only claim to be partially conforming, meaning we do not fully meet all of the success criteria, we also try to take a broader view of accessibility and go above and beyond the legal and regulatory standards to provide a good experience for all of our users. + +== Feedback +We welcome your feedback on the accessibility of Kibana. Please let us know if you encounter accessibility barriers on Kibana by either emailing us at accessibility@elastic.co or opening https://github.com/elastic/kibana/issues/new?labels=Project%3AAccessibility&template=Accessibility.md&title=%28Accessibility%29[an issue on GitHub]. + +== Technical specifications +Accessibility of Kibana 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 +* CSS +* JavaScript +* WAI-ARIA + +== Limitations and alternatives +Despite our best efforts to ensure accessibility of Kibana, there are some limitations. Below is a description of known limitations, and potential solutions. Please contact us if you observe an issue not listed below. +Broad categories of limitations for Kibana: + +* *Charts*: We are still working on figuring out an approach for making charts accessible. See our https://github.com/elastic/elastic-charts/issues/300[current progress on GitHub]. +* *Maps*: We do not know how to make them accessible yet. Would love to hear your ideas and suggestions. +* *Tables*: Though generally accessible and marked-up as standard HTML tables with column headers, tables rarely make use of row headers (even if they should have them) and have poor captions. We have a plan to improve this and you will see incremental improvements as various applications adopt the new accessible component. +* *Color contrast*: Modern Kibana interfaces generally do not have color contrast issues, however older code of Kibana may fall below the recommended contrast levels. As we continue to update our older work, this issue will phase out naturally. + +To see individual tickets, view our https://github.com/elastic/kibana/issues?q=is%3Aissue+is%3Aopen+sort%3Aupdated-desc+label%3AProject%3AAccessibility[GitHub issues label "`Project:Accessibility`"]. + +== Assessment approach +Elastic assesses the accessibility of Kibana by the following approaches: + +* *Self-evaluation*: Our employees are familiar with accessibility standards and review new designs and implemented features to confirm they are accessible. +* *External evaluation*: We engage external contractors to help us conduct an independent assessment and generate a formal VPAT. +* *Automated evaluation*: https://www.deque.com/axe/[axe] is being rolled out to run on every page. See our current progress in the https://github.com/elastic/kibana/issues/51456[automated testing GitHub issue]. + +Manual testing largely focuses on screen reader support and is done on: + +* VoiceOver on MacOS with Safari, Chrome and Edge +* NVDA on Windows with Chrome and Firefox diff --git a/docs/index.asciidoc b/docs/index.asciidoc index 491a9629e983e6..5474772ab7da81 100644 --- a/docs/index.asciidoc +++ b/docs/index.asciidoc @@ -22,6 +22,8 @@ include::{asciidoc-dir}/../../shared/attributes.asciidoc[] include::user/index.asciidoc[] +include::accessibility.asciidoc[] + include::limitations.asciidoc[] include::release-notes/highlights.asciidoc[] From 68d49d9f4697d9df209e52464e8b8bec62714737 Mon Sep 17 00:00:00 2001 From: Michail Yasonik Date: Mon, 10 Feb 2020 20:13:23 -0500 Subject: [PATCH 2/3] round of edits --- docs/accessibility.asciidoc | 52 +++++++++++++++++++++++++------------ 1 file changed, 35 insertions(+), 17 deletions(-) diff --git a/docs/accessibility.asciidoc b/docs/accessibility.asciidoc index 2b136475a68fd5..7602f40549a3b7 100644 --- a/docs/accessibility.asciidoc +++ b/docs/accessibility.asciidoc @@ -1,44 +1,62 @@ [[accessibility]] = Accessibility Statement for Kibana -Elastic is committed to ensuring digital accessibility for people with disabilities. We are continually improving the user experience for everyone, and strive towards meeting relevant accessibility standards. +++++ +Accessibility +++++ +Elastic is committed to ensuring digital accessibility for people with disabilities. We are continually improving the user experience for everyone, and strive toward meeting accessibility standards. + +[float] +[[accessibility-measures]] == Measures to support accessibility Elastic takes the following measures to ensure accessibility of Kibana: -Provides continual accessibility training for our staff. -Employs a 3rd-party audit. -Maintains and incorporates an accessible shared UI component library. +* Maintains and incorporates an https://elastic.github.io/eui/[accessible component library]. +* Provides continual accessibility training for our staff. +* Employs a third-party audit. + +[float] +[[accessibility-conformance-status]] == Conformance status -Initially, Kibana set out to meet https://www.w3.org/WAI/WCAG21/quickref/?currentsidebar=%23col_customize&levels=aaa&technologies=server%2Csmil%2Cflash%2Csl[WCAG 2.1 level AA] compliance. While we can only claim to be partially conforming, meaning we do not fully meet all of the success criteria, we also try to take a broader view of accessibility and go above and beyond the legal and regulatory standards to provide a good experience for all of our users. +Kibana aims to meet https://www.w3.org/WAI/WCAG21/quickref/?currentsidebar=%23col_customize&levels=aaa&technologies=server%2Csmil%2Cflash%2Csl[WCAG 2.1 level AA] compliance. Currently, we can only claim to partially conform, meaning we do not fully meet all of the success criteria. However, we do try to take a broader view of accessibility, and go above and beyond the legal and regulatory standards to provide a good experience for all of our users. +[float] +[[accessibility-feedback]] == Feedback We welcome your feedback on the accessibility of Kibana. Please let us know if you encounter accessibility barriers on Kibana by either emailing us at accessibility@elastic.co or opening https://github.com/elastic/kibana/issues/new?labels=Project%3AAccessibility&template=Accessibility.md&title=%28Accessibility%29[an issue on GitHub]. +[float] +[[accessibility-specs]] == Technical specifications -Accessibility of Kibana relies on the following technologies to work with the particular combination of web browser and any assistive technologies or plugins installed on your computer: +Accessibility of Kibana relies on the following technologies to work with your web browser and any assistive technologies or plugins installed on your computer: * HTML * CSS * JavaScript * WAI-ARIA +[float] +[[accessibility-limitations-and-alternatives]] == Limitations and alternatives -Despite our best efforts to ensure accessibility of Kibana, there are some limitations. Below is a description of known limitations, and potential solutions. Please contact us if you observe an issue not listed below. -Broad categories of limitations for Kibana: +Despite our best efforts to ensure accessibility of Kibana, there are some limitations. Please https://github.com/elastic/kibana/issues/new?labels=Project%3AAccessibility&template=Accessibility.md&title=%28Accessibility%29[open an issue on GitHub] if you observe an issue not in this list. + +Known limitations are in the following areas: -* *Charts*: We are still working on figuring out an approach for making charts accessible. See our https://github.com/elastic/elastic-charts/issues/300[current progress on GitHub]. -* *Maps*: We do not know how to make them accessible yet. Would love to hear your ideas and suggestions. -* *Tables*: Though generally accessible and marked-up as standard HTML tables with column headers, tables rarely make use of row headers (even if they should have them) and have poor captions. We have a plan to improve this and you will see incremental improvements as various applications adopt the new accessible component. -* *Color contrast*: Modern Kibana interfaces generally do not have color contrast issues, however older code of Kibana may fall below the recommended contrast levels. As we continue to update our older work, this issue will phase out naturally. +* *Charts*: We have a clear plan for the first steps of making charts accessible. We’ve opened this https://github.com/elastic/elastic-charts/issues/300[Charts accessibility ticket on GitHub] for tracking our progress. +* *Maps*: Maps might pose difficulties to users with vision disabilities. We welcome your input on making our maps accessible. Go to the https://github.com/elastic/kibana/issues/57271[Maps accessibility ticket on GitHub] to join the discussion and view our plans. +* *Tables*: Although generally accessible and marked-up as standard HTML tables with column headers, tables rarely make use of row headers and have poor captions. You will see incremental improvements as various applications adopt a new accessible component. +* *Color contrast*: Modern Kibana interfaces generally do not have color contrast issues. However, older code might fall below the recommended contrast levels. As we continue to update our code, this issue will phase out naturally. -To see individual tickets, view our https://github.com/elastic/kibana/issues?q=is%3Aissue+is%3Aopen+sort%3Aupdated-desc+label%3AProject%3AAccessibility[GitHub issues label "`Project:Accessibility`"]. +To see individual tickets, view our https://github.com/elastic/kibana/issues?q=is%3Aissue+is%3Aopen+sort%3Aupdated-desc+label%3AProject%3AAccessibility[GitHub issues with label "`Project:Accessibility`"]. +[float] +[[accessibility-approach]] == Assessment approach -Elastic assesses the accessibility of Kibana by the following approaches: +Elastic assesses the accessibility of Kibana with the following approaches: -* *Self-evaluation*: Our employees are familiar with accessibility standards and review new designs and implemented features to confirm they are accessible. -* *External evaluation*: We engage external contractors to help us conduct an independent assessment and generate a formal VPAT. -* *Automated evaluation*: https://www.deque.com/axe/[axe] is being rolled out to run on every page. See our current progress in the https://github.com/elastic/kibana/issues/51456[automated testing GitHub issue]. +* *Self-evaluation*: Our employees are familiar with accessibility standards and review new designs and implemented features to confirm that they are accessible. +* *External evaluation*: We engage external contractors to help us conduct an independent assessment and generate a formal VPAT. Please email accessibility@elastic.co if you’d like a copy. +* *Automated evaluation*: We are starting to run https://www.deque.com/axe/[axe] on every page. See our current progress in the https://github.com/elastic/kibana/issues/51456[automated testing GitHub issue]. Manual testing largely focuses on screen reader support and is done on: From 926bee362fde7f266a2a0101cb72a91a35159f63 Mon Sep 17 00:00:00 2001 From: Michail Yasonik Date: Tue, 11 Feb 2020 14:55:43 -0500 Subject: [PATCH 3/3] intro tweak --- docs/accessibility.asciidoc | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/docs/accessibility.asciidoc b/docs/accessibility.asciidoc index 7602f40549a3b7..4869d35dab1568 100644 --- a/docs/accessibility.asciidoc +++ b/docs/accessibility.asciidoc @@ -1,10 +1,11 @@ +[chapter] [[accessibility]] = Accessibility Statement for Kibana ++++ Accessibility ++++ -Elastic is committed to ensuring digital accessibility for people with disabilities. We are continually improving the user experience for everyone, and strive toward meeting accessibility standards. +Elastic is committed to ensuring digital accessibility for people with disabilities. We are continually improving the user experience, and strive toward ensuring our tools are usable by everyone. [float] [[accessibility-measures]]