Description
Navigation through elements should be clear and easily understandable. It should be in sequence, and each interactive element when reached by the user should get an indication that user is on it - focus visible.
Preconditions
Stateful Home page (Overview) is opened.
Steps to reproduce
1.Navigate to New button while using only keyboard by pressing Tab key.
2.Press Enter.
3.Press Tab key.
4.Press Tab key.
Gif showing issue
Setup button
Actual Result
There is no focus on any element so cannot understand which element should be active.
Expected Result
After x (close) button, Setup button should get focus visible.
Notes:
When user is on X (close) button and presses Tab key, he/she can press either Enter or Space bar key - nothing happens.
Only after pressing Tab key one more time, focus is visible on Setup button.
Meta Issue
Kibana Version: 8.16.0-SNAPSHOT
OS: Windows 11 Pro
Browser: Chrome Version 129.0.6668.70 (Official Build) (64-bit)
Indices page with Default settings dialog. When on x (close) button user presses Tab key - no focus visible on ingest pipelines link. It appears on the link, when user one more time presses Tab key.
Description Navigation through elements should be clear and easily understandable. It should be in sequence, and each interactive element when reached by the user should get an indication that user is on it - focus visible.
Preconditions Stateful Home page (Overview) is opened.
Steps to reproduce
1.Navigate to New button while using only keyboard by pressing Tab key. 2.Press Enter. 3.Press Tab key. 4.Press Tab key.
Gif showing issue
Setup button
Actual Result
Expected Result
Notes: When user is on X (close) button and presses Tab key, he/she can press either Enter or Space bar key - nothing happens. Only after pressing Tab key one more time, focus is visible on Setup button.
Meta Issue
Kibana Version: 8.16.0-SNAPSHOT
OS: Windows 11 Pro
Browser: Chrome Version 129.0.6668.70 (Official Build) (64-bit)
WCAG or Vendor Guidance (optional)
Related to: https://github.com/elastic/search-team/issues/8256