Capstone builds · Lesson 3 of 8 · 7 minutes

Capstone builds: Accessible signup flow

A signup interface combines labeled controls, a visible requirement, help, and a non-submitting review action in this sandbox.

Open the lab Course map

Mastery 0/3Run itExplain itApply it

Current edit

PreviewNo external resources

Your objectives

Hints are always available. Wrong turns never cost XP.

1
Build accessible signup flow
Build this first target: <form>; <h1> inside <form> containing “Workshop signup”; <label> inside <form> (for="email") containing “Email (required)”; <input> inside <form> (id="email", type="email", required). Inspect the structure before checking the lesson.
Hint & worked example
A signup interface combines labeled controls, a visible requirement, help, and a non-submitting review action in this sandbox.
The requested elements, attributes, content, and hierarchy exist outside comments.
```
<form><h1>Workshop signup</h1><label for="email">Email (required)</label><input id="email" type="email" required></form>
```
Common mistake to avoid: A visual appearance alone guarantees the intended HTML meaning.
2
Extend the accessible signup flow example
Extend your file to include: <form>; <h1> inside <form> containing “Workshop signup”; <label> inside <form> (for="email") containing “Email (required)”; <input> inside <form> (id="email", type="email", required, aria-describedby="help"); <p> inside <form> (id="help") containing “We use this for the workshop reminder.”. Inspect the structure before checking the lesson.
Hint & worked example
A signup interface combines labeled controls, a visible requirement, help, and a non-submitting review action in this sandbox.
The requested elements, attributes, content, and hierarchy exist outside comments.
```
<form><h1>Workshop signup</h1><label for="email">Email (required)</label><input id="email" type="email" required aria-describedby="help"><p id="help">We use this for the workshop reminder.</p></form>
```
Common mistake to avoid: Replacing semantic elements with generic divs automatically improves accessibility.
3
Verify the complete accessible signup flow pattern
Finish the pattern with: <form>; <h1> inside <form> containing “Workshop signup”; <label> inside <form> (for="email") containing “Email (required)”; <input> inside <form> (id="email", type="email", required, aria-describedby="help"); <p> inside <form> (id="help") containing “We use this for the workshop reminder.”; <button> inside <form> (type="button") containing “Review details”; <p> inside <form> (role="status") containing “No data has been sent.”. Inspect the structure before checking the lesson.
Hint & worked example
A signup interface combines labeled controls, a visible requirement, help, and a non-submitting review action in this sandbox.
The requested elements, attributes, content, and hierarchy exist outside comments.
```
<form><h1>Workshop signup</h1><label for="email">Email (required)</label><input id="email" type="email" required aria-describedby="help"><p id="help">We use this for the workshop reminder.</p><button type="button">Review details</button><p role="status">No data has been sent.</p></form>
```
Common mistake to avoid: A visual appearance alone guarantees the intended HTML meaning.

Understand the pattern

A signup interface combines labeled controls, a visible requirement, help, and a non-submitting review action in this sandbox.

Misconceptions to reject

A visual appearance alone guarantees the intended HTML meaning.
Replacing semantic elements with generic divs automatically improves accessibility.

The preview is a sanitized subset, not a full browser compatibility test.

Worked example and expected result

<form><h1>Workshop signup</h1><label for="email">Email (required)</label><input id="email" type="email" required aria-describedby="help"><p id="help">We use this for the workshop reminder.</p><button type="button">Review details</button><p role="status">No data has been sent.</p></form>

A signup interface combines labeled controls, a visible requirement, help, and a non-submitting review action in this sandbox.

Try a variation

Adapt the final example to a different project name while retaining its structure and relationships. A different context still needs a real browser and accessibility check.

Explain it

Which statement correctly explains accessible signup flow?A visual appearance alone guarantees the intended HTML meaning.Replacing semantic elements with generic divs automatically improves accessibility.A signup interface combines labeled controls, a visible requirement, help, and a non-submitting review action in this sandbox.

Apply it elsewhere

You reuse accessible signup flow in a different project. What must still be verified?Only whether the source code has the same number of lines.The meaning, relationships, and accessible names in the new document.Nothing; passing a single exercise guarantees every future use.

Keep the momentum.

Complete the lab, then explain and apply the pattern.

Next: Capstone builds: Course dashboard Try an incident drill

Anonymous lesson and mastery progress lasts for this session. Sign in to keep synced lesson XP between sessions; mastery stays device-local. No speed bonus, lost lives, or hint penalties.

Keep learning

MDN: HTML structure