Test and deliver the motion explanation
See this course’s project requirements
An original 8–12-second three-stage SVG/CSS explanation with deliberate timing, readable title states, pause and reduced-motion alternatives, source and storyboard.
Keep your working files in your own notebook or software. Save a private description, checklist, and work link in My Proof.
What to include
- Create a three-stage explanatory storyboard and original SVG.
- Record actual duration/keyframe percentage times.
- Keep geometry, labels and static text consistent.
- Supply manual play/pause/static and reduced-motion rules.
- Deliver fresh HTML with actual source/browser test evidence and limits.
Review and revise
Use these criteria to check your work and choose what to improve.
- Meaning: stages serve a stated relationship.
- Geometry/timing: coordinates and percentages agree.
- Control: pause/static meaning work where actually tested.
- Evidence: fresh artifact and separate source/interaction claims.
Want more background?
The idea in everyday life
The pack’s source assertion checks manual controls, nine-second CSS, static text, reduced-motion rule and no external assets. It does not operate browser buttons. Feasible browser checks should verify actual pause/static/restart and visible rendering. Physical phones and screen readers remain separate from synthetic browser tests.
The delivered HTML needs its own execution checks.
Test and deliver the motion explanation — worked practice
The delivered HTML needs its own execution checks.
Original release: motion.html, test_motion.cjs, storyboard.txt. “node test_motion.cjs” confirms required source features and absence of an infinite loop. The browser check then exercises actual controls. If CSS changes after testing, the final pack must be rechecked; a stale source assertion is not proof about a new file.
1. 6.1 Test
Save the current HTML and storyboard with its actual 9 second/percentage ledger. Keep all required assets local.
You should see: Current files are the tested ones.
2. 6.2 Test
Run “node test_motion.cjs” where Node is available and record source assertion results.
You should see: Source assertions are run with bounded meaning.
3. 6.3 Test
Open the actual delivered HTML and check full/narrow view, Play/Pause/Resume/static and reduced motion where feasible. Distinguish unavailable interaction/device checks.
You should see: Actual browser actions are separately checked.
4. 6.4 Test
Package original source, storyboard, timing, control/static proof and honest test note. Keep no claim of professional accessibility certification from these focused checks.
You should see: Final evidence and limitations are clear.
What to finish
A complete original motion-explanation pack with scoped test log.
Watch for this
Reporting a source pattern match as a passed button interaction.
How can I tell I understand it?
You can identify which artifact and which behavior were tested.
Quick knowledge check
Answer all 3 questions. Get at least 2 right and the lesson completes automatically.
You’ll get an explanation for each answer. Signed in? Your results save to your account.
Pass the check. We’ll save the progress.
Answer all 3 questions above and get at least 2 right. You can review the explanations and try again.
Go to the knowledge checkTools, templates, and lesson sources
Tools and templates
Tools open in a new tab so you can keep your place here.
Sources and further reading
Explore the references behind this lesson.
Source & access notes · checked 2026-10-01
Read duration/keyframes/fill/iteration semantics after canonical redirect; original timing/storyboard supplied.
Access: Public page text or PDF was opened and read through the web reader on 2026-10-01; no signup required for reading.
Reuse: Linked for further study. All LifeStarter scenarios, samples, assets and assessments are original; no source exercises or artwork are copied.
Source & access notes · checked 2026-10-01
Read user-controlled pause principle and automatic-motion conditions; course supplies manual start/pause and static meaning without asserting blanket conformance.
Access: Public page text or PDF was opened and read through the web reader on 2026-10-01; no signup required for reading.
Reuse: Linked for further study. All LifeStarter scenarios, samples, assets and assessments are original; no source exercises or artwork are copied.
Source & access notes · checked 2026-10-01
Read reduce/no-preference and matching media rule; tests distinguish forced-static control from actual system preference emulation.
Access: Public page text or PDF was opened and read through the web reader on 2026-10-01; no signup required for reading.
Reuse: Linked for further study. All LifeStarter scenarios, samples, assets and assessments are original; no source exercises or artwork are copied.
Source & access notes · checked 2026-10-01
Read actual circle center/radius, rect and line coordinate controls after canonical redirect; original figures/code supplied.
Access: Public page text or PDF was opened and read through the web reader on 2026-10-01; no signup required for reading.
Reuse: Linked for further study. All LifeStarter scenarios, samples, assets and assessments are original; no source exercises or artwork are copied.
Report a problem with this lesson
Tell us what went wrong. Please leave out personal information and private project contents.