• Success Criterion 1.4.2
  • Conformance level A

Audio That Starts on a Single-Page-App Route Change

1.4.2 — Audio Control

Scenario

Setting

A used-car marketplace's listing filter

What’s wrong

Audio starts on route change in SPAs (no full page load — users can't rely on browser mute heuristics) with no in-page stop.

Example

Open a used-car marketplace's listing filter and this is what you'll see: audio starts on route change in SPAs (no full page load — users can't rely on browser mute heuristics) with no in-page stop.

Why it matters

Screen-reader users competing with page audio, and people with auditory sensitivity. On a used-car marketplace's listing filter specifically, they miss information that's only conveyed visually.

How to test

Navigate between views in a single-page app: if audio starts on a route change with no full page reload (so browser tab-mute doesn't help) and no in-page stop control, it fails.

How to fix

Audio must not autoplay beyond 3 seconds without an obvious, keyboard-usable pause/stop/volume control.

Outcome

Fixed, a visitor to a used-car marketplace's listing filter can understand the image, video, or audio content, specifically for the “Audio That Starts on a Single-Page-App Route Change” issue on a used-car marketplace's listing filter.

Who is affected

Screen-reader users competing with page audio, and people with auditory sensitivity.

Learn more