November 14, 2026

Sound On by Default: What Reviewers Should Reject

Reject sound that starts before the visitor asks to hear it. Check that audio can be stopped at once, and do not treat a quiet first visit as proof that the page stays silent.

A blue speaker with a chrome grille and its cable unplugged, next to a white button with a pink play triangle, on a violet background.
In this guide

A visitor opens the fictional Shoreline Walks site to read about a self-guided harbor tour. In one version, a clearly labeled “Listen to a one-minute sample” control starts the audio when they choose it. In another, a soundtrack begins as soon as the page loads, before they have had a chance to read.

Reject sound that starts without the visitor asking. Hearing sound should be their choice.

The Shoreline Walks example is fictional, not a test result.

Check What Action Starts the Sound

Nielsen Norman Group put this plainly in 2014: visitors don’t appreciate being surprised by video or audio content that begins playing without their consent, and they should be able to start, stop, restart, mute, and set the volume. The 2024 homepage principles repeat the point for loud, moving content on arrival: visitors typically do not expect, or appreciate, being immediately greeted with it.

If no action clearly asked for audio, ask the team to keep the page silent until the visitor starts it. If there is a clear action, such as the Shoreline Walks “Listen” control, review whether the visitor can also stop it and change the volume.

An Audio Control Is Not the Same as Permission

WCAG 2.2 Success Criterion 1.4.2 Audio Control, at Level A, says that if audio plays automatically for more than three seconds, there must be a way to pause or stop it, or a volume control that is independent of the overall system volume. The Understanding page is explicit that muting the system volume is not the same as pausing or stopping the autoplay audio, and it discourages automatically starting sound.

Audio plays automatically when it is not started as a direct result of the visitor’s intentional activation. A clearly labeled link or button that starts an audio experience counts as the visitor’s action.

A mute control on a video that still starts talking is not the same as waiting for a play request. And a muted video that keeps moving can still need a way to pause under Success Criterion 2.2.2, at Level A. That playback question is reviewed in How to Review Video and Autoplay on a Marketing Page, which is also where the browser autoplay rules are explained in full.

Check the Published Page in a Real Browser

Browser rules for autoplay with sound depend on the browser, and on exceptions such as a previous interaction with the site. Those rules are in the video-and-autoplay guide. One practical consequence, from our reading of those rules, belongs here: a reviewer in a fresh browser may hear nothing from a page that plays sound for someone who has already used the site in that browser. Silence in your review is not proof that sound is off.

Open the page directly in your browser and note whether sound starts before you choose an audio control. Record the browser or phone you used and whether you had already interacted with the site. Phone Preview vs Real Phone: What to Check covers what a preview cannot settle.

A useful note might say: “On the Shoreline Walks homepage at [address], in [browser or phone], a soundtrack starts as soon as the page loads, before I choose an audio control. Please keep the page silent until a visitor chooses ‘Listen to a one-minute sample,’ and keep a visible control to stop the audio.”