-
Notifications
You must be signed in to change notification settings - Fork 121
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
aria-valuenow range requirement for meter role, non-consistent with other "similar" roles #2025
Comments
@giacomo-petri to check if this behavior is consistent with HTML then we will discuss |
Should this guidance change also apply to |
I'm listing below the output of my analysis, role by role, with references to the html5 specs:
|
a use case to consider in determining what to do here: a meter could very well be used to present the amount of storage space a user has for a product of some sort, a mailbox, file storage, web hosting, whatever. generally the meter would only allow a user to have their storage usage fall between the 0 to 100% of what their account allows. but, there are instances where a user's account is modified and their available storage is decreased. but the product won't typically delete their content to get them back down to their storage ceiling. Rather, the value can become larger than the maximum. This can be handled by adding extra text to say the account is over the limit, potentially even removing the instance of the meter so that there isn't a disconnect with the element stating it's at 100% with additional content saying it's more than 100%. So, really don't mind if it stays the way it is, esp. since it aligns with HTML. But, also, maybe HTML is being too strict... |
Concern description:
Concerning the "meter" role, ARIA doc states:
However, this requirement does not seem to apply to other "similar" roles such as:
or scrollbar, separator (if focusable), and slider roles, aria-valuenow is required but doesn't have a strict range requirement.
Is there a specific reason why this requirement is not applicable to these particular roles?
If it's just an inconsistency, might be worth if we remove the first requirement from meter role
and maybe add this requirement into the definition of aria-valuenow, adding something like:
"if aria-valuemin and aria-valuemax are set, then ..."
or, in alternative, add the statement
also to the other roles?
The text was updated successfully, but these errors were encountered: