This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.

Bug 8554 - <progress> element should be labelable with a label
Summary: <progress> element should be labelable with a label
Status: CLOSED FIXED
Alias: None
Product: HTML WG
Classification: Unclassified
Component: pre-LC1 HTML5 spec (editor: Ian Hickson) (show other bugs)
Version: unspecified
Hardware: PC All
: P2 normal
Target Milestone: ---
Assignee: Ian 'Hixie' Hickson
QA Contact: HTML WG Bugzilla archive list
URL:
Whiteboard:
Keywords: a11y
Depends on: 12254
Blocks:
  Show dependency treegraph
 
Reported: 2009-12-26 23:06 UTC by Maciej Stachowiak
Modified: 2011-03-06 10:26 UTC (History)
5 users (show)

See Also:


Attachments

Description Maciej Stachowiak 2009-12-26 23:06:45 UTC
In native UI, progress bars sometimes have an associated piece of text that could be considered a label. For example, in a download manager showing multiple progress bars, the item name would likely be the label. Particularly if <progress> is changed to only support setting the progresss programatically and not declaratively via markup, it should be labelable like a form control.
Comment 1 Ian 'Hixie' Hickson 2010-01-06 11:30:23 UTC
EDITOR'S RESPONSE: This is an Editor's Response to your comment. If you are satisfied with this response, please change the state of this bug to CLOSED. If you have additional information and would like the editor to reconsider, please reopen this bug. If you would like to escalate the issue to the full HTML Working Group, please add the TrackerRequest keyword to this bug, and suggest title and text for the tracker issue; or you may create a tracker issue yourself, if you are able to do so. For more details, see this document:
   http://dev.w3.org/html5/decision-policy/decision-policy.html

Status: Did Not Understand Request
Change Description: no spec change
Rationale: Does this also apply to <meter>, <output>, <time>, <video>, <iframe>, <embed>, etc?

Or does it only apply to <progress> and the elements that currently are categorised as "labelable form-associated elements"?

Making <label> apply to <progress> is a pretty complicated set of changes (with a pretty complicated set of implementation requirements), so I want to be absolutely clear about whether that's what you mean before doing it.
Comment 2 Ian 'Hixie' Hickson 2010-01-06 11:31:15 UTC
(Also, are ARIAs various labeling mechanisms adequate for this? If not, why not?)
Comment 3 Maciej Stachowiak 2010-01-06 19:46:12 UTC
It does not apply to <video>, <iframe> or <embed>, as the closest equivalents to those do not normally have labels in native UI. I think it would equally apply to <meter>. I don't know enough about the intended rendering and use of <output> to be sure, but it probably does need to be labeled.

aria-labeledby would work OK, however, and is not materially different from using <label> for elements that do not take focus or react to clicks. I'm happy to withdraw the request if you think it's ok to have that be the recommended approach for particular built-in controls. If that's your position, feel free to mark WONTFIX.

Reopening for further disposition.
Comment 4 Ian 'Hixie' Hickson 2010-01-06 23:34:40 UTC
I guess I'll make <meter> and <progress> into proper form controls (and move them to the form controls section), and make them and <output> labelable.
Comment 5 Ian 'Hixie' Hickson 2010-01-07 03:39:06 UTC
EDITOR'S RESPONSE: This is an Editor's Response to your comment. If you are satisfied with this response, please change the state of this bug to CLOSED. If you have additional information and would like the editor to reconsider, please reopen this bug. If you would like to escalate the issue to the full HTML Working Group, please add the TrackerRequest keyword to this bug, and suggest title and text for the tracker issue; or you may create a tracker issue yourself, if you are able to do so. For more details, see this document:
   http://dev.w3.org/html5/decision-policy/decision-policy.html

Status: Accepted
Change Description: see diff given below
Rationale: Concurred with reporter's comments.
Comment 6 contributor 2010-01-07 06:25:57 UTC
Checked in as WHATWG revision r4531.
Check-in comment: Make <progress>, <meter>, and <output> labelable with <label>.
http://html5.org/tools/web-apps-tracker?from=4530&to=4531
Comment 7 Michael Cooper 2010-02-11 17:18:04 UTC
The HTML Accessibility Task Force intends to track these issues, per the proposal at http://lists.w3.org/Archives/Public/public-html-a11y/2010Jan/0245.html.
Comment 8 Maciej Stachowiak 2010-03-14 18:20:12 UTC
Looks good to me.
Comment 9 Michael Cooper 2010-08-28 14:38:11 UTC
http://www.w3.org/2002/09/wbs/44061/20080513_bugs/results#xq12

Remove Task Force tracking of this bug. Original submitter may pursue it further if they wish, though it appears this one has been resolved satisfactorily.