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:WebCrawlers:ViewCrawler:Manage Domains page]Content radio buttons are skipped when navigating using only keyboard #199190

Closed
L1nBra opened this issue Nov 6, 2024 · 1 comment · Fixed by #201191
Assignees
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 Nov 6, 2024

Description
Not checked radio buttons should get focus in order when navigating through elements that user won't skip them, especially the ones which cannot see and relies on assistive technology.

Preconditions
Stateful Web crawlers -> View Crawler -> Manage Domains page, Extraction rules tab is opened.
Domain is added.

Steps to reproduce

1.Navigate to Add content fields rule button by pressing Tab key.
2.Press Enter.
3.Navigate to Learn more about storing... link by pressing Tab key.
4.Observe the flyout.

Actual Result

  • Radio buttons in Source section get focus, but radio buttons in Content section are skipped (don't get focus). Focus after Source radio buttons goes to the link Learn more about storing...

Expected Result

  • After Source radio buttons focus in order should go to Content radio buttons (Extracted value). After this radio button - to the link.

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 6, 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 labels Nov 6, 2024
@botelastic botelastic bot removed the needs-team Issues missing a team label label Nov 6, 2024
@jedrazb jedrazb self-assigned this Nov 21, 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

Successfully merging a pull request may close this issue.

5 participants