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

[ML] [Accessibility] "Select this row" checkbox should also read ID or description #28390

Closed
aphelionz opened this issue Jan 9, 2019 · 3 comments · Fixed by #40149
Closed

Comments

@aphelionz
Copy link
Contributor

Steps to reproduce (assumes ChromeVox or similar)

  1. Navigate to Machine learning, ensure there is at least one job
  2. Tab to the table and to one of the check boxes on the right of the row

screenshot_20190109_122756

Actual Result

  1. Screen reader reads "Select this row, checkbox unchecked"

Expected Result

  1. Screen reader should include ID or description i.e "Select filebeat-apache-2..." or "Select Apache2 Access Logs"

Meta Issue #26855

Kibana Version: 6.5

Relevant WCAG Criteria: 3.3.2 Labels or Instructions

@elasticmachine
Copy link
Contributor

Pinging @elastic/ml-ui

@jgowdyelastic jgowdyelastic changed the title (Accessibility) "Select this row" checkbox should also read ID or description [ML] (Accessibility) "Select this row" checkbox should also read ID or description Jan 9, 2019
@jgowdyelastic jgowdyelastic changed the title [ML] (Accessibility) "Select this row" checkbox should also read ID or description [ML] [Accessibility] "Select this row" checkbox should also read ID or description Jan 9, 2019
@peteharverson
Copy link
Contributor

This requires work on EUI tables to allow labeling of table row selection checkboxes - see elastic/eui#747

@peteharverson
Copy link
Contributor

Raised issue to allow setting of the aria-label for the EUI table row selection checkboxes - see elastic/eui#1697.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

6 participants