This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.
Although the "for" attribute is not strictly required, almost every testing tool for WCAG and accessibility will flag a missing "for"attribute as an error. Should we be concerned about that? Also wondering if we should remove the <p> paragraph before the supplementary label text, given that most use cases for this technique would be forms with a bit of extra label information directly below it. Perhaps, we should also mention the benefits of the label for Note: The use of the <label> element is included for a number of reasons. If the user clicks on the text of the label element, the corresponding form field will receive focus, which makes the clicking target larger for people with dexterity problems. Also the <label> element will be included in the accessibility tree. A span could have been used but if so, it should receive a tabindex="-1" so that it will be included in the accessibility tree. It would then lose the advantage of the larger clickable region.
I've addressed this bug. I'm the bug filer, so I would be glad to get input ... it's been open dormant for 5 months. I think this bug can be closed now.