How Queue Music Announces Playlist Duration on Load

Many people who stream music want to know how long a freshly loaded playlist will play. For sighted users this is a glance at a progress bar. For screen reader users it is an audio cue. Queue Music, the browser-based player built by Thomas Logan with backing from the Mozilla Foundation, treats that moment as an accessibility checkpoint. When a list of tracks lands in the queue, the application reads out the total running time so listeners can plan their session without ever touching a mouse.

This announcement happens through an ARIA live region, the same mechanism that powers weather alerts on a bank website or new message chimes in a chat client. Sydney commuters hopping on the Eastern Suburbs line to Bondi Junction often want to know whether a 45-minute playlist will outlast their trip before they hit play. Melbourne office workers running a playlist through a long focused block might want the same. The duration readout arrives politely, in the same register as any other polite live region update, without forcing the user to fumble for a graphical control.

The Role of ARIA Live Regions in Playback Feedback

ARIA live regions fall into two politeness levels. Polite regions wait for the screen reader to finish what it is saying before delivering the message. Assertive regions interrupt immediately. Queue Music uses a polite region for the duration announcement so the voice never barges in on a track title or an artist name that the user is still listening to. NVDA on Windows and VoiceOver on macOS handle this in subtly different ways, but both treat the polite setting the same way and let the duration land at a natural pause.

The element itself is hidden visually but exposed to assistive technology. When the JavaScript updates the text content with a string such as "Total duration: 1 hour 23 minutes", the assistive layer rerenders that string and announces it. Australian developers working on accessible web apps often model their patterns after the Web Content Accessibility Guidelines, and Queue Music's choice of polite politeness lines up with that guidance for non-essential feedback that still carries useful information.

Critically, the announcement fires once when the playlist finishes loading, not every time the track list mutates. That decision keeps the experience predictable, which matters for users with cognitive load considerations who rely on consistent cues from their tools and dislike noisy interfaces that talk over a track preview.

Why Duration Matters for Daily Routines

Knowing the length of a list turns music from a passive companion into a planned utility. A regional rail traveller boarding at Central Station in Sydney for the three-hour journey up to Newcastle can match a curated playlist to a known travel window. A Brisbane cyclist heading to New Farm Park might build a 50-minute session to fit a single riverloop lap. The screen reader readout is what makes those plans verifiable without relying on visual cues or a sighted companion.

The number also helps users spot when a saved list has been corrupted or truncated. If a "favourite instrumentals" queue used to be two hours but now announces only 22 minutes, the user can act on that discrepancy before pressing play. The same applies when a public playlist pulled from a shared resource has been edited behind the scenes. Hearing the total time acts as a quick sanity check that catches drift before it ruins an afternoon focus block or a long Sunday cook-up.

What Gets Announced Alongside the Time

Duration is rarely the only thing read out. Queue Music typically announces the track count first, then the aggregate time, then a confirmation that the queue is ready to play. The order matters: counting items is a habit many screen reader users develop for any list, from email folders at work to grocery items picked up at a Harris Farm on the weekend shop.

Where applicable, the application also reports on shuffle state. "Shuffle enabled" or "shuffle off" lands in the same polite live region, queued behind the duration line. If the loaded list contains a track that has been marked unavailable on YouTube, a short warning about the skipped item follows the duration announcement so the user can choose a replacement rather than discovering a silent gap mid-listen on a packed train carriage.

Browser Behaviour and Multiple Tabs

Because Queue Music runs entirely in the browser, the announcement depends on where the live region fires and which tab has focus. Only the tab that is currently active delivers live region announcements in most modern browsers. Anyone juggling a work tab, a research tab, and a music tab on a Perth office workstation will hear the duration readout when they first land on the queue tab rather than while reading an email.

The Queue Music team has written about how to coordinate multiple in-flight queues across tabs in the journal walkthrough. Each tab carries its own live region instance, so opening a second queue and switching focus will cause that tab's queue duration to be read independently. This separation also means the announcements do not cross-talk between unrelated sessions, which prevents confusing multi-hour reports from colliding when two queues carry similar numbers.

Users on Firefox with the NVDA remote driver, JAWS 2024, or Apple VoiceOver will all hear the message, though the exact tone and pacing of the voice varies by engine. Listeners on slower regional connections in South Australia have reported that very long playlists can take an extra beat to load before the announcement fires, but the message itself remains consistent across hardware and connection quality.

Customising What You Hear and Where Queue Music Differs

Users who prefer silence or who find repeated announcements distracting can mute the live region through the player preferences panel. There is a checkbox that suppresses duration announcements while leaving track-change updates active. The full set of toggles is documented in the player help guide, which also covers keyboard shortcuts and queue-saving options for users who leave a session running across a full working day.

Queue Music is funded by the Mozilla Foundation and run as a community utility rather than a commercial product. The journal occasionally explores adjacent topics in digital culture, including commentary on free-spin promotions online and how such incentives differ from the trust-based design that underpins the player itself. The duration readout fits into that same ethos, where nothing is hidden, nothing is guessed, and every user gets the same truthful summary of what is about to play.

Listeners always know what they have queued, how long it will last, and whether anything in it is missing. That kind of transparency is uncommon, and for screen reader users in Adelaide, Hobart, or anywhere else across the country, it turns a queue into something they can plan around rather than something they have to keep manually checking with a mouse they do not have.