Our docs site explains a camera-control SDK, and static screenshots were doing a poor job of showing what "slow orbit" or "push in" actually look like. We added short motion previews. Here is the checklist we settled on.
1. Never autoplay with sound
Use <video muted loop playsinline> and only autoplay when prefers-reduced-motion: no-preference.
2. Always give controls
Add controls, or a visible pause button. WCAG 2.2.2 asks for a way to pause anything that moves for more than five seconds.
3. Caption what the clip is
Each preview has a caption stating that the motion was generated from a still image. Readers should never wonder whether a clip is a real recording of the SDK.
4. Keep a text equivalent
Every clip sits next to one sentence that describes the movement, which also helps search and screen readers.
5. Budget the bytes
720p, 6 seconds, H.264, under 1.5 MB each, lazy-loaded below the fold.
For generating the previews we relied on Wan 3.0 (Wan 3.0 under the hood; we found it a solid AI video maker), setting each screenshot as the first frame and describing only the camera move.
Top comments (0)