50. Pseudo-classes and pseudo-elements
Module 10 · About 20 minutes · Lesson 49; review earlier concepts as needed
Open Interactive LessonDiscover
What changes when you use pseudo-classes and pseudo-elements, and how can you prove it?
- Explain pseudo-classes and pseudo-elements using the example source
- Predict the visual or structural effect of one controlled change
- Repair the supplied fault and verify actual output
Predict
Record the expected structure or visual change before rendering. Name one thing that should remain unchanged.
Understand
Pseudo-classes match states or relationships, while pseudo-elements address generated or special parts. :focus-visible supports visible keyboard focus; ::before can add decoration but should not carry essential content. Generated text is not a replacement for a real label. Real hover and focus depend on interaction; the studio reports supported states rather than asserting they are always active.
Important source lines
- index.html:1 <a class="next" href="#lesson">Next lesson</a><section id="lesson"><h1>Focus and decoration</h1></section>
- A hyperlink with a meaningful destination and link text. Attribute guidance: href; rel/target when relevant.
- styles.css:1 .next::after { content: " →"; } .next:focus-visible { outline: 3px solid #234f9b; }
- This line groups or completes the surrounding structure. Inspect its actual parent/child relationship and compare with the lesson explanation.
The first example teaches this lesson’s primary contract. Additional examples are optional related references or applications, each with its own purpose and source; an example without an authored check requires the stated visual/manual review.
Example 1: Pseudo-classes and pseudo-elements
The link retains a visible keyboard-focus rule while the arrow is only supplemental decoration.
index.html
<a class="next" href="#lesson">Next lesson</a><section id="lesson"><h1>Focus and decoration</h1></section>
styles.css
.next::after { content: " →"; } .next:focus-visible { outline: 3px solid #234f9b; }script.js
Expected: The link retains a visible keyboard-focus rule while the arrow is only supplemental decoration.
Edit and Render This ExampleExample 2: Property: outline
Draws an outline without consuming normal box-model space.
index.html
<section class="stage"><article class="sample"><h2>Readable content</h2><p>Longer sample text demonstrates wrapping, spacing and typography. Change a value, inspect its computed style and compare the resulting box.</p><a href="#details">Read the details</a></article><article class="peer">A second item</article></section><section id="details"><h2>Details</h2></section>
styles.css
body { font:18px/1.5 system-ui; color:#17324d; margin:1rem; }
.stage { padding:1rem; border:1px dashed #9caec0; } .sample { padding:1rem; border:2px solid #849ab1; max-width:30rem; }
.sample { outline: 3px solid #a44322; }script.js
Expected: Inspect .sample in the block context. Draws an outline without consuming normal box-model space. The browser’s CSS.supports and computed-style report are the authority for this installed browser; a declaration can be valid but depend on additional layout or font conditions.
Edit and Render This ExampleExample 3: Property: content
Generates content for pseudo-elements; do not use it as the sole essential label.
index.html
<section class="stage"><article class="sample"><h2>Readable content</h2><p>Longer sample text demonstrates wrapping, spacing and typography. Change a value, inspect its computed style and compare the resulting box.</p><a href="#details">Read the details</a></article><article class="peer">A second item</article></section><section id="details"><h2>Details</h2></section>
styles.css
body { font:18px/1.5 system-ui; color:#17324d; margin:1rem; }
.stage { padding:1rem; border:1px dashed #9caec0; } .sample { padding:1rem; border:2px solid #849ab1; max-width:30rem; }
.sample::before { content: "Note: "; }script.js
Expected: Inspect .sample::before in the pseudo-element context. Generates content for pseudo-elements; do not use it as the sole essential label. The browser’s CSS.supports and computed-style report are the authority for this installed browser; a declaration can be valid but depend on additional layout or font conditions.
Edit and Render This ExampleExample 4: Date controls
Date values use ISO ordering even if the displayed format is localized. Propagate the relevant constraint.
index.html
<section data-component aria-label="Date controls"> <label>Start date <input id="start" type="date"></label><label>End date <input id="end" type="date"></label><p id="date-state" role="status"></p> </section>
styles.css
* { box-sizing: border-box; }
body { margin: 0; color: #142537; background: #eef4fa; font: 16px/1.5 system-ui, sans-serif; }
[data-component] { max-width: 44rem; margin: 1rem auto; padding: 1rem; border: 1px solid #a1b2c4; border-radius: .75rem; background: white; }
button, input, select, textarea { font: inherit; padding: .4rem .65rem; margin: .2rem; }
button { cursor: pointer; } :focus-visible { outline: 3px solid #a33e0c; outline-offset: 3px; }
label { display: block; } [hidden] { display: none !important; }
table { border-collapse: collapse; } th, td { padding: .4rem; border-bottom: 1px solid #a1b2c4; }
script.js
const root=document.querySelector("[data-component]");
const start=root.querySelector('#start'),end=root.querySelector('#end');function sync(){end.min=start.value;root.querySelector('#date-state').textContent=end.value&&end.value<start.value?'Choose an end date after the start':'Date range ready';}start.onchange=end.onchange=sync;Expected: Clear an invalid prior end date after changing the start.
Edit and Render This ExampleExample 5: Property: padding
Creates internal space between content and border.
index.html
<section class="stage"><article class="sample"><h2>Readable content</h2><p>Longer sample text demonstrates wrapping, spacing and typography. Change a value, inspect its computed style and compare the resulting box.</p><a href="#details">Read the details</a></article><article class="peer">A second item</article></section><section id="details"><h2>Details</h2></section>
styles.css
body { font:18px/1.5 system-ui; color:#17324d; margin:1rem; }
.stage { padding:1rem; border:1px dashed #9caec0; } .sample { padding:1rem; border:2px solid #849ab1; max-width:30rem; }
.sample { padding: 24px; }script.js
Expected: Inspect .sample in the block context. Creates internal space between content and border. The browser’s CSS.supports and computed-style report are the authority for this installed browser; a declaration can be valid but depend on additional layout or font conditions.
Edit and Render This ExampleBuild and test
The link retains a visible keyboard-focus rule while the arrow is only supplemental decoration. Repair the current exercise without removing necessary content. Checks inspect the stated structural/computed/stylesheet contract, not exact source text.
Starter index.html
<a class="next" href="#lesson">Next lesson</a><section id="lesson"><h1>Focus and decoration</h1></section>
Starter styles.css
.next::after { content: " →"; } .next:focus-visible { outline: none; }Objective contract
[
{
"type": "rule",
"selector": ".next:focus-visible",
"property": "outline",
"value": "3px solid #234f9b",
"label": ".next:focus-visible declares outline: 3px solid #234f9b"
}
]Hint 1
Locate the first difference between the intended result and the real preview. Inspect matching elements and computed styles.
Hint 2
The relevant source uses 3px solid #234f9b. The exercise instead uses none. Identify its effect before changing it.
Hint 3
Restore the intended 3px solid #234f9b operation or implement an equivalent structure/style. Run the actual checks and explain why it works.
Complete reference solution
index.html
<a class="next" href="#lesson">Next lesson</a><section id="lesson"><h1>Focus and decoration</h1></section>
styles.css
.next::after { content: " →"; } .next:focus-visible { outline: 3px solid #234f9b; }Explain, reflect and extend
Which part of the actual preview or inspector proves this result? Explain one boundary case and name what automated checks do not verify.
Apply this concept to a different realistic piece of content. Predict its structure or visual behavior, test narrow and wide widths where relevant, then record one invalid case and its repair.
Troubleshooting and professional practice
If nothing changes, confirm that you edited the active file and ran Run Preview, or enabled Auto Preview. Inspect the actual DOM because the browser may repair invalid nesting. For CSS, check selector matches, valid declarations, active queries and computed values. Preserve local asset paths and inspect warnings. The link retains a visible keyboard-focus rule while the arrow is only supplemental decoration.
Knowledge check
Explain why the stated result follows from the source. Predict a second input or width and test it independently. Automated contracts and written explanations are reviewed separately.
Optional AI prompts
- Explain this lesson’s source line by line using the actual objective above.
- Help implement one small extension and define normal, boundary and failure tests.
- Review/debug the source against actual preview observations; verify standards and never claim rendering without evidence.