[Search:AppSearch:Credentials page]Issues with API keys table

[L1nBra]

Description
For user it should be clear what table is about, how many rows, columns it contains. Without any strange or unexpected announcements.

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

Steps to reproduce

1.Press T key while on the page to navigate to the API keys table.
2.Observe table and screen reader.
3.Navigate to Edit button while pressing Tab key.
4.Press Enter.
5.Navigate to Update button.
6.Press Enter.
7.Observe screen reader.
8.Press Enter (focus should still be on Edit button).
9.Navigate to Close button.
10.Press Enter.
11.Observe screen reader.

UI elements + NVDA Speech Viewer

[step 2]

[step 7]

[step 11]

Actual Result

• [step 2] Table has 3 rows, but it is announced "table with 4 rows... This table contains 3 rows out of 1 rows...".
  [step 7] After pressing Enter on Update on flyout, focus is on Edit button, row 3 is also announced "row 3 Type column 2...".
  [step 11] After pressing Enter on Close button on flyout, focus is on Edit button, "out of table clickable" is announced.

Expected Result

• [step 2] Table is announced correctly that it contains 3 rows.
  [step 7] After pressing Enter on Update on flyout, no additional rows are announced. If needed, only announcement about the row in which Edit buttons is, is announced. Or only Edit button is announced.
  [step 11] After pressing Enter on Close button on flyout, no announcement about "out of table" is made. Only announcement about Edit button.

Meta Issue

Kibana Version: 8.17.0-SNAPSHOT

OS: Windows 11 Pro

Browser: Chrome Version 130.0.6723.70 (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/search-team/issues/8256

[elasticmachine]

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