Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

(Accessibility) Dashboard Keyboard Navigation #39437

Closed
barlowm opened this issue Jun 21, 2019 · 4 comments
Closed

(Accessibility) Dashboard Keyboard Navigation #39437

barlowm opened this issue Jun 21, 2019 · 4 comments
Labels
Feature:Dashboard Dashboard related features Project:Accessibility Team:Visualizations Visualization editors, elastic-charts and infrastructure WCAG A

Comments

@barlowm
Copy link
Collaborator

barlowm commented Jun 21, 2019

Steps to reproduce

Navigate to a new dashboard and using the keyboard navigate to the "Add Filter" link and press enter.
The "Edit Filter" dialog appears
Using the keyboard only perform the following steps:

  • Press the TAB key to navigate to the "Field" field and fill out,
  • Press the TAB key to navigate to the "Operator" field and fill out
  • Press the TAB key to navigate to the next field (which should be the "Values" field) the focus goes to the ** "Edit as Query DSL" ** link.

Expected Result

Navigation should go in proper sequence (left to right, top to bottom). (see attached)

Meta Issue:

Accessibility Audit for Kibana 7.0
Make Uptime App Accessible for 7.0

Kibana Version:

7.0

Relevant WCAG Criteria:

WCAG Criterion

https://www.w3.org/WAI/WCAG21/quickref/?versions=2.0#focus-order

@myasonik myasonik added the Team:Visualizations Visualization editors, elastic-charts and infrastructure label Feb 10, 2020
@elasticmachine
Copy link
Contributor

Pinging @elastic/kibana-app (Team:KibanaApp)

@majagrubic
Copy link
Contributor

I believe this has been fixed with the recent rewrite of the search bar component. The behavior looks correct to me:
dashboard_filtering

Can you confirm @myasonik so we can close this issue?

@jgough
Copy link

jgough commented Oct 2, 2020

I would personally argue that the tabindex of the dropdown arrow V is superfluous to functionality and tabbing should skip over this - as happens in Kibana 6.

@myasonik
Copy link
Contributor

myasonik commented Oct 2, 2020

@jgough You're totally right!

That issue is tracked as part of a larger effort of a11y improvements for combobox in EUI: elastic/eui#2841

Closing this issue as there's nothing more to do Kibana side

@myasonik myasonik closed this as completed Oct 2, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Feature:Dashboard Dashboard related features Project:Accessibility Team:Visualizations Visualization editors, elastic-charts and infrastructure WCAG A
Projects
None yet
Development

No branches or pull requests

6 participants