@zersiax values aren't supposed to be human readable. The button needs human readable text relating to it's action and current value. That's what this system provides.
Top-level
@zersiax values aren't supposed to be human readable. The button needs human readable text relating to it's action and current value. That's what this system provides. 4 comments
@zersiax have you tested this? Remember that the browser knows that this button is a select popover activator. @jaffathecake I have not, I am purely going on your code sample and have not had a chance to look into the specifics, it just struck me as odd from that perspective :) Do you happen to have a link to a codepen where this can be tried? No problem if not, also not intending to tell you you're wrong, just expressing a knee-jerk observation :) |
@jaffathecake isn't the currently selected <option> visually distinguishable in a bog standard <select>? For reference, a screen reader will read a select as "label, combobox, current option". A button is more likely than not going to be "option, button collapsed/submenu", which loses the label, or "label, button collapsed/submenu" which loses the value. To fix this on a button you now have to cluge together the currently selected option and the button label with JS