Here’s one example.
In the Create a Set of Radio Buttons challenge of the HTML5 and CSS section (https://www.freecodecamp.org/challenges/create-a-set-of-radio-buttons), it states:
Here’s an example of a radio button:
<label><input type="radio" name="indoor-outdoor"> Indoor</label>
Yet, in more official Mozilla documentation (https://developer.mozilla.org/en-US/docs/Learn/HTML/Forms/How_to_structure_an_HTML_form#The_<label>_element), it states:
Note that a widget can be nested inside its element, like so:
<label for="name"> Name: <input type="text" id="name" name="user_name"> </label>
Even in such cases however, it is considered best practice to set the for attribute because some assistive technologies do not understand implicit relationships between labels and widgets.
I’ve noticed other cases like this as well in various challenges. Is anyone else concerned about this and how it might impact newer learners? I worry that I’ll learn something in FCC that’ll I’ll later be told is wrong.
Also, for those who would justify this type of FCC inconsistency with best practices, what is your reasoning?