Embedded audio player

The embedded audio player is the component displayed on the article page, usually between the headline and the first paragraph, that lets readers start the audio version. It is the single point of contact between a publisher's entire audio investment and its readers: if the player is slow, ugly or buried, nothing else matters.

One-line integration

Technically, a player is most often integrated through a single code snippet added to the article template: a script tag or an iframe. The script detects the page's article, checks that an audio version exists and renders the player; the iframe isolates the component from the rest of the page, avoiding style and script conflicts with existing code. Either way, installation happens once, on the template, and then covers every article on the site.

For WordPress sites, the WeDispatch WordPress plugin removes even that step: the player is configured from the CMS admin, without touching code.

What separates a good player

Four concrete criteria. Weight first: the player loads on every article page and must not degrade site speed or the web performance metrics search engines factor in. Accessibility second: operable by keyboard and properly announced to screen readers, otherwise the audio meant to help certain audiences becomes unreachable for them. Visual consistency third: colours and typography should match the publication's design, because the player lives on the article page, the most viewed real estate on the site. Measurement last: every play, every drop-off, every stopping point must be reported, because that is the raw material of the listen-through rate.

The player is also the foundation for advanced features: read-along highlighting, the preview before a registration wall, ad insertion. Everything runs through it.