The second problem is that the patch doesn't account for multi-handle sliders.
I am assuming that aria-valuenow is updating, because I can hear valuechanges using JAWS (demo version 10.0.1142 on FF3 on XP). I can also
see the aria-valuenow updating when I inspect with my firebug (1.3.2)
and using the console. In the past I've experienced problems with
firebug checking aria-valuenow using inspect. I am using the slider
demos in the jQuery trunk. I'm not sure how to replicate the problem
I've updated our patch that adds aria support to the slider.
Specifically, support for multi-handled sliders is added; included
some unit tests for this. I checked our results with NVDA and JAWS.
What we haven't included is a way for people to add aria-valuetext to
a slider. Aria-valuetext can be very important: it gives aria-valuenow
a human readible value that's meaningful. For example, on a slider
that was a thermostat, a screen reader user should hear with every
step that the value is also a degree Celcius. This could be an option
that people could specify when people add the widget to their code;
where aria-valuenow is set, aria-valuetext that people specify as an
option would be tacked on. This could have internationalization
implications though depending on the way we code this. After
aria-valuenow is set, a .attr line such as "aria-valuetext", val + "
" + this.options.unittext might not be good for nonenglish speakers if
they read from right to left. Please advise if there any jQuery string
templates we should follow or other things to consider.
You received this message because you are subscribed to the Google Groups "jQuery Accessibility" group.
To post to this group, send email to jquer...@googlegroups.com
To unsubscribe from this group, send email to jquery-a11y...@googlegroups.com
For more options, visit this group at http://groups.google.com/group/jquery-a11y?hl=en