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.

Sign up for GitHub

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

Jump to bottom

[Security:Cases:Create page]Incorrect announcement of timeline options #205618

Open
L1nBra opened this issue Jan 6, 2025 · 2 comments
Open

[Security:Cases:Create page]Incorrect announcement of timeline options #205618

L1nBra opened this issue Jan 6, 2025 · 2 comments
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 6, 2025

Description
Options in the list should be correctly announced for the users using assistive technology.

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

Steps to reproduce

1.Navigate to Insert timeline link (in Description field).
2.Press Enter.
3.Navigate to filter options.
4.Press down arrow key few times.
5.Observe options and screen reader.

UI elements + NVDA Speech Viewer
Image

Actual Result

  • Few options present are announced as "blank".

Expected Result

  • If dash means blank, then at least "JK Timeline blank 1 of 2" is announced. Or if they are blank and the same, one option is enough or no options present, until user enters something existing in Filter field.

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 6, 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. defect-level-2 Serious UX disruption with workaround Team: SecuritySolution Security Solutions Team working on SIEM, Endpoint, Timeline, Resolver, etc. labels Jan 6, 2025
@elasticmachine
Copy link
Contributor

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

@botelastic botelastic bot removed the needs-team Issues missing a team label label Jan 7, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
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
Milestone
No milestone
Development

No branches or pull requests
2 participants
@elasticmachine @L1nBra