[Feature Request]: Improve Select accessibility

[AykutSarac]

Describe the problem or use case

Noticed while using select component for city selection. I wanted to focus directly to the city starting with X, so I pressed to X key however it didn't focus/scroll to it.

Proposed solution

Should focus to the select option starting with the pressed key

Alternatives considered

No response

Additional technical context

Additionally it might listen for other keys while select visible and match the ongoing characters like XY...

[AykutSarac]

This should be discussed though whether this should be implemented along with Search functionality or separately, as I was thinking a key press may trigger focus into the search input.

[muratcorlu]

This can be considered for the

This should be discussed though whether this should be implemented along with Search functionality or separately, as I was thinking a key press may trigger focus into the search input.

Good point. I think jumping to the option by writing a name still can be a good improvement when the search is not enabled. But indeed, this can be considered with #265.

[gokcecicek]

Select Accessibility (ADR)

This improvement aims to enable users to access bl-select-option elements more easily using the keyboard.

Rules

• This feature does not work with search-bar attribute.
• When a character is pressed on the keyboard, if there is an option starting with that character among the bl-select-option elements, that option will be focused automatically.
• When characters are pressed consecutively on the keyboard, the first option starting with those characters will be focus.
• The threshold for consecutive key presses is 500.
• If the target option is disabled, it will not be focus when attempting to access it via keyboard.
• Comparisons are case-insensitive.

[AykutSarac]

• Do we need an attribute for key-press-threshold for customization, or a fixed value isn't sufficient? If there are cases that requires to set custom threshold can you include it in the ADR?
• Is there a limit on the number of characters allowed for consecutive submissions?
• Maybe we can mention that the key presses will be compared case-insensitive?

[gokcecicek]

• I don't have a specific case in mind. I added the key-press-threshold attribute to provide more flexibility. I was undecided about this matter, embedding it as 500 directly into the code seems reasonable. We can add it as a prop later if needed
• There is no char limit for consecutive submissions
• You're right! That should provide clarity for anyone reviewing the ADR. I added to ADR that it works case-insensitive.