Is your feature request related to a problem? Please describe.

When auditing the combo box component and checking against WCAG 3.3.2, I noticed the ARIA instructions were verbose. Given that they are very specific instructions, in order to pass that Success Criteria, should we also reflect those instructions visibly on the page?

Here's what it says:
When autocomplete results are available use up and down arrows to review and enter to select.
Touch device users, explore by touch or with swipe gestures.

Based on feedback from AT users during our Buffalo batch of usability research testing, most screen reader users were familiar with how to navigate a combo box with a keyboard. Issues found during testing didn't reveal those instructions were necessary.

If we were to leave the instructions as-is we'd want to add recommendations visibly on the page that reflect the keyboard usability. We feel the majority of users know how to interact with a combo box and the instructions are an unnecessary addition that would make the user experience more cumbersome visibly and potentially, audibly.

Describe the solution you'd like

Remove lines L264-267. Instructions are too general to be helpful.

Describe alternatives you've considered

We considered adding instructions visible on the page that reflect the audible ARIA instructions. However, that would lengthen the page unnecessarily. We'd follow this guidance https://www.w3.org/WAI/WCAG21/Understanding/labels-or-instructions that suggests instructions be equally visible and audible (ie accessible to all users). In order to pass this SC, we recommend removing those additional keyboard instructions so the visible and audible instructions are more analagous.

Additional context

No response

Code of Conduct

• I agree to follow this project's Code of Conduct.
• I checked the current issues for duplicate feature requests.