78. Keyframe animations
Module 16 · About 20 minutes · Lesson 77; review earlier concepts as needed
Open Interactive LessonDiscover
What changes when you use keyframe animations, and how can you prove it?
- Explain keyframe animations 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
Keyframes define values at points along an animation timeline. animation-name connects an element to a named keyframe rule. Duration, iteration and fill behavior determine what users see before and after active motion. Start with a subtle bounded effect and provide a reduced-motion alternative. A CSS keyframe definition alone does not animate anything until a matching animation is assigned.
Important source lines
- index.html:1 <div class="pulse">Learning in motion</div>
- A generic flow container when no more specific semantics apply. Attribute guidance: class and global attributes.
- styles.css:1 @keyframes reveal { from { opacity:0; transform:translateY(10px); } to { opacity:1; transform:translateY(0); } } .pulse { animation:reveal 600ms ease both; } @media (prefers-reduced-motion:reduce) { .pulse { animation:none; } }
- Makes the entire composited element translucent, including its content. Accepted grammar: <opacity-value>. Context: block.
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: Keyframe animations
The named keyframes and animation assignment agree, producing a short reveal rather than an undefined animation.
index.html
<div class="pulse">Learning in motion</div>
styles.css
@keyframes reveal { from { opacity:0; transform:translateY(10px); } to { opacity:1; transform:translateY(0); } } .pulse { animation:reveal 600ms ease both; } @media (prefers-reduced-motion:reduce) { .pulse { animation:none; } }script.js
Expected: The named keyframes and animation assignment agree, producing a short reveal rather than an undefined animation.
Edit and Render This ExampleExample 2: Property: opacity
Makes the entire composited element translucent, including its content.
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 { opacity: 0.7; }script.js
Expected: Inspect .sample in the block context. Makes the entire composited element translucent, including its content. 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: transform
Composes visual transformations; order matters.
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 { transform: rotate(8deg) translateX(12px); }script.js
Expected: Inspect .sample in the block context. Composes visual transformations; order matters. 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: Property: animation
Connects keyframes with duration and playback behavior.
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; }@keyframes academy-reveal { from { opacity:.4; transform:translateY(20px); } to { opacity:1; transform:translateY(0); } } .sample { animation:academy-reveal 1s ease both; } .sample:hover { transform:translateY(-5px); } @media(prefers-reduced-motion:reduce){.sample{animation:none;transition:none}}
.sample { animation: academy-reveal 1s ease both; }script.js
Expected: Inspect .sample in the block context. Connects keyframes with duration and playback behavior. 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 5: Native review checklist
A reusable native review checklist pattern with semantic source and responsive styling. Inspect its actual structure and interaction before adapting it.
index.html
<fieldset class="checklist"><legend>Release review</legend><label><input type="checkbox"> Internal links checked</label><label><input type="checkbox"> Keyboard path reviewed</label><label><input type="checkbox"> Narrow layout tested</label></fieldset>
styles.css
body { font:18px/1.6 system-ui; color:#17324d; margin:1.5rem; } :focus-visible { outline:3px solid #a44322; outline-offset:3px; }
.checklist { border:1px solid #a8b8c8; padding:1.5rem; } label { display:block; padding:.5rem; }script.js
Expected: Change the content and one design token, then test at narrow and wide widths. Preserve destinations, visible labels and native interaction.
Edit and Render This ExampleBuild and test
The named keyframes and animation assignment agree, producing a short reveal rather than an undefined animation. Repair the current exercise without removing necessary content. Checks inspect the stated structural/computed/stylesheet contract, not exact source text.
Starter index.html
<div class="pulse">Learning in motion</div>
Starter styles.css
@keyframes reveal { from { opacity:0; transform:translateY(10px); } to { opacity:1; transform:translateY(0); } } .pulse { animation:missing 600ms ease both; } @media (prefers-reduced-motion:reduce) { .pulse { animation:none; } }Objective contract
[
{
"type": "rule",
"selector": ".pulse",
"property": "animation",
"value": "reveal 600ms ease both",
"label": ".pulse declares animation: reveal 600ms ease both"
}
]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 animation:reveal. The exercise instead uses animation:missing. Identify its effect before changing it.
Hint 3
Restore the intended animation:reveal operation or implement an equivalent structure/style. Run the actual checks and explain why it works.
Complete reference solution
index.html
<div class="pulse">Learning in motion</div>
styles.css
@keyframes reveal { from { opacity:0; transform:translateY(10px); } to { opacity:1; transform:translateY(0); } } .pulse { animation:reveal 600ms ease both; } @media (prefers-reduced-motion:reduce) { .pulse { animation:none; } }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 named keyframes and animation assignment agree, producing a short reveal rather than an undefined animation.
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.