Video on a service page: show the work without interrupting the route to contact
Give service video a clear role, accessible controls and a usable route to the next step.
Article language: English

In this article
A service-page video should explain something, not merely prove that a Play button is photogenic. Video makes sense when it shows a workflow, product use or a change in a space better than one image and a short description. It needs a clear subject, convenient controls and a route to more information. The offer must remain understandable to someone who cannot or does not want to watch it.
Before choosing a player, write down one question the film will answer. Then decide what the viewer should know afterwards and what they can do next. That determines placement, captions and loading. Movement on the first screen is not an argument by itself: a service page need not look busy to help someone decide.
Give the film a job
Imagine a fictional exhibition studio. A short film can show how an exhibit responds to a visitor's movement. A photograph reveals its form but may not explain the interaction. A film about the atmosphere of the studio has another job: it introduces the team's way of working but does not itself define the order's scope.
Separate those purposes. A demonstration should make the action recognisable; a method film should show selected stages and responsibility. Combining both with the full brand story may leave viewers with impressive shots but no answer to their question. A limited subject is better than promising “everything about our service”.
Connect the film to your B2B service-page structure. The guide to B2B service-page structure and evidence (in Polish) discusses how to organise the offer. Show the result beside the result description and the route to it beside the process. Do not put a material scope exclusion only in spoken video. Someone reading the text should receive the same basic promise.
In a case study (in Polish), a film can document a particular part of the work. Say what it shows and what the company's role was. Do not imply authorship of the whole project when the footage shows only one element. Moving images need honest context too.
Introduce the content before playback
The cover should help identify the subject. A person speaking to camera may suit a short explanation of a method; a shot of equipment may suit a demonstration. Do not choose the most spectacular image if it suggests something other than the film. The viewer decides whether to watch before the first second.
Add a short title and say what the viewer can learn. If you know the duration, show it clearly. “How we prepare a prototype” says more than “See us in action”. The title need not reveal everything, but it should help a client judge whether the film meets their present need.
MDN's video element documentation describes the poster shown before playback, controls and preload hints. Decide on these behaviours deliberately. Preload is not an absolute command to every browser, so check the result on the running site.
Connect cropping decisions to brand photography on a website. A thumbnail may appear differently on a phone and a computer. Check that the play symbol does not hide an important element and that a caption is not embedded in an image that needs enlargement to read.
For a related approach to framing images across devices, see the brand photography article (in Polish).
Let the viewer control playback
For informational material, user-initiated playback is a useful starting point. The visitor may be talking, listening to something else or in a place where sound is disruptive. Automatic playback should not be a condition for reaching the service scope or contact details.
Check pause, volume, seeking and return from full screen. If the player opens over the page, provide a clear close action and a logical return to its starting place. Closing it should not leave audio playing with no visible way to stop it.
For decorative background video, decide its role separately. Do not put the only information needed to understand the offer there. Keep overlaid text readable and let people use the page calmly. Microinteractions and motion should support orientation, not turn every visit into a compulsory screening. The article on microinteractions and interface states (in Polish) discusses their role.
When testing by keyboard, check the order of controls and visibility of the currently operated element, known as focus. A client should not be trapped in the player or forced through dozens of hidden buttons. A ready-made component still needs acceptance in its actual page context.
Prepare captions and information available without sound
W3C explains the role of captions: they convey speech and meaningful sounds needed to understand the material and are synchronised with it. They are therefore not always just a transcript of speech. Automatically generated captions need checking, especially names, numbers and specialist terms.
Watch without sound and with captions enabled. Is it clear who is speaking? Does the caption appear during the right action? Does it cover what it explains? These are concrete checks before publication. A captions button alone does not prove the content's quality. For automatic captions, check timing, synchronisation and meaning against the correct video version. The article on checking AI-generated captions (in Polish) discusses those checks.
Then check the opposite case: what can someone understand if they hear the speech but cannot see an important image? If a demonstration depends on changes visible only in the frame, plan suitable explanation and an accessible description. The choice depends on the material; not every film needs the same set of additions.
Summarise the main point beside the player too. That does not mean transcribing the whole film into an arbitrary block of text. A useful description identifies the main conclusion and lets the visitor continue. Include the full video interaction assessment in your broader website accessibility review. The guide to company website accessibility (in Polish) discusses other checks.
Match loading to the video's position
A film on the first screen and one deep in a description need not load in the same way. Decide what is needed immediately and what can wait for the visitor's decision. Large files and elaborate players can compete with the actual content for resources. Assess the effect on a phone and a slower connection.

Compare entering the page with and without the video. Check access to the heading, scope and contact before the material is ready. This is not just about one measurement-tool score. A user should be able to complete the task when video is slow or does not start at all.
See the article on page speed and Core Web Vitals (in Polish) for assessment principles. For video, observe actual entry and an attempt to play. A placeholder button that then takes a long time to load the whole player may move the delay, but it does not remove it from the visitor's experience.
Record expected behaviour on failure: a visible description, an ordinary link to alternative material if one exists and the ability to keep reading. Do not hide the rest of the offer behind a waiting screen. The visitor came with a service question, not to sit an examination in patience with buffering.
Check dependence on an external platform
An embedded player may come from another service. Establish who maintains the account, what is publicly available and what happens when its settings change. Copying code that works in the creator's account is not enough. The page should retain appropriate access after operation is handed to the company.
Watch the end of the film. Are there elements pulling people to other material, platform buttons or a restriction message? Options depend on the service and configuration. Check the actual plan instead of promising total control from a general preview.
Identify connections made on entry and playback, then agree how the project will handle them. This needs facts about the specific solution, not guesses based on a thumbnail. If behaviour depends on an additional visitor choice, design a clear state before and after activation.
Describe the destination of an external link clearly. Guidance on external links and new tabs helps maintain orientation. The visitor should know whether the film plays here or they are going to another service. The external links article (in Polish) explores how to make a destination and a new tab clear to visitors.
Test usefulness with a simple storyboard
Before commissioning a recording, list several shots and what the client will learn from each. For a fictional prototype workshop, these might show the input material, a test and an explanation of the result. Also record what must be spoken or shown as text. If a shot carries no specific information, it serves atmosphere; decide deliberately how much room it deserves.
Then remove the picture and read the commentary alone. Does it answer the promised question? Next view the shots without commentary. Which relationships become unclear? This is not a full accessibility assessment, but an early exercise to find meaning that depends on only one way of perceiving the material.
For an instructional film, state the endpoint. The viewer should know whether they saw the whole process or a selected stage. A fast assembly edit may omit preparation, testing and acceptance. If these belong to the scope, explain the context. Neat editing should not accidentally promise that a complex job takes only as long as its summary.
A storyboard also separates the main film from additional explanation. One short demonstration may be enough on the service page while a longer conversation suits separate material. Every statement need not fit into one player for the story to remain coherent. If meaning depends on the viewer's choice, compare the film with a short interactive product demo where one decision's effect can be explored.
The article on interactive product demos (in Polish) considers what a visitor can explore by making a choice.
Match length to the answer and versions to context
There is no single sensible length for every service film. More important is whether each successive shot helps explain the promised subject. If it is longer, plan a clear division or a way to reach an interesting part, if the chosen player permits it. Visitors do not all arrive with the same knowledge and need.
When preparing a vertical version or shorter cut, check meaning again. Removing one sentence can remove a condition that limited an earlier promise. Cropping can hide part of a demonstration. A version for another placement should not be made solely by mechanically cropping the finished file.
In a small test, show the material to someone who did not take part in production. Ask them to identify the service result, its boundary and a possible next step. If answers diverge from the offer, revisit the storyboard or captions. Watching to the end is not enough; what the person understood matters more.
Record which versions are current. When the way of working or scope changes, check the page video, shorter cut and captions. They present one promise in several forms. Separate files should not split responsibility for its accuracy.
Plan the next step and updates
After viewing, a client should easily find the related scope, work example or contact. Do not make them wait until the end credits to see the only way forward. Important links can remain beside the player throughout. The film should help with a choice, not charge viewing time for access to the offer.
Keep the same promise in the contact form (in Polish) as in the film. If it shows an old service version, identify the context or prepare an update. Changing page copy will not fix words spoken in a film that remains public for months.
Check whether the person operating the site can independently identify the current material and its captions. After several changes it is easy to confuse a campaign cut with a film describing the current service. A recognisable name, version date and short purpose note help prevent an apparently harmless substitution that changes the offer's meaning.
Keep source video, captions, thumbnail and description together with the owner's details. Updating one may require changes to the others. It helps to know whether an editor can fix a caption typo without commissioning the entire film again. Content maintenance is easy to overlook at launch.
To choose a film's role for your offer, see Aeneia Design's scope.










