[Search:AppSearch:Engines:API Logs page]Not interactive element in response body gets focus and NVDA stops announcing text

[L1nBra]

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]

[step 3]

[step 6]

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)

• Understanding SC 2.1.1: Keyboard (Level A)(https://www.w3.org/WAI/WCAG22/Understanding/keyboard.html)

Related to: https://github.com/elastic/search-team/issues/8256

[elasticmachine]

Pinging @elastic/kibana-accessibility (Project:Accessibility)