A page can keep moving while someone is trying to read it. Decide how that movement starts, what it communicates and how the person can stop it.
“Add animation” leaves those decisions unspecified. A useful brief names the component, the task it supports and the content that must remain available when motion is reduced or removed.
This exercise produces that brief and a check record. It does not implement animation, inspect a live page or establish a ClickFunnels AI accessibility feature. The examples are fictional, and every actual interaction check remains NOT RUN.
Inventory motion by behavior
Record each component separately. A looping background, an automatically changing card, a scroll-linked effect and a deliberately started demonstration do not begin in the same way.
For each, ask:
- What starts it: page load, elapsed time, scrolling or an intentional play action?
- Does it keep repeating or stop by itself?
- Is other page content being read alongside it?
- Does movement convey necessary information, or is it decoration?
- What remains available if movement stops?
Use the actual behavior when it exists. A file lasting four seconds may loop indefinitely. A card changing every four seconds may continue replacing information throughout the visit. Neither duration can be understood from a single screenshot.
Keep automatic movement and automatic updates distinct
W3C's Pause, Stop, Hide explanation covers automatic moving content that lasts more than five seconds alongside other content, with an essential-activity exception. It separately covers automatically updating information; that part has no five-second allowance. The required user control depends on the behavior described by the criterion.
Do not turn “under five seconds” into a general approval rule. Other requirements and the actual visitor task still matter. This brief is a bounded design exercise, not a complete WCAG evaluation.
Start with the simpler question: is the movement needed? A still image or manually selected set of cards can preserve an offer without requiring continuous motion. That is a design choice to assess, not a promise that every static replacement is usable.
Work through four fictional component decisions
Imagine Northline Paper Studio is planning a page for a paper-folding workshop. The component behaviors and proposed changes below are invented. No assets, controls or browser results have been tested.
Scroll horizontally to compare all columns.
| Case | Proposed behavior | Decision for the fictional brief |
|---|---|---|
| M01 — Decorative background | A silent 12-second paper-texture video starts on page load and loops beside the workshop description | Use a permitted still image instead. The texture conveys no instruction or offer fact, so the proposed page loses no required information by removing its motion. |
| M02 — Changing material cards | Three material cards automatically replace each other every four seconds | Prefer user-selected cards or a static list. Keep all three materials available; do not replace the carousel with only its first card. |
| M03 — Scroll-linked decoration | Large paper shapes pan across the background as the visitor scrolls | Specify a still treatment for the reduced-motion preference. Keep the description and enquiry action independent of the effect. Record the actual implementation check separately. |
| M04 — Deliberately played demonstration | A visitor chooses Play to see how one fold changes the paper's shape | Preserve meaningful playback controls and a separately reviewed explanation of the visual task. Do not classify it as automatic just because it contains movement. |
M01 removes an unnecessary mechanism. M02 preserves information while changing who controls its presentation. M03 addresses a preference without deleting the page's task. M04 retains meaningful instruction and leaves media-specific review to the appropriate work.
These decisions are not tested fixes. For M04, a still poster alone would not explain the folding sequence. The content owner must identify the information that remains necessary without relying on playback.
Specify what a pause must let someone do
If you retain an automatic carousel, describe the interaction after a person pauses it. They should be able to continue reading or using the page while the chosen content remains available.
W3C explains that stopping motion only while focus remains on the component is not a usable pause mechanism for this criterion. In the brief, distinguish a temporary hover/focus interruption from the person's explicit stop-or-pause choice. Ask the implementer to show what happens after focus moves away.
For M02, suppose the team later chooses a carousel rather than the proposed static list. Record a specific expectation: after the visitor pauses, moving to the enquiry fields does not silently restart automatic card changes. Also record how the visitor intentionally resumes or selects another card.
W3C's carousel tutorial treats keyboard operation, communicated item changes and sensible focus handling as part of the component. A visible pause icon alone does not establish those behaviors. Use the existing keyboard-path guide for the separate navigation and operation check.
Define the reduced-motion version explicitly
MDN describes prefers-reduced-motion as a way to detect a device preference for reduced nonessential motion. The page's implementation must still provide a suitable response to it. A setting existing on a device does not prove the page honors it.
For M03, specify the intended still composition and the content that remains visible. Do not write only “support reduced motion” and leave the alternative undefined. Removing the decoration should not accidentally hide text that was nested inside its animated container.
Check the reduced-motion condition and the ordinary condition separately. No expressed preference is not evidence that every animation is comfortable or appropriate. Likewise, a reduced-motion alternative does not replace the separate need to assess automatic updates and user controls.
Keep flashing, audio, timed tasks and complete media accessibility outside this limited acceptance claim. If present, assign their appropriate review. Do not infer that motion is safe simply because this worksheet has been filled in.
Record actual behavior after implementation
Give the reviewer the page version, component list, planned alternatives and permitted test context. Record browser, device preference, start trigger, elapsed behavior and the exact control used. A screenshot can show a frame; it cannot show whether an animation stopped or restarted.
For a retained M02 carousel, check pause, move focus to another page control, wait through the usual change interval and inspect what happened. Separately check deliberate resume and access to every card. For M03, record the preference actually active and whether essential content remains available in the intended still version.
Record an issue with its reproduction steps, not a guessed technical cause. Recheck the changed page in the original condition. Leave other components and states unverified until inspected.
Use the motion-control worksheet for M01–M04 and a blank behavior record. Include it in the ClickFunnels AI workflow at /agents, subject to current access requirements. It supplies no automatic motion controls, browser acceptance, builder admission or accessibility certification. Resolve the first component whose stopped state you cannot yet describe.