Improve Kibana Accessibility

[cjcenizal]

Phase 1: Initial review and issues

Immediate issues to resolve

Per functional area

• Discovery
  • Phase 1, 6.0: [Accessibility] Discovery short-term issues #12203
  • Phase 2, 6.1: [Accessibility] Discovery Phase 2 issues #13554
• Visualizations
  • Phase 1, 6.0: [Accessibility] Visualizations short-term issues #12204
  • Phase 2, 6.1: [Accessibility] Visualizations Phase 2 issues #13560
• Sharing
  • Phase 1, 6.0: [Accessibility] Sharing short-term issues #12205
• Dev Tools
  • Phase 2, 6.1: [Accessibility] Dev Tools Phase 2 issues #12206
• Management
  • Phase 1, 6.0: [Accessibility] Management short-term issues  #12207
  • Phase 2, 6.1: [Accessibility] Management Phase 2 issues #13556
• Design
  • Phase 1, 6.0: [Accessibility] Design short-term issues  #12208
  • Phase 2, 6.1: [Accessibility] Design Phase 2 issues #13555

Global issues

These are general issues we need to address throughout Kibana.

• Remove unnecessary ARIA Accessibility: Remove unnecessary ARIA #11838
• Create ARIA landmarks Accessibility: Create ARIA landmarks #11839
• Alternative text Accessibility: Alternative text #11520
• Interactive elements Accessibility: Interactive elements #11513
• Headings Accessibility: Headings #11519
• Input states Accessibility: Input states #11523
• Keyboard focus Accessibility: Keyboard focus #11517
• Autofocused elements Accessibility: Autofocused elements #11515
• Expand/collapsed icons Accessibility: Expand/collapsed icons #11514
• Skip links Accessibility: Skip links #11516
• Associate form fields with labels Accessibility: Associate form fields with labels #11837
• Tabs Accessibility: Tabs #11841
• Make tables accessible [Accessibility] Make tables accessible #12401

Phase 2: X-Pack review and longer term issues

• X-Pack accessibility in Improve X-Pack Accessibility #18498
• ML [ML] Improve ML Accessibility #18278

Long-term issues

We can get to these once we have an acceptable baseline accessible experience.

Global issues

• Make all UI Framework components accessible, [Accessibility] Improve accessibility in UI framework #14080, Improve Elastic UI Accessibility eui#614
• Use proper page titles in all apps Accessibility: Page titles #11518

Visualizations

• Make charts screen-reader-accessible Accessibility: Make charts screen-reader-accessible #11842
• Discussion: What to do with update / clear visualization buttons [Accessibility] Discussion: What to do with update / clear visualization buttons #12893

Testing / QA

• Add automated accessibility testing Add automated accessibility testing #13758
• Add eslint rules for accessibility Add eslint rules for accessibility #13835

Phase 3: Additional version review

• 6.3 Accessibility: Kibana 6.3 Meta Issue #18866

[nrichers]

A couple of related items I don't see on the list:

1. Product documentation: I just did a search on the spatial references “above,” “below”, “left,” and “right” in the Kibana docs and there are ~45 hits, many of which refer to the spatial placement of UI controls. That's a pretty standard accessibility gotcha, along with tables that have no header to explain what each column means. There are very likely other low-hanging fruit accessibility gotchas in the Kibana docs as well.

2. Error messages: Sooner or later, you will fall off the happy path and you're going to get either a transient or a full error message. Globally, our error messages often stand to be improved (a big handwaving claim if there ever was one--I can supply examples). There are some considerations around making error messages accessible, such as:

• Clearly identifying the UI control that is causing the error in the text (and, again, not having things like spatial references in the messages themselves, for example)
• Indicating how to resolve the error (an area our error messages often don't cover, differently abled user or not)
• Testing to make sure error messages work in the screen reader

(If all of this has been covered, just ignore my comment. 😄 During CJ's intro, it seemed at least the doc stuff had not been considered, yet.)

[SeanFarrow]

I'd be interested in helping with this, as given we're looking to use this and as someone who has no sight it is essential that it is accessible. ARe there any issues that need immediate attention/what form of tests are you looking ot add?
Leave a comment

[timroes]

@SeanFarrow thanks for leaving a comment here. We are currently still in an early phase and doing the best to make the user interface accessible and prioritize our work. In the long term, we would at least like to add automated testing (see issue #13758) to catch some of the basic accessibility issues.

Since you said, that you are evaluating the usage of Kibana at the moment and you are a visually impaired user, we would appreciate it a lot, if you would find the time, to have a short chat with us. We could tell you more about our current state and plans and you could tell us about your use-case, your expectations and wishes, to help us prioritizing our current efforts. If you would be open to having a chat, could you contact us at accessibility@elastic.co so we could arrange an online meeting (with the tool of your choice: Skype, Hangouts, or we can create a meeting using the video conference tool Zoom).

[myasonik]

Closing this meta ticket as it's no longer being actively tracked (though the individual issues that are still open are!).

Promoted @nrichers's comment to its own issue for better visibility: #55566