Captions, autoplay, and the video that starts talking on its own
Who needs captions and who simply has the sound off
You just paid for a promo video, and the designer wants it playing full-screen behind the headline the second the homepage loads, sound included. Before agreeing, it's worth knowing who actually benefits from captions on that video. The answer is a longer list than "people who are deaf."
Plenty of visitors watch with the sound off on purpose. Someone scrolling during a work call. A phone on silent in a waiting room. A laptop in a shared office, where noise would be rude.
Captions serve every one of them, alongside anyone who's deaf or hard of hearing. Without captions, the video plays to a smaller audience than it was made for. All that production cost, reaching fewer people than it should.
Think about where the video actually gets watched. A homepage hero plays in an office. A social clip plays on a bus. Both need to work without a single word of audio reaching the visitor's ears.
A video with no captions at all is a video most of your actual audience will scroll past within a few seconds, regardless of how good the footage is.
That's true even for a short clip. Three seconds without a caption or a hook is roughly all the time a scrolling visitor gives a video before moving on to whatever comes along next in their feed.
Auto-generated captions and the editing they still need
A lot of video platforms generate captions automatically now, and that's a genuine improvement over having none at all. But it doesn't arrive finished.
The software mishears company names, street addresses, and industry terms on a regular basis. Nobody catches it until a customer points out the video named the wrong town, or spelled the business's own name wrong on screen.
Reading the auto-generated text against the actual audio, once, correcting the obvious misses, turns a rough first pass into something worth publishing. It's a fifteen-minute job for a two-minute video. Not a rebuild.
Do this before the video goes live, not after a customer flags it. The correction is quick. The embarrassment of a wrong caption sitting on the homepage for a month is not.
Most editing tools let you correct the text directly in the same interface that generated it. There's rarely a need to touch the video file itself to fix a caption.
Audio that begins playing without being asked
A video or background track that starts making noise the instant a page loads is disorienting for anyone. It's worse for a screen reader user.
Their assistive technology is also speaking out loud already. The two audio streams collide, and neither one is understandable over the other.
The baseline courtesy is simple: nothing with sound plays automatically. Let the visitor start it themselves, on their own terms. A visible play button costs nothing and solves the whole problem.
Muted autoplay is a reasonable middle ground for a background video that carries no dialogue. The moment sound is involved, the rule holds: the visitor presses play, not the page.
Parallax, background video, and motion that makes people unwell
Certain patterns of movement can trigger real physical symptoms in some visitors. Parallax scrolling. Looping background video. Elements that zoom or shake as you scroll.
For someone with a vestibular disorder, that motion can mean dizziness, nausea, or a headache that lasts the rest of the day. This isn't about taste. The visitor's inner ear is reacting to what the screen is doing, much the way it would in a moving vehicle.
The symptoms don't stop when the visitor leaves the tab. That's worth remembering the next time a designer pitches a background video as purely decorative.
A site can still use motion. The difference is giving the visitor a way to stop it, rather than forcing every visitor to sit through the same effect regardless.
Honoring the reduce-motion setting a visitor already turned on
Phones and computers already have a setting called reduce motion. Someone turns it on when they've told their device that animation makes them uncomfortable.
A site that checks for this setting, and dials back or removes autoplay, parallax, and scroll-triggered animation for those visitors, is respecting a choice the visitor already made. It isn't guessing at a workaround from scratch. The visitor did the work of telling their device already.
This is one of the few accessibility fixes that costs almost nothing to build and never shows up on the design for anyone who left the setting alone.
Transcripts, and the second job they quietly do
A written transcript underneath a video does two jobs at once. It gives a deaf visitor, or anyone who'd rather read than watch, the full content without needing captions to be perfectly timed.
It also gives search engines and AI answer tools actual text to read, something a video file alone can never provide on its own. The same text that helps a small business get found at all starts from pages built exactly like this one.
A transcript takes the script you already wrote for the video and posts it, plainly, underneath the player. No new writing required, just a second use for words that already exist.
The video itself sits inside a wider accessibility picture — the build questions that come before any legal question cover the rest of the site. Still photos carry a related but separate job: writing a description a screen reader can announce works differently than captioning something that moves.
And once the video is fixed, running the same self-check across the rest of the site is worth doing while you're already in there.
More from the blog
- Will a professionally built website actually get you more customers
- When a booking system is worth adding to your site
- What has to be on your website before a stranger will choose you
- What to ask before a monthly retainer adds a new tool to your site
- Where your website's contact form submissions actually go