Select

Keyboard accessibility is very important. See for yourself why the first and third example works and the second won't. Example 2 fails on WCAG Succes Criterion 3.2.2.

Example 1

Use Tab until the focus is on year and use the down-arrow key ↓ to select any year.

Example 2

Use Tab until the focus is on year and use the down-arrow key ↓ to select 2019.

Example 3

Use Tab until the focus is on year and use the down-arrow key ↓ to select 2019 and submit Year #3.

Year 3 2016 2017 2018 2019 2020 Submit

You selected the following year:

Screenreaders and select

Windows vs. macOS One of the largest roadblocks in creating an accessible cross-platform select component is that different platforms have fundamental disagreements on what a select component actually is. If you inspect the underlying Accessibility API mappings on Windows and macOS for a <select> element, you’ll notice that it maps to a combobox on Windows and a popup button (which opens a menu) on macOS.

Source:<select> your poison on 24 Accessibility