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) Page size doesnt read instructions #28299

Closed
aphelionz opened this issue Jan 9, 2019 · 2 comments
Closed

(Accessibility) Page size doesnt read instructions #28299

aphelionz opened this issue Jan 9, 2019 · 2 comments
Assignees
Labels
Feature:Rollups Project:Accessibility Team:Kibana Management Dev Tools, Index Management, Upgrade Assistant, ILM, Ingest Node Pipelines, and more WCAG A

Comments

@aphelionz
Copy link
Contributor

Steps to reproduce (assumes ChromeVox or similar)

  1. Navigate to Rollup Jobs UI
  2. Click Create Rollup Job
  3. Tab to the page size field

screenshot_20190108_194517

Actual Result

  1. The label is read but not the instructions like the other fields

Expected Result

  1. Screen reader should read "A larger page size will roll up data quicker, but requires more memory."

Meta Issue #26862

Kibana Version: 6.5

Relevant WCAG Criteria: 3.3.2 Labels or Instructions

@rayafratkina rayafratkina added WCAG A Team:Kibana Management Dev Tools, Index Management, Upgrade Assistant, ILM, Ingest Node Pipelines, and more labels Feb 25, 2019
@elasticmachine
Copy link
Contributor

Pinging @elastic/es-ui

@PhilippBaranovskiy
Copy link
Contributor

PhilippBaranovskiy commented May 17, 2019

Tested with NVDA, it works as expected.

It doesn't work with ChromeVox Chrome extension since the last one doesn't support correctly aria-labelled and aria-describedby attributes.
The Google developers says that ChromeVox Classic doesn't support aria-describedby, but ChromeVox Next does.

Unfortunately, Chrome extenstion is backported ChromeVox Classic version:

Capture2

while ChromeVox Next is just a operation system program that comes installed on Chromebooks.
Therefore, I suggest that we shouldn't take ChromeVox results into account as well as switching from ChromeVox extenstion to NVDA unless we could use a Chromebook for that purpose.

cc @bhavyarm

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Feature:Rollups Project:Accessibility Team:Kibana Management Dev Tools, Index Management, Upgrade Assistant, ILM, Ingest Node Pipelines, and more WCAG A
Projects
None yet
Development

No branches or pull requests

5 participants