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:Cases:View page]Incorrect announcements for Alert table elements #205872

Open
L1nBra opened this issue Jan 8, 2025 · 2 comments
Open
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. Project:Accessibility Team: SecuritySolution Security Solutions Team working on SIEM, Endpoint, Timeline, Resolver, etc. WCAG A

Comments

@L1nBra
Copy link

L1nBra commented Jan 8, 2025

Description
Elements should be announced clearly without too much additional information for the users using assistive technology.

Preconditions
Security -> Cases -> View page.
Use Screen Reader (NVDA).

Steps to reproduce

1.Navigate to Alerts tab.
2.Navigate to first table element.
3.While pressing arrow keys, navigate through table element.
4.OBserve screen reader.

UI elements + NVDA Speech Viewer
Image

Actual Result

  • Screen reader is announcing all values, elements present in the table when user reaches Actions column values for the first line (there buttons present: View details, Investigate in timeline...). When user navigates to View details button separately, screen reader announces "View details...button", but button only after announcing all values in other columns for the first line.

Expected Result

  • User hears only correct elements. And would be enough for user to mention that it is f.e.: for row one instead of announcing all values in the row when navigating to each element separately. Otherwise user can easily miss on what element he/she is at the moment, or even get lost in the page.

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 Jan 8, 2025
@L1nBra L1nBra added WCAG A impact:high Addressing this issue will have a high level of impact on the quality/strength of our product. Team: SecuritySolution Security Solutions Team working on SIEM, Endpoint, Timeline, Resolver, etc. defect-level-2 Serious UX disruption with workaround labels Jan 8, 2025
@botelastic botelastic bot removed the needs-team Issues missing a team label label Jan 8, 2025
@elasticmachine
Copy link
Contributor

Pinging @elastic/security-solution (Team: SecuritySolution)

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. Project:Accessibility Team: SecuritySolution Security Solutions Team working on SIEM, Endpoint, Timeline, Resolver, etc. WCAG A
Projects
None yet
Development

No branches or pull requests

2 participants