GNOME Bugzilla – Bug 552965
aria-valuetext ignored
Last modified: 2009-01-29 22:11:43 UTC
Please describe the problem: Orca announces the aria-valuenow on a role=slider node as a floating point number (1.0, 2.0, 3.0, etc.) even when the aria-textnow is available with a purposeful human-readable description of the value (good, better, best, etc.). Steps to reproduce: See http://mindtrove.info/html/rating-tutorial.html Actual results: Expected results: Orca should report the aria-textnow when available. Does this happen every time? Yes. Other information: http://groups.google.com/group/free-aria/browse_thread/thread/398cf7197cd4ad3
We'll try to take a look at this as we revisit the ARIA support in Orca. Thanks!
Created attachment 127415 [details] [review] First pass at this Here's a first pass that seems to work rather nicely with the test page given in the opener for the bug report. It also cleans up some redundancy in the Gecko speech generator. Running the regression tests now.
Created attachment 127498 [details] [review] A little better patch that also includes some regression test changes This patch changes how we grab the valuetext value -- it just looks at the remainder of the property value instead of splitting the string at ":". It occurred to me that the valuetext value might have :'s in it. D'Oh. In running the regression tests, I also found that the mozilla and dojo tests both use valuetext, so the tests needed adjusting as well. A couple of the dojo slider examples need some improvement in their valuetext support, IMO, so I also logged a bug here: http://bugs.dojotoolkit.org/ticket/8539. The only reason I'm anal about that is that they should promote accessible design since a lot of people code by example. It pylints and regression tests well. Committed to trunk.
Also committed to gnome-2-24 for Orca v2.24.4.