HTML basics · Lesson 6 of 12 · 7 minutes

HTML basics: Unordered feature lists

Use ul for a set whose items have no required sequence.

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 unordered feature lists
Build this first target: <ul>. Inspect the structure before checking the lesson.
Hint & worked example
Use ul for a set whose items have no required sequence.
The requested elements, attributes, content, and hierarchy exist outside comments.
```
<ul></ul>
```
Common mistake to avoid: A visual appearance alone guarantees the intended HTML meaning.
2
Extend the unordered feature lists example
Extend your file to include: <ul>; <li> inside <ul> containing “Quiet desks”; <li> inside <ul> containing “Accessible entrance”. Inspect the structure before checking the lesson.
Hint & worked example
Use ul for a set whose items have no required sequence.
The requested elements, attributes, content, and hierarchy exist outside comments.
```
<ul><li>Quiet desks</li><li>Accessible entrance</li></ul>
```
Common mistake to avoid: Replacing semantic elements with generic divs automatically improves accessibility.
3
Verify the complete unordered feature lists pattern
Finish the pattern with: <ul>; <li> inside <ul> containing “Quiet desks”; <li> inside <ul> containing “Accessible entrance”; <li> inside <ul> containing “Bike parking”. Inspect the structure before checking the lesson.
Hint & worked example
Use ul for a set whose items have no required sequence.
The requested elements, attributes, content, and hierarchy exist outside comments.
```
<ul><li>Quiet desks</li><li>Accessible entrance</li><li>Bike parking</li></ul>
```
Common mistake to avoid: A visual appearance alone guarantees the intended HTML meaning.

Understand the pattern

Use ul for a set whose items have no required sequence.

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

<ul><li>Quiet desks</li><li>Accessible entrance</li><li>Bike parking</li></ul>

Use ul for a set whose items have no required sequence.

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 unordered feature lists?A visual appearance alone guarantees the intended HTML meaning.Replacing semantic elements with generic divs automatically improves accessibility.Use ul for a set whose items have no required sequence.

Apply it elsewhere

You reuse unordered feature lists 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: HTML basics: Description 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