Closed JAWS-test closed 9 months ago
HTML specification says:
[The slider element] represents a control for setting the element's value to a string representing a number, but with the caveat that the exact value is not important, letting UAs provide a simpler interface than they do for the Number state.
Therefore a slider for exact values like in the rating example would be wrong
I agree that allowing half stars has user interface issues and should be avoided, but some people like building them, so we should provide a means to help them understand how to make them accessible.
Examples:
@jongund I don't understand your argument, because if a pattern is not accessible, then it should not be used, whether someone wants it or not. I have concerns about the accessibility and usability of the pattern and think it should be rebuilt or removed. Rebuilt would mean that the click areas are large enough and that I have an visual indicator that
The ARIA Authoring Practices (APG) Task Force just discussed Rating slider issue
.
@JAWS-test We discussed the example at a meting last month and agreed that it was not a good example in its current state. We would like to have a rating example using the slider pattern, since we still feel that additional keystrokes for a larger number of rating options is useful for more efficiently selecting values.
The idea for changing the example is to change the 5 stars to 10 circles, mimicking bubble forms.
We would also add information on why the slider pattern maybe useful over the radio button pattern when the number of options is greater than some number N.
What do you think of this proposal?
@jongund Yes, that sounds good. Thanks for the planned improvements
In my opinion, the rating slider is not a pattern that we should recommend: