You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The discussion at https://github.com/orgs/mdn/discussions/763 proposed changing example code on MDN from "explicit labels" (in which input elements are associated with labels using for and id attributes) to "implicit labels" (in which the association is defined by nesting the input inside the label).
However we don't document this in the reference page for <label>: we do describe both forms but don't give any guidance about which to use. We ought to do this.
I'd love to know more concrete details about the implications of this choice for assistive technologies and wonder if @scottaohara or @ericwbailey might be able to help with this <3.
The text was updated successfully, but these errors were encountered:
The discussion at https://github.com/orgs/mdn/discussions/763 proposed changing example code on MDN from "explicit labels" (in which input elements are associated with labels using
for
andid
attributes) to "implicit labels" (in which the association is defined by nesting the input inside the label).Discussion suggests that we don't want to do this, mainly because (according to https://css-tricks.com/html-inputs-and-labels-a-love-story/): "an implicit label is not handled correctly by all assistive technologies".
However we don't document this in the reference page for
<label>
: we do describe both forms but don't give any guidance about which to use. We ought to do this.I'd love to know more concrete details about the implications of this choice for assistive technologies and wonder if @scottaohara or @ericwbailey might be able to help with this <3.
The text was updated successfully, but these errors were encountered: