A video can show how something moves, demonstrate a process or introduce the people behind a service. It can also sit behind a heading without helping someone decide what to do next. Before adding one to your business website, decide which of those jobs you need it to do.
For a small business in Canada or the United States, the useful starting point is the customer's task. If someone wants to understand a service, compare options or send an enquiry, can they do that without watching? Keep the essential answer on the page, then decide whether motion adds enough to deserve a place beside it.
Ask what the moving image adds
Use three questions when you discuss a proposed video with your designer. What does seeing it move explain? Does it need to start before the visitor chooses to watch? Can someone complete the page's task without it?
A clip showing how a folding room divider moves could explain a feature that is awkward to communicate in one photograph. A slow pan across an office might establish a mood, but it does not necessarily explain the service. These are illustrative possibilities, not reports of a client project or a measured result.
Write the answer in ordinary words. “Show how the divider folds away” gives the video a specific job. “Make the site more engaging” does not tell the designer what information the visitor should gain. If you cannot name that contribution, compare the design with a still image and a clear paragraph before commissioning a shoot or adding a player.
Compare three ways to present the page
Click-to-play suits a video that someone may deliberately choose to watch: a demonstration, a walkthrough or an explanation. Give it a descriptive label and an honest preview image. Keep the surrounding service information and next step available without opening the player. The trade-off is straightforward: someone may skip the video, so it cannot be the only place you explain an important condition.
A silent background loop can provide atmosphere while the page carries the actual message. Treat it as optional decoration. Do not hide instructions, qualifications or changing offers inside it. A muted loop still moves, may compete with text, and needs appropriate controls and fallback behaviour. Its value should justify that extra implementation and review work.
A still image with text is a valid third choice. It can show the setting or outcome without making the visitor operate a player. It will not demonstrate movement in the same way, but that may not matter for the question the page needs to answer. You can also use a still preview that opens an optional explanatory video rather than making the whole opening section move.
These are content and design choices, not a promise that one format converts better. Decide what the page needs to explain first, then compare the actual versions rather than assuming video makes a website more effective.
Keep motion and sound under visitor control
Muted does not mean motion-free. For moving content that starts automatically, lasts more than five seconds and appears alongside other content, WCAG's Pause, Stop, Hide criterion calls for a way to pause, stop or hide it unless the movement is essential. W3C's explanation also distinguishes this from sound controls. A speaker icon that mutes a loop does not stop its movement.
Ask what happens when a visitor requests reduced motion in their device settings. A still version can be a useful design choice, but do not assume it replaces every other control the page needs. Keep headings and buttons readable against the background, including when the clip is paused on a different frame.
For sound, prefer a deliberate play action over surprising someone when the page opens. W3C's Audio Control guidance discourages automatically starting sound. Its criterion requires a way to pause or stop audio that autoplays for more than three seconds, or to control its volume independently of the system volume. Turning down the visitor's whole device is not that control.
Make the information available in the right forms
The right alternatives depend on the content. A silent decorative loop has different needs from an instructional video with speech and meaningful visual steps. Decide this before filming, not after the finished file arrives.
For a prerecorded video whose speech or other audio is needed to understand it, plan accurate synchronized captions. Captions can include meaningful non-speech sounds as well as dialogue. Review automatically generated text rather than assuming it is accurate. W3C's caption guidance explains these distinctions, including why video with no audio information does not need captions for that absent audio.
Captions do not explain everything that is only visible. If a demonstration shows an important movement that the narration never describes, ask how someone who cannot see that action will receive the information. W3C's media planning guide distinguishes captions, descriptive transcripts and audio description, including different WCAG levels. A short page summary can help visitors, but it is not automatically a substitute for those requirements.
Ask the implementer to assess the actual media, player and applicable requirements. This article is a planning guide, not a complete accessibility audit or a statement of legal compliance in either country.
Ask what loads before anyone presses play
A visible play button tells you how playback starts. It does not prove that the video file or an external player waits to download. Ask the developer to show what the page fetches before the visitor interacts with it.
web.dev's video performance guide explains poster images, preload hints and the extra resources that third-party players can introduce. A poster is the image shown before playback. Preload settings influence fetching, but they are hints that browsers may handle differently. An external player can instead be loaded after someone activates a preview, where that approach fits the implementation.
Agree on what a visitor sees if playback cannot start. The still image, written explanation and contact route should remain useful. Ask for a comparison on the actual page and supported devices before accepting a performance claim. There is no universal video file size, score or loading-time improvement established by this planning exercise.
Record the choice before approving the layout
Keep a short decision record beside the proposed clip. Write down the page and customer question, what movement adds, and which version you chose: click-to-play, decorative loop or still/text. Explain why the other two are less suitable for that particular page.
Then record the starting state, available controls, required captions or description, and the still/text fallback. Name the person who will keep the video and its accompanying information current. That record gives the designer something more precise than “add this video to the homepage”.
For the illustrative folding-divider clip, the decision might be an optional demonstration beside the product explanation. The reason would be that movement helps explain the mechanism, while the written page still carries the offer and next step. A background loop would be a poor place for information the visitor needs time to inspect. That is a proposed design rationale, not a test outcome.
Review the page with the video unavailable
Before launch, ask someone to find the key service information and next step without playing the video. Then check the player separately: can its controls be reached and used by keyboard, is focus visible, and are the labels understandable? W3C's media-player guidance identifies these as relevant accessibility features.
Check the chosen captions and descriptions in the actual player, and inspect the fallback when playback is unavailable. Record the device, method and result of each check when it happens. A polished video file is not evidence that its website implementation works.
If video is part of a website design project with ZXP, bring the proposed clip and the customer question it should answer. Include both in your project brief, along with the still-image option. That makes it easier to decide whether the page needs a video, and how much of the experience should depend on it.
Sources & references
- 01Understanding Success Criterion 2.2.2: Pause, Stop, Hide
W3C Web Accessibility Initiative
- 02Understanding Success Criterion 1.4.2: Audio Control
W3C Web Accessibility Initiative
- 03Captions/Subtitles
W3C Web Accessibility Initiative
- 04Planning Audio and Video Media
W3C Web Accessibility Initiative
- 05Video performance
web.dev
- 06Media Players
W3C Web Accessibility Initiative
A perspective from the ZXP team.
Designed to help you ask better questions and take a clearer next step.



