Skip to content

Min/Max Filter bounds #372

@obr42

Description

@obr42

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.

Metadata

Metadata

Assignees

No one assigned

    Labels

    code smellNot good, but not so bad it's a bug

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions