[Bug] A11y: SelectPanel listbox does not have an aria label

[mijpeterson]

Describe the bug
When using the SelectPanel component, it appears that we are unable to configure the listbox it renders with an aria label. This means that it does not have an accessible name.

Digging into the code, I've found that the SelectPanel does spread the rest of its props over to the FilteredActionList component, which then gets passed down to the ActionList component. So if we were able to supply an "aria-label" or "title" prop to SelectPanel, then we'd be able to solve this bug. However, the SelectPanel's type definition for its props does not accept List props.

To Reproduce
Steps to reproduce the behavior:

1. Go to SelectPanel docs
2. Expand one of the example SelectPanels
3. Open developer tools
4. See error

Expected behavior
"title" or "aria-label" is defined for the listbox.

Screenshots

Desktop (please complete the following information):

• OS: Windows 11
• Browser: Edge
• Version: 103.0.1264.77

Additional context
The easier way to solve this issue would be to expose one of "aria-label" or "title" through the SelectPanel's props type. However, given that the ActionList component that it uses under the hood is deprecated, this might be a good chance to switch over the internals.

[siddharthkp]

Hi! Thanks for taking the time to open an issue, I have added it to our backlog to look into!

[github-actions]

Hi! This issue has been marked as stale because it has been open with no activity for 180 days. You can comment on the issue or remove the stale label to keep it open. If you do nothing, this issue will be closed in 7 days.

[mijpeterson]

Commenting to keep the issue open.

[github-actions]

Hi! This issue has been marked as stale because it has been open with no activity for 180 days. You can comment on the issue or remove the stale label to keep it open. If you do nothing, this issue will be closed in 7 days.

[mijpeterson]

Commenting to keep the issue open.

[lesliecdubs]

@siddharthkp do you think any of our active work right now on SelectPanel might resolve this? If not, should we consider adding it to the scope?