Skip to content

Commit e641aa3

Browse files
author
Michail Yasonik
committed
adding accessibility statement to docs
1 parent a98ad7a commit e641aa3

File tree

2 files changed

+48
-0
lines changed

2 files changed

+48
-0
lines changed

docs/accessibility.asciidoc

Lines changed: 46 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,46 @@
1+
[[accessibility]]
2+
= Accessibility Statement for Kibana
3+
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.
4+
5+
== Measures to support accessibility
6+
Elastic takes the following measures to ensure accessibility of Kibana:
7+
Provides continual accessibility training for our staff.
8+
Employs a 3rd-party audit.
9+
Maintains and incorporates an accessible shared UI component library.
10+
11+
== Conformance status
12+
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.
13+
14+
== Feedback
15+
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].
16+
17+
== Technical specifications
18+
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:
19+
20+
* HTML
21+
* CSS
22+
* JavaScript
23+
* WAI-ARIA
24+
25+
== Limitations and alternatives
26+
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.
27+
Broad categories of limitations for Kibana:
28+
29+
* *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].
30+
* *Maps*: We do not know how to make them accessible yet. Would love to hear your ideas and suggestions.
31+
* *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.
32+
* *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.
33+
34+
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`"].
35+
36+
== Assessment approach
37+
Elastic assesses the accessibility of Kibana by the following approaches:
38+
39+
* *Self-evaluation*: Our employees are familiar with accessibility standards and review new designs and implemented features to confirm they are accessible.
40+
* *External evaluation*: We engage external contractors to help us conduct an independent assessment and generate a formal VPAT.
41+
* *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].
42+
43+
Manual testing largely focuses on screen reader support and is done on:
44+
45+
* VoiceOver on MacOS with Safari, Chrome and Edge
46+
* NVDA on Windows with Chrome and Firefox

docs/index.asciidoc

Lines changed: 2 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -22,6 +22,8 @@ include::{asciidoc-dir}/../../shared/attributes.asciidoc[]
2222

2323
include::user/index.asciidoc[]
2424

25+
include::accessibility.asciidoc[]
26+
2527
include::limitations.asciidoc[]
2628

2729
include::release-notes/highlights.asciidoc[]

0 commit comments

Comments
 (0)