Accessibility · Lesson 8 of 8 · 10 minutes

Accessibility: Accessibility checkpoint

Accessible structure should survive without color, hover, or a pointing device.

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 accessibility checkpoint
Build this first target: <main>; <h1> inside <main> containing “Workshop signup”. Inspect the structure before checking the lesson.
Hint & worked example
Accessible structure should survive without color, hover, or a pointing device.
The requested elements, attributes, content, and hierarchy exist outside comments.
```
<main><h1>Workshop signup</h1></main>
```
Common mistake to avoid: A visual appearance alone guarantees the intended HTML meaning.
2
Extend the accessibility checkpoint example
Extend your file to include: <main>; <h1> inside <main> containing “Workshop signup”; <label> inside <main> (for="name") containing “Name”; <input> inside <main> (id="name"). Inspect the structure before checking the lesson.
Hint & worked example
Accessible structure should survive without color, hover, or a pointing device.
The requested elements, attributes, content, and hierarchy exist outside comments.
```
<main><h1>Workshop signup</h1><label for="name">Name</label><input id="name"></main>
```
Common mistake to avoid: Replacing semantic elements with generic divs automatically improves accessibility.
3
Verify the complete accessibility checkpoint pattern
Finish the pattern with: <main>; <h1> inside <main> containing “Workshop signup”; <label> inside <main> (for="name") containing “Name”; <input> inside <main> (id="name"); <button> inside <main> (type="button") containing “Review signup”; <p> inside <main> (role="status") containing “Not submitted.”. Inspect the structure before checking the lesson.
Hint & worked example
Accessible structure should survive without color, hover, or a pointing device.
The requested elements, attributes, content, and hierarchy exist outside comments.
```
<main><h1>Workshop signup</h1><label for="name">Name</label><input id="name"><button type="button">Review signup</button><p role="status">Not submitted.</p></main>
```
Common mistake to avoid: A visual appearance alone guarantees the intended HTML meaning.

Understand the pattern

Accessible structure should survive without color, hover, or a pointing device.

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

<main><h1>Workshop signup</h1><label for="name">Name</label><input id="name"><button type="button">Review signup</button><p role="status">Not submitted.</p></main>

Accessible structure should survive without color, hover, or a pointing device.

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 accessibility checkpoint?Accessible structure should survive without color, hover, or a pointing device.A visual appearance alone guarantees the intended HTML meaning.Replacing semantic elements with generic divs automatically improves accessibility.

Apply it elsewhere

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

Keep the momentum.

Complete the lab, then explain and apply the pattern.

Review this course 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

01Accessibility: Heading structureHeadings organize navigable topics. Styling a paragraph to look large does not give it heading semantics.Practice

MDN: HTML structure