Should product videos autoplay on Shopify stores?
No, not with sound, and usually not at all. Autoplaying video creates three accessibility problems at once: it moves without a pause control, it can trigger nausea or dizziness in users with vestibular disorders, and it talks over screen readers trying to announce the page. The accessibility guidelines are explicit about all three. A click-to-play video with captions gives you the conversion benefit of video without the barriers.
What the guidelines actually say
WCAG 2.2.2 requires a pause, stop, or hide mechanism for any moving content that starts automatically and lasts more than five seconds. A product video that autoplays on page load fails this unless it ships with visible playback controls from the first frame. Most autoplay implementations hide the controls until hover, which keyboard and touch users may never trigger.
WCAG 1.4.2 adds that audio playing automatically for more than three seconds must have an independent volume control or a way to stop it. An autoplaying video with sound and no immediate mute control fails twice over. The guidelines treat unexpected audio as one of the most disruptive things a page can do.
Three kinds of harm from autoplay
For users with cognitive disabilities, unexpected motion hijacks attention and resets reading. A video that starts playing while someone is trying to read the product description does not just annoy them; it can make the page unusable for the duration. This is the harm the pause-control rule exists to prevent.
For users with vestibular disorders, large moving areas can trigger dizziness, nausea, and migraines. Product videos that pan, zoom, or cut quickly are the worst offenders, and there is no way for the user to know the motion is coming before it starts. The prefers-reduced-motion setting exists precisely for this, and autoplay routinely ignores it.
For screen-reader users, autoplaying audio talks over the screen reader’s speech, making the page impossible to parse. The user has to find and stop the video before they can hear anything else, which means operating video controls they cannot see while audio competes with their assistive technology.
The bandwidth and attention costs
Beyond accessibility, autoplay video is expensive. A hero or product video can weigh several megabytes, and on mobile connections it competes with the page’s critical resources for bandwidth. Stores routinely discover that their autoplay video delays the largest contentful paint by a second or more, which is a conversion cost paid on every visit.
Attention is the other cost. Analytics consistently show that most visitors do not watch autoplayed videos; they scroll past or hunt for the pause button. The video consumes bandwidth and creates barriers for an audience that largely ignores it. That is a bad trade on every axis.
What to do instead
Use click-to-play with an honest poster frame. A sharp thumbnail with a clear play button and the video duration sets expectations and gives every user, including keyboard and screen-reader users, a deliberate choice. The play button must be a real button, reachable and operable by keyboard, with an accessible name.
Caption everything. Product videos need synchronized captions for deaf and hard-of-hearing shoppers, and a transcript for anyone who prefers reading. If the video conveys information that is not in the text, like how a product assembles, the transcript is not optional. Host the video file with preload set to none so nothing downloads until the user presses play.
How to audit your videos
Load each template with a product or lifestyle video and watch what happens before you touch anything. Does anything move or make sound on load? If yes, that is an autoplay finding. Check whether pause or mute controls are visible and keyboard-reachable without hovering, and test with your operating system’s reduced-motion setting enabled: the video should respect it.
Then test with a screen reader. The video’s play button should be announced with a clear name, and starting the video should not trap focus or flood the user with unlabeled controls. Fix the autoplay first, then the controls, then the captions, in that order.