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

[Stateful:Indices:Pipelines page] Inaccessible clear buttons with keyboard #196825

Open
L1nBra opened this issue Oct 18, 2024 · 2 comments
Open
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:Search WCAG A

Comments

@L1nBra
Copy link

L1nBra commented Oct 18, 2024

Description
Buttons which gets activate by clicking them with the mouse, should behave the same when activating them with keyboard only.

Preconditions
Stateful Indices -> Pipelines page is opened.
Add an inference pipeline step 1 is filled.

Steps to reproduce

1.Navigate to Add an inference pipeline step 2 while using only keyboard by pressing Tab key.
2.Navigate to Source text field.
3.Enter any text (f.e.: test).
4.Press Tab key (focus is on Cancel button).
5.Pressing Shift + Tab key navigate back to source field.
6.Navigate to x (clear buttons) in this field.
7.Press Enter on x (clear) button.

Gif showing issue
Image

UI elements
Image

Actual Result

  • After entering text in Source field and pressing Enter - focus is on Cancel button.
    When navigating back to the Source field, to clear buttons - they do get focus but when pressing Enter, the field does not become empty.

Expected Result

  • Focus should go to the next element - clear button in the Source text field.
    When pressing Enter on clear buttons, text from the Source text field should be deleted.

Notes:
It is possible to click on clear buttons with the mouse - text from field is deleted.

Meta Issue

Kibana Version: 8.16.0-SNAPSHOT

OS: Windows 11 Pro

Browser: Chrome Version 129.0.6668.101 (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 Oct 18, 2024
@L1nBra L1nBra added WCAG A Team:Search defect-level-2 Serious UX disruption with workaround labels Oct 18, 2024
@botelastic botelastic bot removed the needs-team Issues missing a team label label Oct 18, 2024
@L1nBra
Copy link
Author

L1nBra commented Oct 22, 2024

Same behavior observed on

  • Indices -> Index mapping page, Edit field dialog

UI elements
Image

@L1nBra L1nBra added the impact:high Addressing this issue will have a high level of impact on the quality/strength of our product. label Oct 25, 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 impact:high Addressing this issue will have a high level of impact on the quality/strength of our product. Project:Accessibility Team:Search WCAG A
Projects
None yet
Development

No branches or pull requests

2 participants