-
Notifications
You must be signed in to change notification settings - Fork 125
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
Should aria-valuenow be required if aria-valuetext is used? #2260
Comments
I've been doing some random testing just today, coming at this from the different side (just having Incidentally, in at least some variation (it may have been Safari/VoiceOver/macOS), it seems that using both (hat-tip to @aardrian for pointing me to this issue just now) |
a few quick points from my testing - using just
haven't got the energy to run my whole battery of tests again using slider rather than |
Discussed briefly in today's meeting, no conclusion was reached: https://www.w3.org/2024/07/11-aria-minutes.html#t08 |
per the way the conversation was going towards the end of the call today, i think it's important to reiterate that the proposal here isn't to say there is no value to aria-valuenow, or to even try and say that authors don't need the attribute, or that there couldn't be uses cases for using both together. the point is to acknowledge that there are use cases where using both together is unnecessary and potentially even unwanted for the intended user experience. but right now it is "required" to specify both, and that seems overly prescriptive. |
Discussed in today's meeting: https://www.w3.org/2024/07/18-aria-minutes.html#t08 |
Happened across this issue in axe-core today - dequelabs/axe-core#4515, and I think it raises a good question. Is there a good reason (for a user) for an author to need to maintain both an aria-valuenow and an aria-valuetext?
take for instance the youtube video scrubber:
if one were to remove the aria-valuenow, from my quick testing with Narrator, VoiceOver (macos/ios), NVDA and JAWS, there was no negative user impact to understanding the slider since the aria-valuetext was still being conveyed.
the visual styling of the indicator for sliders, progressbars, etc., are often not even based on the value of aria-valuenow
so largely this seems like it might just be 'extra work' for developers if they're using aria-valuetext, but still being required to declare an aria-valuenow which doesn't get exposed to users, and is not often the source of the visual styling for the slider/progressbar/etc. indicator.
But, maybe i'm missing something and this attribute still can be accessed and has value to users I'm not thinking about???
I'm less concerned about if authors might have use for it - cause if they do, great. Keep using it. This issue is just focused on determining why it needs to be an author requirement to specify the attribute if an author doesn't need it / it isn't being exposed to users anyway?
The text was updated successfully, but these errors were encountered: