The website needs to work in the visitor’s world
A visitor may be comparing providers at work, travelling, listening to something else or using assistive technology. Unexpected sound gives them another thing to deal with before they can understand your offer. For a service website or online catalogue, start with clear information and an easy route to the next step. Music should have a reason to be there beyond making the page feel lively.
Autoplay is not a dependable introduction
Browsers often restrict audio that starts without a deliberate user action. The exact behaviour depends on the browser and context. A website should still make sense when its audio does not play. If a message, explanation or instruction is important, provide it as readable text rather than making successful audio playback the only way to receive it.
Give people a deliberate choice
If sound adds value, label the action clearly and let the visitor start it. A product demonstration, performance sample or spoken explanation is different from music that starts unexpectedly on every page. Make play, pause and volume controls easy to find, and avoid restarting the sound simply because the visitor follows another link.
Think about accessibility from the beginning
Background sound can interfere with spoken content from a screen reader. W3C’s audio-control guidance explains the need for a way to pause or stop audio that plays automatically for more than three seconds, or to control its volume independently of overall system volume. Its guidance also encourages starting sound through a user action. Choosing visitor-controlled playback is a practical starting point.
- Use a clearly labelled action to start the audio.
- Keep pause or stop controls available and operable with a keyboard.
- Provide the important information in an accessible alternative form.
- Check that the page is useful when sound is off.
Choose the format around the job
Before adding music or another audio feature, ask what it helps the customer understand. A visual demonstration may need captions or a written explanation. A music business may need samples. A local service page may need no audio at all. The useful choice follows the content and the visitor’s task, rather than a rule that every website should sound or look the same.
| Website requirement | A useful starting choice |
|---|---|
| Explain a service or show an online catalogue. | Clear text and relevant images, with no surprise audio. |
| Demonstrate a product or process. | An optional, labelled demonstration with an accessible explanation. |
| Let people evaluate music or audio work. | Visitor-controlled samples with clear playback controls. |
Test the experience before launch
Try the page with sound off, using only the keyboard and on the devices your visitors use. Check that controls remain visible and the page still explains the offer. Review media delivery alongside the rest of the page’s performance. Audio should earn its place by helping the customer, not make them hunt for the mute button.