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:Explore:Users page]Incorrect navigation #205314

Open
L1nBra opened this issue Dec 31, 2024 · 2 comments
Open

[Security:Explore:Users page]Incorrect navigation #205314

L1nBra opened this issue Dec 31, 2024 · 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 Dec 31, 2024

Description
Navigation has to be in sequence and in logical order. After closing, canceling dialogs/flyouts, activating elements - navigation should go to the element which activation opened dialog, to the first element which appeared after button activation. Otherwise user will need to navigate longer in order to come back to the element which opens dialog, to reach new elements.

Preconditions
Security -> Explore -> Users page is opened.

Steps to reproduce

1.Using only keyboard navigate to Inspect by pressing Tab key.
2.Press Enter.
3.Navigate to Close button.
4.Press Enter.
5.Press Tab key few times.
6.Observe page.

Screen recording
https://github.com/user-attachments/assets/f271e913-6608-4931-8e6b-f516e7a11acf

Actual Result

  • Navigation goes to Skip to main content element.

Expected Result

  • Navigation goes to either Inspect button or, if dialog has to close, to Panel options button.

Notes:
Similar behavior when:
-checking/unchecking Show external alerts checkbox. Navigation goes to Skip to main content instead of staying on the checkbox and then moving to next element after pressing Tab key.
Image

-navigating through tabs and activating them by pressing Enter. Navigation goes to Skip to main content instead of staying on the active tab and then moving to next element after pressing Tab key.
Image

-changing rows per page. Navigation goes to Skip to main content instead of staying on the Rows per page and then moving to next element after pressing Tab key.
Image

Meta Issue

Kibana Version: 8.17.0-SNAPSHOT

OS: Windows 11 Pro

Browser: Chrome Version 131.0.6778.140 (Official Build) (64-bit)

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 Dec 31, 2024
@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 and removed needs-team Issues missing a team label labels Dec 31, 2024
@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