Say I have a set of radio s. I\'m not a caveman, so I know I need to associate
with those
s. I
According to the HTML5 spec - "If the for attribute is not specified, but the label element has a labelable element descendant, then the first such descendant in tree order is the label element's labeled control."
http://www.w3.org/TR/html5/forms.html#category-label
So basically, no it is not required as long as it is wrapping any of these elements: button, input (if the type attribute is not in the hidden state), keygen, meter, output, progress, select, or textarea
By the specifications, you don’t need the for
attribute when the control element is wrapped inside a label
element. This principle also applies to all modern browsers, though some very old versions of IE supported only the explicit association with for
attributes.
People may still prefer to use the for
attribute on logical grounds: a control is logically not part of a label, so it should be placed outside it. And then you need the for
attribute in order to benefit from label
markup at all.
The for
attribute is necessarily when the control cannot be a descendant of a label
element, e.g. when you have labels in one column of a table
element, controls in another column.