Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Implicit values for aria-valuemin and aria-valuemax on the slider role may need more details #988

Open
melanierichards opened this issue May 30, 2019 · 0 comments
Assignees
Labels
clarification clarifying or correcting language that is either confusing, misleading or under-specified good first issue
Milestone

Comments

@melanierichards
Copy link
Contributor

On PR #946, @mcking65 pointed out that the implicit values for aria-valuemin and aria-valuemax on slider role do not completely mirror those given in HTML for the range input type, which we reference.

Matt's words:

This list is missing the conditions where only one is specified and it invalidates the implicit value of the other. For instance, if aria-valuemax is not specified and aria-valuemin is specified as 200. Or, conversely, if aria-valuemin is not specified and aria-valuemax is set to -1.

I'm not finding at the moment where in HTML this is specified (closest I could find is that in some but not all cases max must not be less than min), but logging this as a separate issue for discussion.

@jnurthen jnurthen added this to the ARIA 1.3 milestone May 30, 2019
@MelSumner MelSumner self-assigned this Mar 18, 2021
@spectranaut spectranaut added the clarification clarifying or correcting language that is either confusing, misleading or under-specified label Sep 13, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
clarification clarifying or correcting language that is either confusing, misleading or under-specified good first issue
Projects
None yet
Development

No branches or pull requests

4 participants