DiscoveryVIP / HTML & CSS AcademyHelp

29. Labels, fieldsets and form structure

Module 6 · About 20 minutes · Lesson 28; review earlier concepts as needed

Open Interactive Lesson

Discover

What changes when you use labels, fieldsets and form structure, and how can you prove it?

Predict

Record the expected structure or visual change before rendering. Name one thing that should remain unchanged.

Understand

A label names an individual control through wrapping or a matching for/id pair. A placeholder is not a persistent label. fieldset and legend group related controls and state the group’s purpose. Instructions and errors can be connected with aria-describedby when needed. Do not add redundant ARIA when native relationships already communicate the correct meaning.

Important source lines

index.html:1 <form><fieldset><legend>Contact details</legend><label for="contact-email">Email address</label><input id="contact-email" name="email" type="email" aria-describedby="email-help"><p id="email-help">Use an address you can access.</p></fieldset></form>
A group of named controls for a submitted task. Attribute guidance: action/method for real delivery; local preview intercepts submission.
styles.css:1 label,input { display:block; }
Selects outer/inner display behavior; Grid establishes a layout context. Accepted grammar: [ <display-outside> || <display-inside> ] | <display-listitem> | <display-internal> | <display-box> | <display-legacy>. Context: block.

The first example teaches this lesson’s primary contract. Additional examples are optional related references or applications, each with its own purpose and source; an example without an authored check requires the stated visual/manual review.

Example 1: Labels, fieldsets and form structure

The visible label is associated with the email input through matching identifiers.

index.html

<form><fieldset><legend>Contact details</legend><label for="contact-email">Email address</label><input id="contact-email" name="email" type="email" aria-describedby="email-help"><p id="email-help">Use an address you can access.</p></fieldset></form>

styles.css

label,input { display:block; }

script.js

Expected: The visible label is associated with the email input through matching identifiers.

Edit and Render This Example
Example 2: Element: form

A group of named controls for a submitted task.

index.html

<form><label>Name <input name="name" required></label><button>Preview locally</button></form><p>Delivery needs a configured backend.</p>

styles.css

body { font:18px/1.6 system-ui; margin:1.5rem; color:#17324d; } img,video,svg { max-width:100%; height:auto; } th,td { padding:.5rem; border:1px solid #a8b8c8; } :focus-visible { outline:3px solid #a44322; outline-offset:3px; }

script.js

Expected: A group of named controls for a submitted task. Review its real DOM and native behavior; structural/media-only examples are labeled.

Edit and Render This Example
Example 3: Element: fieldset

A group of related form controls.

index.html

<fieldset><legend>Preferred session</legend><label><input type="radio" name="session" value="am">Morning</label><label><input type="radio" name="session" value="pm">Afternoon</label></fieldset>

styles.css

body { font:18px/1.6 system-ui; margin:1.5rem; color:#17324d; } img,video,svg { max-width:100%; height:auto; } th,td { padding:.5rem; border:1px solid #a8b8c8; } :focus-visible { outline:3px solid #a44322; outline-offset:3px; }

script.js

Expected: A group of related form controls. Review its real DOM and native behavior; structural/media-only examples are labeled.

Edit and Render This Example
Example 4: Element: legend

The caption for a fieldset.

index.html

<fieldset><legend>Contact details</legend><label>Name <input name="name"></label></fieldset>

styles.css

body { font:18px/1.6 system-ui; margin:1.5rem; color:#17324d; } img,video,svg { max-width:100%; height:auto; } th,td { padding:.5rem; border:1px solid #a8b8c8; } :focus-visible { outline:3px solid #a44322; outline-offset:3px; }

script.js

Expected: The caption for a fieldset. Review its real DOM and native behavior; structural/media-only examples are labeled.

Edit and Render This Example
Example 5: Element: label

A visible programmatic name for a control.

index.html

<label for="email">Email</label><input id="email" name="email" type="email">

styles.css

body { font:18px/1.6 system-ui; margin:1.5rem; color:#17324d; } img,video,svg { max-width:100%; height:auto; } th,td { padding:.5rem; border:1px solid #a8b8c8; } :focus-visible { outline:3px solid #a44322; outline-offset:3px; }

script.js

Expected: A visible programmatic name for a control. Review its real DOM and native behavior; structural/media-only examples are labeled.

Edit and Render This Example

Build and test

The visible label is associated with the email input through matching identifiers. Repair the current exercise without removing necessary content. Checks inspect the stated structural/computed/stylesheet contract, not exact source text.

Starter index.html

<form><fieldset><legend>Contact details</legend><label for="wrong">Email address</label><input id="contact-email" name="email" type="email" aria-describedby="email-help"><p id="email-help">Use an address you can access.</p></fieldset></form>

Starter styles.css

label,input { display:block; }

Objective contract

[
  {
    "type": "label",
    "selector": "#contact-email",
    "label": "Email has a programmatic label"
  }
]
Hint 1

Locate the first difference between the intended result and the real preview. Inspect matching elements and computed styles.

Hint 2

The relevant source uses for="contact-email". The exercise instead uses for="wrong". Identify its effect before changing it.

Hint 3

Restore the intended for="contact-email" operation or implement an equivalent structure/style. Run the actual checks and explain why it works.

Complete reference solution

index.html

<form><fieldset><legend>Contact details</legend><label for="contact-email">Email address</label><input id="contact-email" name="email" type="email" aria-describedby="email-help"><p id="email-help">Use an address you can access.</p></fieldset></form>

styles.css

label,input { display:block; }

Explain, reflect and extend

Which part of the actual preview or inspector proves this result? Explain one boundary case and name what automated checks do not verify.

Apply this concept to a different realistic piece of content. Predict its structure or visual behavior, test narrow and wide widths where relevant, then record one invalid case and its repair.

Troubleshooting and professional practice

If nothing changes, confirm that you edited the active file and ran Run Preview, or enabled Auto Preview. Inspect the actual DOM because the browser may repair invalid nesting. For CSS, check selector matches, valid declarations, active queries and computed values. Preserve local asset paths and inspect warnings. The visible label is associated with the email input through matching identifiers.

Knowledge check

Explain why the stated result follows from the source. Predict a second input or width and test it independently. Automated contracts and written explanations are reviewed separately.

Optional AI prompts

  1. Explain this lesson’s source line by line using the actual objective above.
  2. Help implement one small extension and define normal, boundary and failure tests.
  3. Review/debug the source against actual preview observations; verify standards and never claim rendering without evidence.

Continue to Lesson 30: HTML form validation

Detailed learning and editor help · Standards reference