In one paragraph
Video or audio elements must not play automatically is the rule label, but WCAG does not prohibit every form of autoplay. Automatically playing sound lasting more than three seconds needs the specified independent control. Muted motion has separate requirements. The supplied WebAuditOS configuration does not surface this rule's review results, so inspect actual playback and user controls manually rather than interpreting no finding as approval.
Why it matters
Unexpected audio can compete directly with screen-reader speech and make the controls needed to stop it difficult to discover. WCAG 1.4.2 requires a mechanism to pause or stop automatically playing audio over three seconds, or independent volume control that can reduce it to zero.
System-wide mute is not the independent page-audio control the criterion describes. A tiny sound loop should also be assessed by its real ongoing experience rather than treating each repeat as a new harmless short clip.
Browser autoplay policies help but vary with user interaction, settings, engagement, and environment. They are not a stable substitute for intentional product behaviour. Muted video avoids unwanted sound, but moving content can still need pause or stop controls under WCAG 2.2.2, and meaningful video can need captions or other alternatives.
How WebAuditOS evaluates this finding
The supplied no-autoplay-audio specification inspects relevant autoplay media attributes, sources, muted or controls status, and available duration, with separate handling for looping and missing metadata. It can miss script-initiated playback and content inside third-party frames.
The source states that review outcomes are not included in the failures-only report, so the current integration raises no finding from this rule. Its nominal moderate impact would map to medium if reported. This is a product coverage statement requiring configuration verification, not evidence that all actual sound was measured.
How to fix it
- Inventory native players, background videos, embedded services, sound effects, and scripts calling play. Inspect the actual rendered state and media source, not merely a search for autoplay in templates.
- Prefer user-initiated playback for meaningful sound. A simple audio starting point is:
<audio controls src="/media/interview.mp3"></audio>No autoplay attribute is present. The player still needs appropriate context, usable controls, and an equivalent transcript when required.
- If background video is genuinely necessary, start muted and provide an obvious accessible way to pause the motion. Do not rely on the absence of an audio track or a browser blocking policy as the whole accessibility plan.
- Where automatic audible playback remains, satisfy the actual independent control requirement and put an effective control where users can reach it promptly. Test that stopping it does not require first hearing a long page over the competing audio.
- Check initial and subsequent states. A permission prompt, consent action, route transition, or restored user preference can change whether autoplay succeeds. Verify safe defaults without ignoring deliberate user-requested playback.
- Use labelled native buttons and correct state feedback for custom play, pause, mute, or volume controls. Preserve keyboard operation and focus, and ensure controls actually operate the intended player.
- Review captions, transcripts, visual alternatives, motion, and flashing separately. A muted hero with no sound may still carry information or distract continuously. An audio-control pass does not evaluate those needs.
- Test with supported browsers and assistive technology where practical, including third-party embeds. Record manual results because the supplied report does not expose this rule's review cases.
What the fix can break
Removing autoplay changes playback analytics and can reduce unsolicited starts. Distinguish that measurement effect from evidence that users lost access to useful content.
Muting meaningful speech without an accessible way to start it deliberately or obtain an equivalent can remove information. Preserve a coherent content experience rather than only silencing the player.
Adding a custom pause icon without a usable name, state, or working handler is not a complete control. Test real interruption and resumption across input methods.
Questions
Does WCAG ban every autoplay video?
No. Sound, movement, alternatives, and their applicable conditions must be assessed separately.
Does muted autoplay automatically meet all media requirements?
No. It avoids audible playback, but motion and information alternatives can still require work.
Why does no finding not prove success?
The supplied integration omits review results for this rule and cannot observe every playback mechanism.
Which related checks help?
Review video captions, audio alternatives, and the automation limits guide.
What severity does this get in the report?
None, today - the finding is not raised, because axe-core reports failures of this rule as "needs review" and our report contains only confirmed violations. axe declares the rule moderate; if it were reported, the mapping of critical and serious to high, moderate to medium and minor to low would make it medium.