Screen Readers not able to read dropdown options when we have search functionality

[gnbm]

Hello @sa-si-dev
While doing accessibility tests based on a customer request, I found out that once we have search functionality on the dropdowns, the screen readers are not able to read the dropdown options. So, using the arrow keys to move up and down through the list of options only causes the screen reader to say 'blank' (if the user has entered no characters in the search bar), or whatever characters the user has entered.
Also, when a selection is made, nothing is read out to the user, so they would have no way of knowing which selection has just been made. The icon to delete the search data typed by the end user doesn't seem to be reachable using the keyboard.
This is quite urgent in terms of accessibility (which is a hot topic nowadays), is there a way to achieve this with the current version?
Cheers

[gnbm]

Just to complement, running for instance Wave we can get this information:

[gnbm]

What was done in v1.0.38?

• Added new searchFormLabel option. This option will the used to enhance accessibility when using the search functionality on the dropdowns. Default = 'Search'
• Added new ariaLabelText option. This option will the used to enhance accessibility when focusing on the dropdown wrapper making it verbose. Default = 'Options list'.

Still Missing

• screen readers are not being able to read the options while navigating the list of options since the focus seems to stay on the search box (they spell "blank" or the text that is on the search box);
• screen readers are not being able to read the selected options;
• once on the list of options we cannot go back to the search box;
• we cannot reach the clear icons using the keyboard and they're not read by the screen readers;

cc: @sa-si-dev

[gnbm]

This issue has been fixed in the release v1.0.39.