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

[Search:AppSearch:Users and roles page]Engine assignment group is skipped when navigating with the keyboard #200947

Open
L1nBra opened this issue Nov 20, 2024 · 1 comment
Labels
defect-level-2 Serious UX disruption with workaround deprecated-in-9.0 Feature marked as deprecated in v9.0. This label is used within the a11y project Project:Accessibility Team:Search WCAG A

Comments

@L1nBra
Copy link

L1nBra commented Nov 20, 2024

Description
Navigation between two radio groups should be clear and easy. User should be able to move easily from one group to another.

Preconditions
Stateful App Search -> Users and roles page is opened.
Engine is added.

Steps to reproduce

1.Navigate to Create a new role mapping button by pressing Tab key.
2.Press Enter.
3.Navigate to Role group by pressing Tab key.
4.Navigate to Dev radio button pressing down arrow key.
5.Press Tab key.
6.Observe Create a role mapping flyout.

UI elements
Role mapping flyout
Image

New user flyout
Image

Actual Result

  • Engine assignment group is enabled, when user press Tab key - navigation goes directly to combo box field which belongs to Assign to specific engine radio button.
    Similar behavior when adding an existing user.

Expected Result

  • After pressing Tab, focus goes to Engine assignment group checked radio button (Assign to specific engines).

Notes:
It is possible to navigate from Owner radio button to Assign to specific engines radio button while pressing down arrow key. Focus moves to the next radio button and checks it. After Analyst radio button when user press down arrow key, focus shouldn't go to Engine assignment radio group.

Image

In this case if user would want a combination of Dev and Assign to all engines radio buttons, when on Dev user should press Tab key, then Esc key to close combo box options, then Shift + Tab key to move to Assign to specific engines radio button, then up arrow key to finally reach Assign to all engines radio button.

Meta Issue

Kibana Version: 8.17.0-SNAPSHOT

OS: Windows 11 Pro

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

WCAG or Vendor Guidance (optional)

Related to: https://github.com/elastic/search-team/issues/8256

@elasticmachine
Copy link
Contributor

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

@botelastic botelastic bot added the needs-team Issues missing a team label label Nov 20, 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:Search defect-level-2 Serious UX disruption with workaround and removed needs-team Issues missing a team label labels Nov 20, 2024
@alexwizp alexwizp assigned alexwizp and unassigned alexwizp Nov 21, 2024
@alexwizp alexwizp added deprecated-in-9.0 Feature marked as deprecated in v9.0. This label is used within the a11y project and removed impact:high Addressing this issue will have a high level of impact on the quality/strength of our product. labels Dec 5, 2024
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 deprecated-in-9.0 Feature marked as deprecated in v9.0. This label is used within the a11y project Project:Accessibility Team:Search WCAG A
Projects
None yet
Development

No branches or pull requests

3 participants