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

Screenreader doesn't announce that user is in a new space #23885

Closed
1 of 3 tasks
bhavyarm opened this issue Oct 5, 2018 · 6 comments
Closed
1 of 3 tasks

Screenreader doesn't announce that user is in a new space #23885

bhavyarm opened this issue Oct 5, 2018 · 6 comments
Labels
bug Fixes for quality problems that affect the customer experience Feature:Security/Spaces Platform Security - Spaces feature Project:Accessibility Team:Security Team focused on: Auth, Users, Roles, Spaces, Audit Logging, and more! WCAG A

Comments

@bhavyarm
Copy link
Contributor

bhavyarm commented Oct 5, 2018

Kibana version: 6.x latest snapshot

Browser version: chrome latest

Browser OS version: OS X

Original install method (e.g. download page, yum, from source, etc.): from snapshots

Describe the bug: When a non-sighted user navigates to a space - User doesn't know that he is in that space.

Steps to reproduce:

  1. Use voiceover
  2. Have more than one space
  3. Try to navigate to a space using keyboard
  4. Screenreader doesn't let the user know that she is in that space.

Screenshots (if relevant):
screen shot 2018-10-05 at 12 26 28 pm

Steps to fix that:

@bhavyarm bhavyarm added bug Fixes for quality problems that affect the customer experience Project:Accessibility Team:Security Team focused on: Auth, Users, Roles, Spaces, Audit Logging, and more! Feature:Security/Spaces Platform Security - Spaces feature labels Oct 5, 2018
@legrego
Copy link
Member

legrego commented Oct 15, 2018

Hey @bhavyarm,

Can you elaborate a bit on what you expect the behavior to be? When I am on the space selector screen (or using the space selector from the Kibana nav), the screen reader reads each available space when you tab through the list, and allows the space to be selected via keyboard.

Are you expecting the screen reader to announce the current space when navigating to each app within Kibana? I'm not sure if we have a mechanism for doing that, currently.

What we have now (not announcing) is consistent with the app-switching experience today. Switching between Discover and Timelion, for example, does not announce the new application when the page reloads.

I'm happy to research this further, because I do think it'd help the user experience when using a screen reader, but I likely won't prioritize this for 6.5, unless we deem this a blocker.

@bhavyarm
Copy link
Contributor Author

@legrego it's definitely not a blocker. @aphelionz any inputs? I know I am talking about accessibility and not compliance :) Thanks!

@aphelionz
Copy link
Contributor

Can you make it say "Switching to space ____" when the user clicks to select one? i.e. right before it transitions

@legrego
Copy link
Member

legrego commented Nov 26, 2018

Can you make it say "Switching to space ____" when the user clicks to select one? i.e. right before it transitions

@cchaos Do you know if there's a way to do this within EUI, without introducing an artificial construct? My thought here would be to add a screenreader-only alert to the DOM after clicking the link, and delay the transition long enough for the screen reader to announce this. Sounds like it could be flaky though, depending on the speed of the screen reader, and the length of the space name.

The artificial delay would also get in the way of #25930. We want to change these click handlers to use href instead of onClick events. Using href means that we won't be able to introduce a delay at all, so I'm thinking we'd need to somehow change that loading splash screen that currently just announces "Kibana"

@cchaos
Copy link
Contributor

cchaos commented Nov 29, 2018

@legrego So I talked this over with the design team and the solution we agreed on is to utilize the Kibana toast service.

However, there needs to be an addition to the service that allows for screen-read-only toasts. Meaning the UI is hidden from sighted users, but the toast will be read like an alert for all screen-reader users.

There is an EUI component called EuiScreenReaderOnly that you can wrap the toast in.

@myasonik
Copy link
Contributor

Closing this in favor of #98615 which is a more succinct report and solution of the same problem.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Fixes for quality problems that affect the customer experience Feature:Security/Spaces Platform Security - Spaces feature Project:Accessibility Team:Security Team focused on: Auth, Users, Roles, Spaces, Audit Logging, and more! WCAG A
Projects
None yet
Development

No branches or pull requests

7 participants