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:Settings page]State change when activating elements not announced #205704

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

[Security:Cases:Settings page]State change when activating elements not announced #205704

L1nBra opened this issue Jan 7, 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 7, 2025

Description
When activating elements their state change has to be correctly announced, especially for the users using assistive technology.

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

Steps to reproduce

1.Navigate to Case closure options radio buttons.
2.Check unchecked radio button by pressing down or up arrow key.
3.Observe screen reader.

UI elements + NVDA Speech Viewer
Image

Actual Result

  • Upon reaching unchecked radio button it is announced as not checked. But no announcement that it is checked when it is marked as checked.

Expected Result

  • After announcement of not checked radio button it should also state checked, because visually it is present as checked upon reaching it.

Notes:
Only when user navigates to another element and comes back to now checked radio button - it is announced as checked.

Similar with Preview button: when user press Enter on it, visually name changes to Editor, but it is not announced to the user. Only if user would navigate to another element and comes back, then it is announced as Editor.
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/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 7, 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 7, 2025
@botelastic botelastic bot removed the needs-team Issues missing a team label label Jan 7, 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
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