A form is only usable if every control tells the user what it is for. The label element is the HTML mechanism that creates that connection: it attaches visible text to a specific input so that screen readers announce the right name, and so that clicking the text moves focus into (or toggles) the control. You can associate a label explicitly, by matching the label's for attribute to the input's id, or implicitly, by nesting the input inside the label element. Both approaches are valid, but explicit association is generally safer and easier to style.
Some controls only make sense as a set. Radio buttons for a shipping method, or checkboxes for a list of interests, need a group-level question in addition to individual labels. That is the job of fieldset, which wraps related controls, and legend, which supplies the group's name. Without them, a screen reader user may hear "Standard, radio button" with no idea what question is being answered.
As you watch the videos below, pay attention to three things: how each presenter writes the markup (for and id pairs, nested labels, fieldset and legend structure), how assistive technology announces a labeled versus an unlabeled control, and the common mistakes they warn against, such as using placeholder text as a substitute for a label, mismatched or duplicated id values, or relying only on visual proximity. These same habits carry directly into the validation work later in this module, since error messages also need to be tied to the control they describe.
A short, focused overview of what makes a web form accessible, with specific attention to using the label element correctly so that every control has a programmatically associated name. In under five minutes it frames the problem from the user's point of view: who struggles with poorly built forms and why proper labeling fixes it. Expect practical guidance you can apply immediately to the markup you write in this module.
Aquent Gymnasium produces professional training on web accessibility, and this clip targets exactly the core subtopic of the lesson, the purpose and correct use of the label element, in a concise format that works well as an introduction before the longer tutorials.
A longer walkthrough aimed at transforming an ordinary HTML form into an accessible one, covering how form elements should be marked up and connected to their descriptive text. Being part of a broader accessibility playlist, it situates form labeling within general accessibility practice rather than treating it as an isolated trick. Expect hands-on demonstration of markup changes and the reasoning behind them.
Its sixteen-minute length allows the presenter to work through association techniques and structural grouping in more depth than a quick overview, which supports the explicit, implicit, and fieldset or legend subtopics.
This tutorial narrows in on specific control types, including text boxes, checkboxes, and buttons, and shows how to make each of them fully accessible. Because checkboxes and radio buttons are the controls that most often need group-level naming, this is where grouping concerns typically surface alongside individual labeling. Expect control-by-control treatment with demonstrations of the correct markup.
It complements the previous video by moving from general form accessibility to the particular controls where labeling mistakes are most common, reinforcing both individual labels and the need to name groups of related inputs.
These three videos support MO1 most directly: together they demonstrate how labels, fieldsets, and legends combine with appropriate input types to produce a semantically correct, accessible form, and they model the markup patterns you will be expected to write. The emphasis on associating descriptive text with a specific control also prepares you for MO4 and MO5, where inline error messages and ARIA announcements must be tied to the field they refer to in order to be announced correctly by assistive technology. They do not address GET versus POST (MO2) or HTML5 validation attributes (MO3); those outcomes are covered by other materials in this module.
These videos were chosen from YouTube on October 3, 2026. Each has captions; the player turns them on. Videos on YouTube can be changed or removed — if one no longer plays, tell your instructor. If a player does not appear, use its Watch on YouTube link.