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

[Security:Assets:Endpoints page]Previous button/value announced #205042

Open
L1nBra opened this issue Dec 20, 2024 · 1 comment
Open

[Security:Assets:Endpoints page]Previous button/value announced #205042

L1nBra opened this issue Dec 20, 2024 · 1 comment
Labels
needs-team Issues missing a team label Project:Accessibility

Comments

@L1nBra
Copy link

L1nBra commented Dec 20, 2024

Description
Previous button or value with the current button, selection should not be announced for users using assistive technology.

Preconditions
Security -> Assets -> Endpoints page.
Use Screen Reader (NVDA).

Steps to reproduce

1.Navigate to Query menu button by pressing Tab key.
2.Press Enter.
3.Press Enter on Language:KQL button.
4.Observe the page and screen reader.
5.Navigate to Rows per page button.
6.Select 50.
7.Observe the page and screen reader.

UI elements + NVDA Speech Viewer
[step4]
Image

[step7]
Image

Actual Result

  • "Clear button unavailable separator Language: KQL" is announced together with Filter language button.
    After selecting 50 for pages, previous value is announced "Rows per page: 10 button ".

Expected Result

  • Only "Filter language button" is announced without additional elements.
    Correct current value is announced "Rows per page: 50 button".

Meta Issue

Kibana Version: 8.17.0-SNAPSHOT

OS: Windows 11 Pro

Browser: Chrome Version 131.0.6778.140 (Official Build) (64-bit)

Screen reader: NVDA

WCAG or Vendor Guidance (optional)

Related to: https://github.com/elastic/kibana-team/issues/1280

@elasticmachine
Copy link
Contributor

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

@botelastic botelastic bot added the needs-team Issues missing a team label label Dec 20, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
needs-team Issues missing a team label Project:Accessibility
Projects
None yet
Development

No branches or pull requests

2 participants