WCAG 1.4.7: What Low or No Background Audio Actually Requires
Jamie · AI Research Engine
Analytical lens: Strategic Alignment
Small business, Title III, retail/hospitality
AI-assisted · Source-linked · Editorially reviewed · Methodology
Trust note
This article was drafted with AI assistance, reviewed against accessibility.chat editorial standards, and should be treated as research and education rather than legal advice. We prioritize primary sources and correct material errors.

What does a 20 dB threshold have to do with equal access to audio content? More than most teams realize — and the answer starts with understanding who gets left out when background sound overwhelms speech.
WCAG Success Criterion 1.4.7 (opens in new window) addresses a specific, measurable problem: prerecorded speech audio that competes with background sound in ways that make it inaccessible to people who are hard of hearing. The criterion sits at Level AAA — the highest conformance tier — which means it's aspirational rather than required for most baseline compliance claims. But "aspirational" shouldn't mean "ignorable." For the people this criterion protects, background audio isn't a minor annoyance. It can make spoken content completely unintelligible.
The Requirement
SC 1.4.7 applies to prerecorded audio-only content and the audio track of prerecorded video. It requires one of three conditions to be met:
- Background sounds are at least 20 dB lower than the foreground speech content
- Background sounds can be turned off by the user
- There is no background audio at all
The 20 dB figure isn't arbitrary. It comes from research on large-area assistive listening systems (LAALS (opens in new window)) and studies on interference in hearing aids from digital wireless telephones (HEARING-AID-INT (opens in new window)). Twenty decibels represents roughly a 4:1 ratio in perceived loudness — enough separation that a hearing aid or assistive listening device can meaningfully amplify the foreground speech without proportionally amplifying the background noise.
The criterion has explicit exceptions. It does not apply to audio where the background sound is essential — a musical performance, a nature soundscape, a documentary where ambient sound is the point. It also does not apply to audio CAPTCHAs or audio logos. The target is narration, instruction, and speech-primary content where background sound serves a decorative or atmospheric function.
The single sufficient technique documented by W3C is G56 (opens in new window): mixing audio files so that non-speech sounds are at least 20 dB lower than the speech, or providing a version of the content without background audio.
Why This Matters
People who are hard of hearing — including the estimated 15% of American adults who report some degree of hearing difficulty — often rely on hearing aids, cochlear implants, or assistive listening devices. These technologies are good at amplifying sound. They are not good at selectively amplifying the right sound.
When background music or ambient noise sits close to the same volume level as speech, hearing aids amplify everything together. The signal-to-noise ratio doesn't improve; it just gets louder. For someone with high-frequency hearing loss, consonant sounds are already difficult to distinguish. Add a music bed running at comparable volume, and words blur into noise.
The practical consequence: a training video with background music, a product explainer with ambient sound design, a podcast-style interview with music intros that don't fully fade — all of these can exclude people who are hard of hearing from accessing the spoken content. This isn't a theoretical edge case. It's a routine production choice that gets made without considering its downstream effect on listeners who can't simply "tune out" background sound the way hearing people do.
Cognitive disabilities add another dimension. Background audio increases cognitive load for many users, including people with attention-related disabilities or auditory processing differences. The 20 dB threshold addresses the perceptual problem; the "turn it off" option addresses both the perceptual and cognitive dimensions.
How to Meet It
Three paths to compliance, in order of production complexity:
| Approach | What It Requires | Best For |
|---|---|---|
| No background audio | Remove music/ambient sound entirely | Instructional content, training videos |
| 20 dB separation | Mix background at ≥20 dB below speech | Branded content where music is desired |
| User control | Provide audio toggle or alternate track | Complex productions with layered audio |
For production teams, the 20 dB rule needs to be part of the audio mixing brief, not a post-production afterthought. If a video producer is working from a style guide that calls for a music bed, that guide should specify the dB differential. This is a workflow and specification problem as much as a technical one.
For content with existing background audio, the remediation path is to either re-mix with corrected levels or produce an alternate version without background sound. Neither is trivial for large content libraries, which is why catching this at the production stage matters.
For user-controlled options, the implementation requires a UI mechanism — typically an audio settings panel or a toggle in the media player — that lets users disable background audio independently of speech. This is architecturally more complex but gives users the most control.
Common failures include music that fades from intro levels but never drops to the 20 dB threshold during narration, ambient sound in interview settings that wasn't controlled during recording, and audio that meets the threshold on studio monitors but not in the compressed formats used for web delivery.
Applying This
SC 1.4.7 is almost entirely a manual review concern. Automated testing tools cannot measure audio signal levels or evaluate whether background sound is "essential" to the content. As our research on automated versus manual testing methodologies makes clear, audio criteria sit firmly in the category of issues that require human judgment.
Practical QA steps:
- During production: Require audio engineers to document dB levels for speech and background tracks. Make this part of the deliverable specification.
- During review: Use audio analysis software (Audacity is free; Adobe Audition provides more detail) to verify the differential before publishing.
- For existing content: Prioritize high-use content — onboarding videos, training modules, product demos — for audit. Full library remediation is a long-term project; focus first on what users actually encounter.
- For media players: Verify that any background audio controls are keyboard accessible and work with screen readers. Solving the audio problem while creating an interface barrier defeats the purpose.
Teams working across multiple standards frameworks — WCAG, Section 508, EN 301 549 — should note that audio requirements like this one can create compliance complexity across overlapping standards. The underlying requirement is consistent, but documentation and testing expectations may differ by framework.
CORS Perspective
From a strategic alignment standpoint, SC 1.4.7's AAA status creates a real organizational challenge: it's easy to deprioritize requirements that aren't part of baseline conformance claims, even when the people they protect face genuine barriers. The business case here isn't about litigation risk — AAA criteria rarely appear in enforcement actions — it's about whether an organization's audio content actually serves the 15% of users with hearing difficulty. For media-heavy industries (e-learning, corporate training, marketing), that's not a marginal audience. Framing this as a production quality standard, not just an accessibility checkbox, tends to land better with teams who control audio workflows. The 20 dB threshold gives them something concrete to specify and verify, which is exactly the kind of measurable standard that production pipelines can absorb.
About the Jamie lens
A strategy lens for small business and Title III. Frames findings around cost, sequencing, and what a retail or hospitality operator can realistically act on first.
Jamie is an AI analyst lens, not a human staff member. It helps frame this article through a consistent accessibility perspective.
Specialization: Small business, Title III, retail/hospitality
View all articles using this lens →Primary source reviewed: https://www.w3.org/WAI/WCAG22/Understanding/low-or-no-background-audio (opens in new window)
Transparency Disclosure
This article was drafted with AI assistance and reviewed against our editorial methodology. We disclose that process so readers can judge the work clearly.