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:Findings:Misconfigurations] Fields filter panel on misconfigurations is incorrectly announced as button #208266

Open
bhavyarm opened this issue Jan 24, 2025 · 2 comments
Open

[Security:Findings:Misconfigurations] Fields filter panel on misconfigurations is incorrectly announced as button #208266

bhavyarm opened this issue Jan 24, 2025 · 2 comments
Labels
defect-level-2 Serious UX disruption with workaround impact:critical This issue should be addressed immediately due to a critical level of impact on the product. Project:Accessibility Team: SecuritySolution Security Solutions Team working on SIEM, Endpoint, Timeline, Resolver, etc. WCAG A

Comments

@bhavyarm
Copy link
Contributor

Description
The fields panel using which user can select which fields can be displayed in misconfigurations table is incorrectly announced as "Fields, button". This doesn't tell the user that they can click on this and select which fields they can display in the table.

Preconditions
Security -> Findings page is populated

Steps to reproduce

  1. Open findings page -> misconfigurations
  2. Run voice over on the page
  3. Notice that the announcement for fields is just "Fields, button" and no hint about users can click on it and select which fields they can select to display in the misconfigurations table.
Image

Kibana Version: 8.17.0

OS: OX X

Browser: Chrome latest

WCAG or Vendor Guidance (optional)

Guidelines:
Understanding SC 4.1.2: Name, Role, Value (Level A)(https://www.w3.org/WAI/WCAG22/Understanding/name-role-value.html)

Related to: https://github.com/elastic/kibana-team/issues/1280
@bhavyarm bhavyarm added defect-level-2 Serious UX disruption with workaround impact:critical This issue should be addressed immediately due to a critical level of impact on the product. Project:Accessibility Team: SecuritySolution Security Solutions Team working on SIEM, Endpoint, Timeline, Resolver, etc. WCAG A labels Jan 24, 2025
@elasticmachine
Copy link
Contributor

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

@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:critical This issue should be addressed immediately due to a critical level of impact on the 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
@bhavyarm @elasticmachine