Browser autoplay policies block sound-on-load AI-researched
Dependency: Browser autoplay policy
Modern browsers restrict autoplay with sound (Chrome 66 era), breaking net artworks that rely on immediate audio/video or WebAudio on page load unless redesigned around user gestures.
Affected Artworks
philip wood
Randomized animation loops with audio. Audio may not start automatically; experience changes.
Liz Franko
Flash/HTML animation coupled with audio playback. Autoplay audio blocked; timing/affect shifts.
Jodi Rose
Embedded audio players (SoundCloud or similar). Autoplay may be disabled; user must press play.
Fixes & Mitigations
- Workaround: Add explicit 'Start / Enable sound' interaction and treat it as part of the work's dramaturgy.
- Workaround: Use muted-first strategies and prompt unmute.
Chrome’s autoplay policy (launched in Chrome 66, April 17, 2018) generally allows muted autoplay but blocks autoplay with sound unless the user has interacted with the site or meets engagement heuristics.
Notes
Autoplay changes are reversible only by redesign; you cannot rely on consistent sound-on-load across browsers.