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) (ML) "WCAG 3.2.2 On Input does not cause a change of context" #191867

Open
barlowm opened this issue Aug 30, 2024 · 3 comments
Open

Comments

@barlowm
Copy link
Collaborator

barlowm commented Aug 30, 2024

Steps to reproduce
Open Kibana and navigate to the "Machine Learning" section then tab through the buttons, the Screen Reader should announce the label associated with each button. Tabbing to the "Level" component, the Screen Reader reads "Button Level".
Activating the "Level" component opens a new dialog and adjusts the focus so the next tab will result in the focus being set on the first entry in the dialog. But the user is not informed prior to activating the "Level" component that a change in focus will occur.

An example of a better label for the "Level" component is the button for the "Calendar" icon above, which, when tabbed into, the Screen Reader reads "Date Quick Select Button", which informs the user that activating the button will present them with a way to select a date.
Suggest adding "Select" to the "Level" component so the Screen Reader will read "Level Select Button"

Screen Shot:
Image

Expected Result
Activating the "Level" component, the screen reader should read "Level Select Button"

Kibana Version:
Kibana-8.13.2

OS:
Windows

Screen Reader:
NVDA ver 2024.3

Browser:
Chrome

Relevant WCAG Criteria:
WCAG Criterion - 3.2.2 On Input - Level A
Changing the setting of any user interface component does not automatically cause a change of context unless the user has been advised of the behavior before using the component.

@elasticmachine
Copy link
Contributor

Pinging @elastic/kibana-accessibility (Project:Accessibility)

@botelastic botelastic bot added the needs-team Issues missing a team label label Aug 30, 2024
@barlowm barlowm added :ml and removed needs-team Issues missing a team label labels Aug 30, 2024
@elasticmachine
Copy link
Contributor

Pinging @elastic/ml-ui (:ml)

@rbrtj
Copy link
Contributor

rbrtj commented Oct 18, 2024

It also seems more like an EUI issue rather than an ML issue.
I've created an issue in EUI for that:
elastic/eui#8088

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

No branches or pull requests

4 participants