You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
During a recent accessibility audit, we were told that, when TABing through the page if at least one value has already been added, no label is communicated to ATs.
During a recent accessibility audit, we were told that, when TABing through the page if at least one value has already been added, no label is communicated to ATs.
Test case:
Executive summary:
selected='selected'
The reason is because TABing lands the user on a
.select2-search__field
input. It currently renders like this in Chrome like:(Looks different when no item is selected)
Maybe use text from
<label for="xxx">
because<select id="xxx"
is known?Maybe an
aria-label="<placeholder>"
?Better ideas?
The text was updated successfully, but these errors were encountered: