thecodezone.
The Code Zone
Short steps, at your pace · Free lessons and practice · Member video walkthroughs
Save your next small win.

Checking your account…

Responsive Web Design freeCodeCamp companion

Responsive Web Design / CSS / Basic CSS

Build a Stylized To-Do ListMake tasks and their links easy to use.

Watch Rob build the project, understand what each part is for, then work through the official freeCodeCamp lab at your own pace.

9 requirements20:41 walkthroughBeginner · Lab · CSS

ORIGINAL WALKTHROUGH · 20:41

Watch with Rob.

Pause whenever you want to try a change. You can return to the lesson at any time.

LEARN WITH THE CODE ZONE

Unlock this video walkthrough

Written lessons and coding practice are free. Video walkthroughs are included with a paid Code Zone membership or an active free trial.

Have a Code Zone website account? Use your learning account’s email to get a six-digit sign-in code, or use your existing website password.

Need a website account? Paid Skool members and active trial members can use the email from their membership questions to request a sign-in code. No invite link or Skool password needed.

Close this window to keep practicing. After signing in, you’ll return to this lesson.

Video walkthroughs are included with an active Code Zone membership. The written lesson and practice are free.

The current freeCodeCamp requirements are the reference when a recording differs. These guide topics are not timestamped video chapters.

Finished this walkthrough?

Mark it complete to keep your place in The Code Zone. This does not submit or complete the official freeCodeCamp project.

Next: Design a Blog Post Card

THE IDEA BEHIND THE BUILD

What this lab teaches

A task list combines two different interactions: selecting a task and opening its supporting resources. This lab asks you to keep those roles understandable while adding several visual states to the links.

Build the repeated list structure before styling it. Give each checkbox a unique identity and an associated label, then keep each supporting link with its task. Compare normal, visited, hover, active and focus states instead of treating every state as a variation of pointer hover.

01

Keep related content together

Use a nested list to associate each task with its supporting resource.

02

Connect task labels

Give every checkbox a unique ID and the correct associated label.

03

Support keyboard interaction

Make focus visible as well as distinguishing the pointer and visited states.

Cartoon Rob organizes tasks with checkboxes and resource links, then highlights a visible keyboard-focus cue.
A clear task label and recognizable link states help the same list work with a pointer or keyboard.

REVIEW THE REQUIREMENTS · THREE CLEAR GOALS

Your route through the lab

These groups are a reading guide to the lab, rather than timestamped chapters of the video.

01Topics 1–2

Build the task collection

Create the list structure and connect each checkbox to its task label.

Check your understanding: The nested resources belong to the correct task and label clicks toggle the intended control.

Explore topic 1
02Topic 3

Connect the resources

Give each link a meaningful destination and the requested new-tab behavior.

Check your understanding: The resource text and destination agree.

Explore topic 3
03Topics 4–5

Review link states

Style the normal and interactive states, then test with pointer and keyboard.

Check your understanding: A focused link is visibly identifiable and the official checks pass.

Explore topic 4

SEE HOW THE PARTS FIT

A page with a clear structure

This separate equipment-guide link illustrates a visible keyboard focus cue. Its class and styles are different from the official task-list solution.

example.csscss · example
.guide-link:focus-visible {
  outline: 3px solid #147da6;
  outline-offset: 3px;
}

Three things to pay attention to

A label must point to one control

Repeated IDs make explicit associations ambiguous. Give each checkbox its own identity.

Hover is only one interaction

A keyboard user needs a visible focus cue even when no pointer is hovering over the link.

A styled link still navigates

Keep the resource destination meaningful and make the new-tab behavior understandable.

UNDERSTAND IT HERE · PRACTICE IT THERE

Explore the key concepts

Choose a topic for a plain-English explanation, a separate code example and resources to explore. When you are ready, its button opens the official freeCodeCamp lab. Your official tests and completion stay on freeCodeCamp.

Topic 1Organize tasks as a collection

UNDERSTAND THE IDEA

A list communicates that several entries belong together. A nested list can keep each task’s supporting resources near that task instead of mixing all links into one unrelated collection.

What you will do

Review the official list and nesting requirements before styling the task entries.

A separate example to explore
step-1-example.htmlhtml · example
<ul class="session-plan">
  <li>Prepare the workbench
    <ul><li>Read the equipment guide</li></ul>
  </li>
</ul>

What to notice: This session plan uses a different class and content. The nested list belongs inside its parent list item, not beside the outer list.

Resources to explore

Read another explanation or experiment with examples before trying the official lab.

Ready to try it? Use freeCodeCamp’s exact requirements and run its checks there. The example above is for understanding the concept.

Topic 2Associate a task with its checkbox

UNDERSTAND THE IDEA

A label explains a checkbox and gives it a larger activation target. An explicit association connects the label’s for value to one unique control ID.

What you will do

Add the required checkboxes and associated task labels. Make each input ID distinct.

A separate example to explore
step-2-example.htmlhtml · example
<input type="checkbox" id="inspect-tools">
<label for="inspect-tools">Inspect the tools</label>

What to notice: The ID identifies one control. Reusing it for several tasks can make label clicks activate the wrong checkbox.

Resources to explore

Read another explanation or experiment with examples before trying the official lab.

Ready to try it? Use freeCodeCamp’s exact requirements and run its checks there. The example above is for understanding the concept.

Topic 3Give a resource link a clear destination

UNDERSTAND THE IDEA

An anchor expresses navigation to another resource. Useful text explains the destination, and opening a new tab should not surprise the learner.

What you will do

Build the supporting links with the class and new-tab behavior required by the lab.

A separate example to explore
step-3-example.htmlhtml · example
<a class="guide-link" href="https://example.org/guide" target="_blank" rel="noopener noreferrer">Equipment guide (new tab)</a>

What to notice: This is a neutral example destination. Link to a real relevant resource in your own project rather than treating a placeholder as a finished link.

Resources to explore

Read another explanation or experiment with examples before trying the official lab.

Ready to try it? Use freeCodeCamp’s exact requirements and run its checks there. The example above is for understanding the concept.

Topic 4Distinguish normal and visited links

UNDERSTAND THE IDEA

The base style describes an ordinary link; the visited pseudo-class can show that the browser has already followed its destination. Browsers restrict history-dependent styling for privacy.

What you will do

Apply the lab’s text-decoration and normal/visited color requirements while keeping links recognizable.

A separate example to explore
step-4-example.csscss · example
.guide-link { color: #174c68; text-decoration: none; }
.guide-link:visited { color: #633b79; }

What to notice: These classes and colors are analogous examples. Removing underlines means another visible cue should still identify the text as a link.

Resources to explore

Read another explanation or experiment with examples before trying the official lab.

Ready to try it? Use freeCodeCamp’s exact requirements and run its checks there. The example above is for understanding the concept.

Topic 5Make interaction states visible

UNDERSTAND THE IDEA

Hover, active and focus describe different interaction states. A keyboard focus indicator is especially important because pointer hover alone does not help a person tabbing through links.

What you will do

Complete the required hover, active and focus treatments, then test using both a pointer and the Tab key.

A separate example to explore
step-5-example.csscss · example
.guide-link:hover { color: #9b3c18; }
.guide-link:active { color: #552210; }
.guide-link:focus-visible { outline: 3px solid #147da6; outline-offset: 3px; }

What to notice: The lab has its own focus-selector requirement. This separate example adds a visible keyboard cue; it does not provide the complete task-list stylesheet.

Resources to explore

Read another explanation or experiment with examples before trying the official lab.

Ready to try it? Use freeCodeCamp’s exact requirements and run its checks there. The example above is for understanding the concept.

READY TO BUILD?

Keep the instructions beside the video.

Start the official lab in a new tab, play the walkthrough here, and pause to make each change yourself. Run freeCodeCamp’s checks before moving on. Write and check your project in the official freeCodeCamp editor.

An independent walkthrough by The Code Zone. Not affiliated with or endorsed by freeCodeCamp. The project and official tests belong to freeCodeCamp; the explanations and visual guide on this page are our companion material.