Why Queue Music uses a custom slider for playback progress

Queue Music is a web-based music player built around YouTube search, queued tracks and keyboard-friendly playback. Its design gives people who use screen readers or avoid a mouse a clear way to find songs, manage a queue and control listening sessions.

Playback progress is one of the most demanding parts of that experience. A user needs to know where a track is, move through it accurately, hear useful feedback and avoid losing focus. Queue Music uses a custom slider because a carefully designed control can connect those needs more reliably than a browser’s native media interface.

The browser’s native controls are a limited fit

Native audio and video controls are useful for ordinary playback, but they are controlled partly by the browser and partly by the embedded service. Their appearance, keyboard behaviour and accessibility announcements can vary between Chrome, Firefox, Safari and assistive technologies such as NVDA, JAWS and VoiceOver.

That variation matters for a player intended to behave consistently. A native progress bar may expose a position, yet provide little control over how that position is announced or how focus moves between play, volume and seeking. A custom control gives Queue Music a defined interaction model instead of leaving important details to whichever browser a person happens to use.

A slider gives progress a familiar meaning

A playback slider represents the current time as a value between the beginning and end of a track. Its role is familiar to keyboard users: focus the control, use the arrow keys for smaller movements, and use larger navigation keys for broader changes. The exact step size can be chosen to make seeking practical rather than frustrating.

The control can also expose a useful accessible name, current value and boundaries. A screen reader may announce information such as the track position and total duration, helping someone understand whether they are near the chorus, halfway through a podcast or approaching the end of a song. That is more informative than a visual bar that changes silently.

Keyboard control needs to be predictable

For people listening during a Sydney train trip or while moving between platforms at Melbourne Central, a mouse may be inconvenient or impossible to use. Keyboard commands let listeners pause, resume and seek without reaching for a small visual target. The same principle helps people using switch access, alternative input devices or a laptop without a reliable trackpad.

A custom slider can be designed around standard keyboard expectations while fitting Queue Music’s broader shortcuts. Arrow keys can make fine adjustments, while Home and End can move to the start or finish. Page-level movement can support faster seeking. These behaviours reduce the need to repeatedly press a key when a listener wants to skip several minutes.

Screen readers need useful updates, not constant noise

Progress changes every second, so announcing every update would create an exhausting stream of speech. An accessible custom slider can separate the visual update from the spoken update, allowing the interface to provide information when the user focuses the control or actively changes its value.

ARIA properties and live regions can then be used with care. The slider can expose its current position while Queue Music’s other status messages report events such as a track starting, stopping or failing to load. This separation helps a screen-reader user distinguish continuous playback time from an important change in the player.

That balance is especially useful on a long listening session, such as music playing through an NBN connection while someone works from home in Perth. The interface remains informative without competing with the music or turning every small time change into an announcement.

YouTube playback creates an extra boundary

Queue Music uses YouTube as its source, which means the application works alongside an embedded playback system rather than owning a local audio file. The player needs to receive timing information from YouTube, translate it into a usable progress value and send seek commands back to the service.

Native controls do not automatically solve that coordination problem. The visible YouTube interface may have its own focus order and controls, while Queue Music needs a single, understandable experience for searching, queue management and playback. A custom slider acts as a bridge between YouTube’s playback state and Queue Music’s accessible interface.

The design also needs to account for tracks with unavailable or broken video sources. Queue Music explains those situations through playback error details, rather than leaving users to infer from a progress control that something has gone wrong.

Custom styling supports clearer visual feedback

A native range input can be styled, but results may differ across browsers and operating systems. Its thumb, track, focus ring and contrast can be difficult to control precisely, particularly when the player must show a moving position and a keyboard focus state at the same time.

A custom slider lets the interface make those states visible. The filled portion can show elapsed time, the remaining track can show what is left, and a strong focus indicator can identify the active control. This matters for people with low vision, users in bright Australian sunlight and anyone viewing the player on a small laptop screen in a Brisbane café.

Visual customisation still needs to preserve semantic accessibility. A control that looks like a slider but has no meaningful role, value or keyboard behaviour is not an accessible replacement. Queue Music’s approach is useful because the visual treatment is paired with an interaction model designed for keyboard and screen-reader use.

The control fits queue-based listening

Playback progress is connected to queue behaviour. When a track ends, the next item may begin; when a user skips forward, the current position changes; and when a queue is saved between sessions, the player must present the current item clearly. A custom control can participate in those state changes without making the user navigate through an unrelated browser media bar.

Queue management is also easier to understand when the player’s controls follow a consistent pattern. Someone listening to Triple J on a long drive through regional New South Wales may build a queue in advance, while a user in Adelaide may save a collection for a later session. In either case, playback position should remain part of the same accessible workflow. If the queue becomes unwieldy, the instructions for clearing the entire queue explain the action separately from the progress control.

A deliberate control can remain usable over time

The choice of a custom slider is less about replacing a familiar HTML element and more about controlling the complete experience. Queue Music can define how focus is handled, how time is represented, how seeking works with keys and how status information reaches assistive technology. Those details are difficult to guarantee when the browser and YouTube each provide part of the interface.

That consistency supports the project’s wider purpose: making web music practical for people who depend on keyboard access or screen readers. Whether a listener is using VoiceOver on a Mac in Canberra, NVDA on a Windows computer in Hobart, or a compact keyboard during a Melbourne commute, the progress control should communicate the same essential facts. It shows where playback is, accepts intentional movement and stays connected to the rest of the queue.