Last Comment Bug 559770 - make HTML 5 meter element accessible
: make HTML 5 meter element accessible
Status: NEW
: access
Product: Core
Classification: Components
Component: Disability Access APIs (show other bugs)
: unspecified
: All All
-- normal with 4 votes (vote)
: ---
Assigned To: Nobody; OK to take it and work on it
:
: alexander :surkov
Mentors:
http://dev.w3.org/html5/spec/forms.ht...
Depends on:
Blocks: html5a11y 555985 2013q3a11y 2013q4a11y 956711
  Show dependency treegraph
 
Reported: 2010-04-16 00:03 PDT by alexander :surkov
Modified: 2017-02-24 13:56 PST (History)
15 users (show)
See Also:
Crash Signature:
(edit)
QA Whiteboard:
Iteration: ---
Points: ---
Has Regression Range: ---
Has STR: ---


Attachments

Description User image alexander :surkov 2010-04-16 00:03:41 PDT
Probably similar to progressmeter however HTML5 make difference between these controls. Should expose nsIAccessibleValue.
Comment 1 User image Marco Zehe (:MarcoZ) 2011-06-08 07:12:00 PDT
Mounir, are we exposing something for the low, high, and optimum attributes? Because there is currently no accessibility API to deal with these values. The rest looks vaguely similar to the progress element, indeed.
Comment 2 User image philipp.naderer 2013-06-15 15:59:20 PDT
Firefox should expose the inner phrasing content of a meter element. I created a test case for that: http://hoffburg.at/bugreports/meter.html
Comment 3 User image alexander :surkov 2013-08-13 12:28:06 PDT
more examples: http://peter.sh/examples/?/html/meter-progress.html

Max, if it looks interesting please feel free to pick up this one.
Comment 4 User image alexander :surkov 2013-08-13 12:32:23 PDT
(In reply to Marco Zehe (:MarcoZ) from comment #1)
> Mounir, are we exposing something for the low, high, and optimum attributes?
> Because there is currently no accessibility API to deal with these values.
> The rest looks vaguely similar to the progress element, indeed.

Color is changed from green to yellow when the value is out of low/high range. I'm curious what state the element has when its value is out of optimum range?

As alternative we could expose low/high/optimum as object attributes.
Comment 5 User image Mounir Lamouri (:mounir) 2013-08-14 03:18:56 PDT
The meter element is exposing the values of low/high/optimum:
http://www.whatwg.org/specs/web-apps/current-work/multipage/the-button-element.html#the-meter-element

Regarding the states, there is NS_EVENT_STATE_OPTIMUM, NS_EVENT_STATE_SUB_OPTIMUM and NS_EVENT_STATE_SUB_SUB_OPTIMUM. You can find the logic in HTMLMeterElement::GetOptimumState().
Comment 6 User image alexander :surkov 2013-08-15 10:28:52 PDT
Ideas how to expose optimum states into accessibility API?
Comment 7 User image James Teh [:Jamie] 2013-08-15 16:52:15 PDT
Can you explain how optimum, sub-optimum and sub-sub-optimum are represented visually? I don't follow this.

I think we're going to need new accessible states, but I was imagining low, optimum and high states based on my understanding of the spec. (Object attributes could be used, but I think they should probably be boolean for the current value, not numeric.)
Comment 8 User image alexander :surkov 2013-08-15 19:26:21 PDT
(In reply to James Teh [:Jamie] from comment #7)
> Can you explain how optimum, sub-optimum and sub-sub-optimum are represented
> visually? I don't follow this.

by default green, yellow and red colors, I believe people can CSS style them as they want

> I think we're going to need new accessible states, but I was imagining low,
> optimum and high states based on my understanding of the spec. (Object
> attributes could be used, but I think they should probably be boolean for
> the current value, not numeric.)

yep, they are boolean, states sound like a right way
Comment 9 User image Mounir Lamouri (:mounir) 2013-08-16 04:14:18 PDT
I thought of bug 687202 to increase the a11y of the meter element but I never finished the patch. Would that be worth it?
Comment 10 User image alexander :surkov 2013-08-16 11:02:39 PDT
(In reply to Mounir Lamouri (:mounir) from comment #9)
> I thought of bug 687202 to increase the a11y of the meter element but I
> never finished the patch. Would that be worth it?

sure, the bug seems to be a good step forward to improve a11y and usability. this bug is different, it's about how to expose the control through a11y APIs.
Comment 11 User image alexander :surkov 2014-02-25 09:02:06 PST
AKT part is done (https://bugzilla.gnome.org/show_bug.cgi?id=684576), we need to implement it.

Curious, if Yurii wants to pick it up ;)
Comment 12 User image steve faulkner 2016-07-15 03:46:48 PDT
any update on this?
Comment 13 User image Marco Zehe (:MarcoZ) 2016-07-18 06:36:49 PDT
I have no new data on this.

Note You need to log in before you can comment on or make changes to this bug.