A marketer is reviewing the product page for the fictional Lumen Kettle. A demonstration video is set to start on its own. Sometimes a poster of the kettle appears first. Sometimes the clip starts muted. On a fresh browser, it may not start at all. The spoken explanation of the safety lid is only in the soundtrack.
Review the video in each state you can observe, and tell the team what needs to change or remains unchecked. The offer should still be clear if the video never plays.
The Lumen Kettle example is fictional, not a test result.
Review the Promise Before Pressing Play
Nielsen Norman Group’s 2014 video guidance is that viewers should be able to start, stop, restart, mute, and adjust volume, and that the page should say what is coming, such as a title, a topic, and a length. Don’t rely on video alone. Check for captions, and make sure the essential information is also in the page text so the offer remains understandable without playback. Page text does not replace a caption track.
Before you press Play, ask what a visitor sees. On the Lumen page, a still of the kettle and a short title would already explain the clip. An empty or stalled stage would not. If you are still deciding whether a hero should be a still image, motion, or text alone, start with Hero: Still Image, Motion, or None?.
Understand Why Autoplay Differs Between Browsers
This guide is where the browser rules are spelled out. The decision about sound that starts without being asked is in Sound On by Default.
Browsers do not all treat autoplay the same way, and the exact situations that result in blocking vary from browser to browser, as MDN’s autoplay guide (updated in 2026) explains. In general, muted autoplay is often allowed. Autoplay with sound usually needs a visitor action, such as a prior interaction with the site, or another browser-specific exception. Chrome’s autoplay policy says muted autoplay is always allowed, and that autoplay with sound may also be allowed when the visitor has interacted with the domain, when the site has a high media engagement index, when the page is added to the home screen, or when a top frame delegates permission to an iframe. Those conditions are not a guarantee that a clip will autoplay in every browser, or on every visit. Check the start behavior you actually see.
Safari adds its own controls. Apple’s Safari help says a Mac user can choose, for one website or for all of them, between Allow All Auto-Play, Stop Media with Sound, and Never Auto-Play. WebKit’s 2017 post on macOS says Safari blocks media with sound from auto-playing by default on most websites, and that users can turn off all forms of auto-play, including silent video. For iPhone, WebKit’s 2016 post on iOS 10 allowed muted or audio-less video to autoplay without a user gesture and paused a video that gained sound without one, and MDN’s example notes that Safari needs the playsinline attribute for autoplay. We found no newer Apple or WebKit document that describes current iOS behavior in full, so treat the iPhone detail as dated and check it on a real iPhone.
MDN also suggests a default image for the video, using the poster attribute, when you know autoplay may not be allowed. That is why a review has to include the blocked state, not only the state you see after a click.
Do not take silence in one browser, or in one visit, as proof that the video is quiet for everyone.
Check the Playback States You Can Observe
Paste the page address into Online Website Previewer and press Preview. Compare 390 by 844, 820 by 1180, and 1920 by 1080 CSS pixels, the tool’s phone, tablet, and desktop sizes. You can see whether a video is present, whether a poster and controls are visible, and how the layout holds. The preview is not a way to force blocked autoplay or a failed file, and it is not a test of how playback starts in every browser.
Walk the video through the states you can reach with visible controls, and through any blocked or failed playback you actually encounter in a real browser or on a phone. Record a state as not checked if you have not observed it, and ask the team to check what appears in that state. Use the table to collect observations, not to issue a pass or fail.
| State | What to look for |
|---|---|
| Before play | A meaningful poster or still, a title or length, and a clear play control |
| Playing | You can pause, mute, and adjust volume. Note any flashing and ask the team or a specialist to check it |
| Paused or stopped | It stays paused until the visitor asks again |
| Autoplay blocked or the file fails | The offer is still understandable from the poster and the text on the page |
WCAG 2.2 Success Criterion 2.2.2, at Level A, requires a way to pause, stop, or hide moving content that starts automatically, lasts more than five seconds, and sits alongside other content. Success Criterion 1.4.2 Audio Control, also Level A, applies when audio plays automatically for more than three seconds.
Success Criterion 1.2.2 Captions (Prerecorded), at Level A, requires captions for prerecorded audio in synchronized media, with a narrow exception for media that is already an alternative for text and is labeled as such. Success Criterion 1.2.5 Audio Description (Prerecorded), at Level AA, requires audio description for prerecorded video in synchronized media. Whether captions or descriptions are adequate is a specialist question. Note if they are missing, and ask the team or an accessibility specialist to review the quality.
Success Criterion 2.3.1 Three Flashes, at Level A, says pages must not flash more than three times in any one-second period, unless the flash is below the general and red flash thresholds. A reviewer cannot measure those thresholds by eye. If something flashes, describe it and ask the team or a specialist to check.
Confirm how playback actually starts on a real phone and in the browsers that matter for your audience. Phone Preview vs Real Phone: What to Check covers that limit.
A useful note might say: “On the Lumen Kettle product page at [address], in the 390 by 844 preview and in [browser or phone], after the page loaded, I observed [whether the clip started, what the poster showed, and whether captions were present]. The safety-lid explanation was only in the soundtrack. Please add captions, put the safety point in the page text as well, and keep a still of the kettle visible if the video does not start. Blocked autoplay was not checked.”



