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:Settings page]Fields missing title from announcement #205700

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

[Security:Cases:Settings page]Fields missing title from announcement #205700

L1nBra opened this issue Jan 7, 2025 · 2 comments
Labels
defect-level-1 Critical UX disruption 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
Field visible title should be announced for the users, especially using assistive technology to know what is the purpose of the field, what user can enter/select.

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

Steps to reproduce

1.Navigate to Add template button.
2.Press Enter.
3.Navigate to Severity field.
4.Navigate to Description field.
5.Observe screen reader.

UI elements + NVDA Speech Viewer
Image

Actual Result

  • "Low menu button opens list" is announced, no announcement about Severity field itself.
    When reaching Description field - navigation instantly goes to "Bold button". No announcement about Description field itself.

Expected Result

  • Severity field is correctly announced.
    For Description field would be better firstly to get focus on the whole field (editor) and announce it to the user, then navigation after pressing Tab key would move to Bold button which is inside in editor.

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-1 Critical UX disruption 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
Labels
defect-level-1 Critical UX disruption 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