- From: Steve Faulkner <faulkner.steve@gmail.com>
- Date: Sat, 6 Jul 2013 09:08:26 +0100
- To: HTMLWG WG <public-html@w3.org>
- Message-ID: <CA+ri+VkeeQP_PNbSX983+6j1jXTDP00F2Wbh7xQa2w5Zv-xJAQ@mail.gmail.com>
forgot to mention I have opened a bug so you can comment there: https://www.w3.org/Bugs/Public/show_bug.cgi?id=22586 if you like. -- Regards SteveF HTML 5.1 <http://www.w3.org/html/wg/drafts/html/master/> On 6 July 2013 09:04, Steve Faulkner <faulkner.steve@gmail.com> wrote: > Hi all, > > are there any uses cases for the <label> element[1] that does not label a > control? > > example: > > <label>name</label> <input type="text"> > > in the case above the label element is not associated with the input using > for/id or via wrapping. > > It does not appear to do anything, so why should it be conforming? would > it be helpful to authors/users if this was flagged as an error > > I have a use case for use of an additional secondary label associated > using aria-describedby: > > primary label = accessible name, auxiliary label = accessible description > > <p><label>name <input type"text" aria-describedby="instructions"></label></p> > > <p><label id="instructions">last name only please</label></p> > > > https://gist.github.com/stevefaulkner/5935190 > > is the above a reasonable use case? > > [1] > http://www.w3.org/html/wg/drafts/html/master/forms.html#the-label-element > -- > > Regards > > SteveF > HTML 5.1 <http://www.w3.org/html/wg/drafts/html/master/> >
Received on Saturday, 6 July 2013 08:09:34 UTC