8554 2009-12-26 23:06:45 +0000 <progress> element should be labelable with a label 2011-03-06 10:26:17 +0000 1 1 1 Unclassified HTML WG pre-LC1 HTML5 spec (editor: Ian Hickson) unspecified PC All CLOSED FIXED a11y P2 normal --- 12254 1 mjs ian ian laura.lee.carlson mike public-html-admin public-html-wg-issue-tracking public-html-bugzilla oldest_to_newest 30258 0 mjs 2009-12-26 23:06:45 +0000 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. 30646 1 ian 2010-01-06 11:30:23 +0000 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. 30647 2 ian 2010-01-06 11:31:15 +0000 (Also, are ARIAs various labeling mechanisms adequate for this? If not, why not?) 30682 3 mjs 2010-01-06 19:46:12 +0000 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. 30689 4 ian 2010-01-06 23:34:40 +0000 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. 30690 5 ian 2010-01-07 03:39:06 +0000 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. 30692 6 contributor 2010-01-07 06:25:57 +0000 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 31769 7 cooper 2010-02-11 17:18:04 +0000 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. 33547 8 mjs 2010-03-14 18:20:12 +0000 Looks good to me. 38118 9 cooper 2010-08-28 14:38:11 +0000 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.