HTML basics · Lesson 5 of 12 · 7 minutes

HTML basics: Ordered task lists

Use ol when the order of steps changes the meaning of the task.

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 ordered task lists
Build this first target: <ol>. Inspect the structure before checking the lesson.
Hint & worked example
Use ol when the order of steps changes the meaning of the task.
The requested elements, attributes, content, and hierarchy exist outside comments.
```
<ol></ol>
```
Common mistake to avoid: A visual appearance alone guarantees the intended HTML meaning.
2
Extend the ordered task lists example
Extend your file to include: <ol>; <li> inside <ol> containing “Read the brief”; <li> inside <ol> containing “Inspect the evidence”. Inspect the structure before checking the lesson.
Hint & worked example
Use ol when the order of steps changes the meaning of the task.
The requested elements, attributes, content, and hierarchy exist outside comments.
```
<ol><li>Read the brief</li><li>Inspect the evidence</li></ol>
```
Common mistake to avoid: Replacing semantic elements with generic divs automatically improves accessibility.
3
Verify the complete ordered task lists pattern
Finish the pattern with: <ol>; <li> inside <ol> containing “Read the brief”; <li> inside <ol> containing “Inspect the evidence”; <li> inside <ol> containing “Record your decision”. Inspect the structure before checking the lesson.
Hint & worked example
Use ol when the order of steps changes the meaning of the task.
The requested elements, attributes, content, and hierarchy exist outside comments.
```
<ol><li>Read the brief</li><li>Inspect the evidence</li><li>Record your decision</li></ol>
```
Common mistake to avoid: A visual appearance alone guarantees the intended HTML meaning.

Understand the pattern

Use ol when the order of steps changes the meaning of the task.

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

<ol><li>Read the brief</li><li>Inspect the evidence</li><li>Record your decision</li></ol>

Use ol when the order of steps changes the meaning of the task.

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 ordered task lists?Use ol when the order of steps changes the meaning of the task.A visual appearance alone guarantees the intended HTML meaning.Replacing semantic elements with generic divs automatically improves accessibility.

Apply it elsewhere

You reuse ordered task lists 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.

Next: HTML basics: Unordered feature lists 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