[Observability:Alerts page]Drag and drop not working with keyboard or keyboard and NVDA

[L1nBra]

Description
Drag and drop functionality should be working for only keyboard users. Also for keyboard and screen reader (NVDA) users.

Preconditions
Observability -> Alerts page.
At least two filter already added in Add filter.

Steps to reproduce

1.Navigate to Add filter button.
2.Press Enter.
3.Navigate to drag handle.
4.Press Spacebar.
5.Press up/down arrow keys few times.
6.Observe the page.
7.While on drag handle press insert + Spacebar with NVDA turned on (to get in focus mode).
8.Press Spacebar.
9.Press up/down arrow keys few times.
10.Observe the page.

Screen recording
https://github.com/user-attachments/assets/bc3ae825-61dc-4a14-98ac-6e88a4a0c8d4

UI elements + NVDA Speech Viewer

Actual Result

• Filter row is not moved to another position.

Expected Result

• Filter row is moved to another position.

Notes:
Similar with drag and drop keyboard + NVDA
-Navigate to Columns button -> press Enter -> navigate to dragable element -> press insert + Spacebar (to get in focus mode) -> press arrow keys. Result: NVDA announces that "...lifted an item...", but user cannot drag and drop, it's not working. (Even though with only keyboard in this place it is working correctly).

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 2.1.1: Keyboard (Level A)(https://www.w3.org/WAI/WCAG22/Understanding/keyboard.html)

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

[elasticmachine]

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

[jasonrhodes]

@heespi @cnasikas I believe this is an accessibility issue (critical level-1) that's embedded in the alert table, can you confirm?

[elasticmachine]

Pinging @elastic/response-ops (Team:ResponseOps)

[cnasikas]

@jasonrhodes The columns are part of the alerts table, but the search bar above the table is not. We do not own the search bar. I am not sure which team is responsible for it. I put it to our board to address the column's accessibility issue.