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]When creating user and getting error, field in error should be in focus #200963

Open
L1nBra opened this issue Nov 20, 2024 · 1 comment
Labels
defect-level-3 Moderate UX disruption or potentially confusing 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
The field which is in error after filling and saving form (in this case adding user) should receive focus for user to instantly see where the error is and fix it faster.

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

Steps to reproduce

1.Navigate to Add a new user button by pressing Tab key.
2.Press Enter.
3.Navigate to Username field.
4.Enter any text (f.e.: test).
5.Navigate to Email field.
6.Provide incorrect email structure (f.e.: [email protected]...sdfsdf...).
7.Navigate to Add user button.
8.Press Enter.
9.Press Tab key few times.
10.Observe Add a new user flyout.

Gif showing the issue
Image

Actual Result

  • Error is shown regarding email in the top of flyout. Focus is on the error itself.

Expected Result

  • Better to have focus on the field which is in error, in this case Email field.

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 Team:Search defect-level-3 Moderate UX disruption or potentially confusing and removed needs-team Issues missing a team label labels Nov 20, 2024
@alexwizp alexwizp added the deprecated-in-9.0 Feature marked as deprecated in v9.0. This label is used within the a11y project label Dec 5, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
defect-level-3 Moderate UX disruption or potentially confusing 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