Consider supporting and encouraging the use of native select instead of a custom dropdown

[danielck]

The Problem

The Dropdown component accomplishes the same functionality as the native HTML select element, but does not come with the benefits of the native element which are e.g.

• Automatic keyboard and AT accessibility (reducing the need for testing)
• Automatically follows differing platform conventions and keyboard interactions on Windows and macOS.
• Supports native elements on mobile without UA detection.

Proposed Solution

Develop a native select based version of the Dropdown component which is visually similar to the current one in its unopened state. Make it the recommended variant.

Alternative Solutions

Develop a separate component based on select and deprecate Dropdown.

Background

• https://www.24a11y.com/2019/select-your-poison/
• https://www.24a11y.com/2019/select-your-poison-part-2/

[LJKaski]

Thanks for the report. Basing the dropdown on the native select element was our preferred method of going about it, but there were some deal breaker issues with the approach that steered us away. @riitasointi might be able to shed some more light on this.