13620 2011-08-03 18:34:40 +0000 Clarify label vs caption 2011-08-15 13:37:01 +0000 1 1 1 Unclassified HTML WG LC1 HTML5 spec unspecified PC Windows XP RESOLVED DUPLICATE 13296 http://www.w3.org/TR/2011/WD-html5-20110525/forms.html#the-label-element a11y P2 normal --- 1 cooper ian annevk joshue.oconnor laura.lee.carlson mike public-html-a11y public-html-admin public-html-wg-issue-tracking public-html-bugzilla oldest_to_newest 52210 0 cooper 2011-08-03 18:34:40 +0000 [Filed on behalf of Joshue O Connor, so please approach him for further details / suggestions] The label is said to represent a 'caption' in a user interface. There is however there is no explanation of what “caption” means in this context. Is it the same as a 'caption' for a data table, or is it similar to the figcaption etc? I suggest linking to the section of the spec that describes what a caption is, and what it is for as well as its content model etc. 54051 1 mike 2011-08-04 05:35:40 +0000 mass-move component to LC1 54234 2 zcorpan 2011-08-05 13:43:26 +0000 Is the label element different to almost all other instances of "The foo element represents bar" where bar is not explained anywhere in further detail? For example: "The html element represents the root of an HTML document." -- root not explained. "The head element represents a collection of metadata for the Document." -- metadata not explained. "The title element represents the document's title or name. " -- title or name not explained. etc. > I suggest linking to the section of the spec that describes what a caption > is, Why not put sufficient explanation next to the definition instead of having it in a separate section? > and what it is for The next paragraph says what it is for: "The caption can be associated with a specific form control..." > as well as its content model etc. The content model is a few lines higher up: "Content model: Phrasing content, but with no descendant labelable elements unless it is the element's labeled control, and no descendant label elements." 55083 3 annevk 2011-08-15 13:37:01 +0000 *** This bug has been marked as a duplicate of bug 13296 ***