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
The using the Accessibility Insights for Web extension, the accessible name for the min/max filter inputs are descriptions of what the min or max are. While helpful, just having Min (0) doesn't do much for the user as a name - either add the label/title in there or make the label the name and move that text as the aria-description. The way the accessible name is written makes me think there is supposed to be a bounds set on the min/max properties i.e. Min (1) would make me think the minimum value for that field is 1, however there are no restriction bounds put on the input fields. Can min errors be -1? Is the number instead supposed to be the value of the filter - if so that should be in the description not the name.
If the input is set to 0 it comes up as undefined on the filter.
The text was updated successfully, but these errors were encountered:
The using the
Accessibility Insights for Web
extension, the accessible name for the min/max filter inputs are descriptions of what the min or max are. While helpful, just havingMin (0)
doesn't do much for the user as a name - either add the label/title in there or make the label the name and move that text as the aria-description. The way the accessible name is written makes me think there is supposed to be a bounds set on the min/max properties i.e.Min (1)
would make me think the minimum value for that field is 1, however there are no restriction bounds put on the input fields. Can min errors be-1
? Is the number instead supposed to be the value of the filter - if so that should be in the description not the name.If the input is set to
0
it comes up asundefined
on the filter.The text was updated successfully, but these errors were encountered: