[Security:Investigations:Osquery page]Incorrect announcement for Exit full screen

[L1nBra]

Description When activating button and its' state changes, it has to be correctly announced for users using assistive technology.

Preconditions Security -> Investigations -> Osquery page. Use Screen Reader (NVDA).

Steps to reproduce

1.Navigate to Enter fullscreen toggle button. 2.Press Enter. 3.Observe page and screen reader.

UI elements + NVDA Speech Viewer

Actual Result

• Live query details table is in fullscreen, focus is on Exit full screen button. Exit full screen button is announced and instantly "pressed is announced" (even though it is not pressed yet).

Expected Result

• "pressed" is announced instantly after "Enter fullscreen toggle button not pressed" when the button is activated.

Meta Issue

Kibana Version: 8.17.0-SNAPSHOT

OS: Windows 11 Pro

Browser: Chrome Version 131.0.6778.140 (Official Build) (64-bit)

Screen reader: NVDA

WCAG or Vendor Guidance (optional)

• Understanding SC 4.1.2: Name, Role, Value (Level A)(https://www.w3.org/WAI/WCAG22/Understanding/name-role-value.html)
• Understanding SC 1.3.1: Info and Relationships (Level A)(https://www.w3.org/WAI/WCAG22/Understanding/info-and-relationships.html)

Related to: https://github.com/elastic/kibana-team/issues/1280

[elasticmachine]

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

[elasticmachine]

Pinging @elastic/security-solution (Team: SecuritySolution)

[elasticmachine]

Pinging @elastic/security-defend-workflows (Team:Defend Workflows)

[szwarckonrad]

This looks like an issue with the EuiDataGrid component. The behavior can also be reproduced here: https://eui.elastic.co/docs/components/data-grid/

[JasonStoltz]

@bhavyarm By transferring this to the EUI repo, it looks like we've lost the ACR context. Do you recall what Defect Level this is, and where it is listed in the https://github.com/elastic/kibana-team/issues/1153? We use that to determine how to prioritize EUI fixes.