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:Engines:Overview page]Not interactive element in response body gets focus and NVDA stops announcing text #202745

Open
L1nBra opened this issue Dec 3, 2024 · 2 comments
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 Dec 3, 2024

Description
Only interactive elements should get in focus and NVDA should still continue to announce other elements when user navigates to them.

Preconditions
Stateful App Search -> Engines -> API Logs page is opened.
Engine is added.
Use Screen Reader (NVDA).

Steps to reproduce

1.Navigate to Details button in the first row in the Recent API tabs table.
2.Navigate with Tab through elements in Request details flyout.
3.Observe flyout and screen reader.
4.Close the flyout.
5.Continue navigating through element by pressing Tab key.
6.Observe screen reader.

UI elements + NVDA Speech Viewer

[step 1]
Image

[step 3]
Image

[step 6]
Image

Actual Result

  • Response body (when pressed Enter on first row Details) gets focus visible when user navigates through flyout. NVDA stops announcing anything after that (the text, elements are only present in speech viewer but not announced).

Expected Result

  • If response body element should really be not interactive then it should not get in focus. NVDA should continue announcing other elements after this one.

Notes: after some time or closing then opening NVDA speech viewer, again it starts announcing elements.

Meta Issue

Kibana Version: 8.17.0-SNAPSHOT

Screen reader: NVDA

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 Dec 3, 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 Dec 3, 2024
@botelastic botelastic bot removed the needs-team Issues missing a team label label Dec 3, 2024
@L1nBra
Copy link
Author

L1nBra commented Dec 3, 2024

Same as issue #202690 only on another page.

@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