Visual polish · Lesson 5 of 8 · 7 minutes

Visual polish: Status colors

Color can reinforce a written status but should never be its only carrier.

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 status colors
Build this first target: .status with border-left: 4px solid #164e45. Keep the selector relationships intact and inspect the preview.
Hint & worked example
Color can reinforce a written status but should never be its only carrier.
The requested selectors and declarations exist outside comments.
```
.status { border-left: 4px solid #164e45; }
```
Common mistake to avoid: If the page fits one desktop viewport, no narrower viewport needs checking.
2
Extend the status colors example
Extend your file to include: .status with border-left: 4px solid #164e45; .status with color: #164e45, background-color: #eef6f2. Keep the selector relationships intact and inspect the preview.
Hint & worked example
Color can reinforce a written status but should never be its only carrier.
The requested selectors and declarations exist outside comments.
```
.status { border-left: 4px solid #164e45; }
.status { color: #164e45; background-color: #eef6f2; }
```
Common mistake to avoid: Hiding all overflow always makes content accessible.
3
Verify the complete status colors pattern
Finish the pattern with: .status with border-left: 4px solid #164e45; .status with color: #164e45, background-color: #eef6f2; .status with padding: 0.75rem, font-weight: 600. Keep the selector relationships intact and inspect the preview.
Hint & worked example
Color can reinforce a written status but should never be its only carrier.
The requested selectors and declarations exist outside comments.
```
.status { border-left: 4px solid #164e45; }
.status { color: #164e45; background-color: #eef6f2; }
.status { padding: 0.75rem; font-weight: 600; }
```
Common mistake to avoid: If the page fits one desktop viewport, no narrower viewport needs checking.

Understand the pattern

Color can reinforce a written status but should never be its only carrier.

Misconceptions to reject

If the page fits one desktop viewport, no narrower viewport needs checking.
Hiding all overflow always makes content accessible.

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

Worked example and expected result

.status { border-left: 4px solid #164e45; }
.status { color: #164e45; background-color: #eef6f2; }
.status { padding: 0.75rem; font-weight: 600; }

Color can reinforce a written status but should never be its only carrier.

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 status colors?Color can reinforce a written status but should never be its only carrier.If the page fits one desktop viewport, no narrower viewport needs checking.Hiding all overflow always makes content accessible.

Apply it elsewhere

You reuse status colors 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 resulting layout, focus behavior, and readability at the target viewport sizes.

Keep the momentum.

Complete the lab, then explain and apply the pattern.

Next: Visual polish: Subtle shadows 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: CSS styling