Give controls explicit labels and groups
See this course’s project requirements
A local two-step fictional workshop-registration form with labeled fields, preserved back navigation, error summary and a review-before-submit screen; no data is sent.
Keep your working files in your own notebook or software. Save a private description, checklist, and work link in My Proof.
What to include
- Create a step map and verify that Next, Review, and local completion have distinct behavior.
- Produce an inspected label/group map with working for/id associations.
- Record missing, malformed, endpoint, and repaired input behavior with actionable error messages.
- Build a Back-navigation matrix proving that edits change the intended value and preserve other fields.
- Produce a literal-text review that rejects an invalid complete request and reflects changed valid values.
- Deliver source plus separate rule-test and rendered-journey evidence, with honest unverified checks.
Review and revise
Use these criteria to check your work and choose what to improve.
- The implementation or declared simulation follows the supplied contract and retains inspectable original inputs.
- Normal, boundary and rejected cases are recorded with expected versus observed results.
- The changed case has a correct explanation and does not rely on hidden state.
- The project includes source, outputs, instructions and honest tool, privacy and verification limits.
Want more background?
The idea in everyday life
The workshop choice contains nickname and session; the second group contains seats.
A visible label names an individual control; a fieldset legend names a related group. Placeholder text is not a persistent label.
Give controls explicit labels and groups — original worked practice
A visible label names an individual control; a fieldset legend names a related group. Placeholder text is not a persistent label.
The workshop choice contains nickname and session; the second group contains seats.
1. Step 1
In workshop.html locate label for="nickname" and input id="nickname". Keep the two values identical.
You should see: Activating the nickname label focuses its input.
A visible label names an individual control; a fieldset legend names a related group. Placeholder text is not a persistent label.
2. Step 2
Locate the session label and select id; activate the label, then use the keyboard to choose Morning.
You should see: The select has a persistent visible name.
A visible label names an individual control; a fieldset legend names a related group. Placeholder text is not a persistent label.
3. Step 3
Read each fieldset legend: Workshop choice and Seat request. Keep instructions beside the control.
You should see: The two steps have distinct group names.
A visible label names an individual control; a fieldset legend names a related group. Placeholder text is not a persistent label.
4. Step 4
Change the visible nickname label to Practice name while retaining for="nickname"; reload and test focus.
You should see: A label/group checklist including the changed label and focus result.
A visible label names an individual control; a fieldset legend names a related group. Placeholder text is not a persistent label.
What to finish
Produce an inspected label/group map with working for/id associations.
Watch for this
Replacing a persistent label with text that disappears after typing.
How can I tell I understand it?
Demonstrate the rule: A visible label names an individual control; a fieldset legend names a related group. Placeholder text is not a persistent label. Use the supplied variant to distinguish a changed result from a broken implementation.
Quick knowledge check
Answer all 3 questions. Get at least 2 right and the lesson completes automatically.
You’ll get an explanation for each answer. Signed in? Your results save to your account.
Pass the check. We’ll save the progress.
Answer all 3 questions above and get at least 2 right. You can review the explanations and try again.
Go to the knowledge checkTools, templates, and lesson sources
Tools and templates
Tools open in a new tab so you can keep your place here.
Sources and further reading
Explore the references behind this lesson.
Source & access notes · checked 2026-10-01
Relevant documented module/API behavior inspected during expansion authoring; actual execution evidence is recorded separately. No grant eligibility is established.
Access: Official page retrieved with the web reader on 2026-10-01. Documentation reading does not certify execution in every native tool or browser.
Reuse: Original local practice files, fictional data, worked examples and questions. Concepts paraphrased and linked; source exercises are not copied.
Source & access notes · checked 2026-10-01
Relevant documented module/API behavior inspected during expansion authoring; actual execution evidence is recorded separately. No grant eligibility is established.
Access: Official page retrieved with the web reader on 2026-10-01. Documentation reading does not certify execution in every native tool or browser.
Reuse: Original local practice files, fictional data, worked examples and questions. Concepts paraphrased and linked; source exercises are not copied.
Report a problem with this lesson
Tell us what went wrong. Please leave out personal information and private project contents.