Just today I have uploaded patches to this bug: https://bugzilla.gnome.org/show_bug.cgi?id=684576
that do a refactoring of AtkValue. One of the main objectives is including a text description for values, and include the support for ranges. Any feedback is welcome Best regards On 12/11/2013 06:15 PM, Alexander Surkov wrote: > Hi. > > HTML5 introduced meter element [1], which is basically a progressbar > role but can be in special states: > > 1) optimal state when value is in optimal rage (for example, if low > < optimum < high then value should be in [low, high], if optimum > > high then value should be greater than high. > > 2) suboptimal state when value is in range next to optimum range (for > example, if low < optimum < high then value < low is suboptimal. > > 3) subsuboptimal state when value is not neither optimal nor > suboptimal for example if optimum > high but value < low. > > Firefox colors these states as green/yellow/red. > > Would it be reasonable to introduce these states in ATK? Any other > ways to expose that info? > > [1] > http://www.whatwg.org/specs/web-apps/current-work/multipage/the-button-element.html#the-meter-element > > Mozilla bug https://bugzilla.mozilla.org/show_bug.cgi?id=559770 > Some examples: http://peter.sh/examples/?/html/meter-progress.html > Try it out: > http://www.w3schools.com/tags/tryit.asp?filename=tryhtml5_meter > > Thanks. > Alex. -- ---- Alejandro Piñeiro _______________________________________________ gnome-accessibility-devel mailing list gnome-accessibility-devel@gnome.org https://mail.gnome.org/mailman/listinfo/gnome-accessibility-devel
