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

[Observability:Rules page]Incorrect announcement when selecting option #211258

Open
L1nBra opened this issue Feb 14, 2025 · 1 comment
Open

[Observability:Rules page]Incorrect announcement when selecting option #211258

L1nBra opened this issue Feb 14, 2025 · 1 comment
Labels
defect-level-2 Serious UX disruption with workaround impact:high Addressing this issue will have a high level of impact on the quality/strength of our product. needs-team Issues missing a team label obs-accessibilty A11Y issues in the Obs. solution. Project:Accessibility WCAG A

Comments

@L1nBra
Copy link

L1nBra commented Feb 14, 2025

Description
When checking options - state change has to be correctly announced that user, using screen reader, would know that he successfully selected/unselected option.

Preconditions
Observability -> Rules page.
Use Screen Reader (NVDA).

Steps to reproduce

1.Navigate to Type.
2.Press Enter.
3.Select few options (press Enter on them)
4.Observe screen reader.

UI elements + NVDA Speech Viewer
Image

Actual Result

  • No announcement that it was selected/unselected is made. Checked option is announced as "not selected".

Expected Result

  • When selecting/unselecting option - it is announced accordingly as selected/unselected. When user navigate to already selected option - it is announced as "selected".

Notes:
Similar with
-options in Response dialog
Image

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/1254

@L1nBra L1nBra added defect-level-2 Serious UX disruption with workaround impact:high Addressing this issue will have a high level of impact on the quality/strength of our product. obs-accessibilty A11Y issues in the Obs. solution. Project:Accessibility WCAG A labels Feb 14, 2025
@elasticmachine
Copy link
Contributor

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

@botelastic botelastic bot added the needs-team Issues missing a team label label Feb 14, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
defect-level-2 Serious UX disruption with workaround impact:high Addressing this issue will have a high level of impact on the quality/strength of our product. needs-team Issues missing a team label obs-accessibilty A11Y issues in the Obs. solution. Project:Accessibility WCAG A
Projects
None yet
Development

No branches or pull requests

2 participants