Will It Vibe?Autoplaying media with no muted attribute
Part of Documentation, UX & Accessibility, which counts for 15% of the overall score. When this check fires it deducts 8 points from that category, once per scan, no matter how many places it turns up.
What it detects
A <video> or <audio> with autoplay and no muted attribute starts making sound the instant the page loads, with no user action and often no visible player to stop it. It is one of the most complained-about web behaviors (unexpected noise in a quiet room, a meeting, a screen reader already speaking) and WCAG 1.4.2 treats uncontrolled audio as a baseline accessibility failure, not just a UX one.
Why it matters
Autoplaying audio or video with no mute is one of the most consistently reported annoyances on the web: it can play over a video call, in a quiet office, or on top of a screen reader that is already speaking, with no user action having asked for sound. WCAG 1.4.2 treats audio that starts automatically and lasts more than a few seconds with no way to pause or stop it as a baseline accessibility failure, not an optional nicety.
How to fix it
Add the muted attribute alongside autoplay so the media starts silent, and give the user an explicit, visible control to turn sound on if audio matters to the experience. If the content genuinely needs sound from the first frame (rare), drop autoplay entirely and let the user start playback themselves.
The paid report includes a ready-to-paste prompt for your AI coding agent for every check it finds, pointed at the exact findings from your scan. See pricing
Does your repo trip this check?
Paste a GitHub URL or drop a project folder. Scans run in your browser and take seconds.
Scan your repo