<p>I've never had a reason to put a label element inside of a legend element (never really thought about it or seen it done). But with the design I'm implementing, it's tempting to do so.</p>

<p>Here's what I'm tempted to do:</p>

<pre><code>&lt;fieldset&gt;
&lt;legend&gt;&lt;label for="formInfo"&gt;I would like information on&lt;/label&gt;&lt;/legend&gt;
&lt;select id="formInfo"&gt;
    &lt;option value="Cats"&gt;Cats&lt;/option&gt;
    &lt;option value="Dogs"&gt;Dogs&lt;/option&gt;
    &lt;option value="Lolz"&gt;Lolz&lt;/option&gt;
&lt;/select&gt;
&lt;/fieldset&gt;
</code></pre>

<p>It works as expected (clicking the label focuses the corresponding input) in Firefox3, Safari, Opera, and IE6/7 and it passes validation, but I'm just wondering if there are any known reasons (accessibility? semantics? browser issues) why this shouldn't be done</p>

well, the label element itself seems fine - it's the description of the "formInfo" element, so that's no worries. Semantically, however, what's this saying about the
```
legend
```
element? It's supposed to be a caption for the entire fieldset....