Defining the skip controls in Queue Music's interface

Queue Music is a web-based player designed from the ground up for keyboard-only operation and screen reader compatibility. Created by Thomas Logan with support from the Mozilla Foundation, it pulls tracks from YouTube, lets users build queues, and exposes every action through shortcut keys. Among those actions, the skip-forward and skip-backward commands are the most frequently used during a listening session, and the way their intervals are defined shapes how the whole player feels.

The default interval sits at a value that balances two competing needs: reaching a new track quickly without overshooting, and stepping back just far enough to catch a missed lyric. Most users discover these shortcuts within the first few minutes, and the chosen values reflect research into how people actually scrub through audio when their hands never leave the home row.

The constants that drive the jump

Inside the source, the skip distances are stored as plain constants near the top of the playback module. A forward jump and a backward jump are defined separately, with the forward value slightly larger than the backward one to account for the way people typically want to move through a song. The numbers are expressed in seconds, which keeps the logic readable for anyone browsing the repository or adjusting the code for their own deployment.

These constants feed directly into the playback engine. When a user triggers the forward key, the engine reads the current timestamp, adds the constant, and seeks the underlying YouTube player to that point. The backward command performs the same calculation in reverse, subtracting the constant and clamping the result to zero so a skip never lands before the track begins. Because the constants live in one place, changing them is a matter of editing two lines, and the rest of the application responds automatically.

The choice to keep these values hard-coded rather than computed at runtime was deliberate. The development team wanted the shortcuts to feel identical on every device, from a powerful desktop in a Brisbane co-working space to a budget laptop connected to the NBN in a regional Tasmanian town. A fixed value removes any chance of inconsistent behaviour caused by network jitter or device performance.

Announcing the new position

Accessibility is central to Queue Music, and the skip commands do more than move the playhead. Each jump triggers an ARIA live region update that announces the new timestamp to screen readers, using a format that screen reader users in Sydney and Perth have reported as clear and easy to parse. The announcement fires once per command, avoiding the chatter that happens when a player reports the position continuously.

The announcement is short by design. It reads the minutes and seconds in plain language, then briefly states the action that was taken. A forward skip might say "two minutes forty-five seconds, skipped forward," while a backward skip says "one minute twelve seconds, skipped backward." This pattern matches the conventions used in other accessible media tools, and it gives users enough information to decide whether to keep listening from that point or trigger another jump.

The team chose to announce the resulting position rather than the interval itself. A user pressing the backward key generally wants to know where they have landed, not how far they have travelled. This decision reflects feedback gathered during testing with screen reader users across Australia, including participants who navigate long-form audio content like interviews and audiobooks through the player.

Why these specific values

The forward and backward intervals were selected after informal testing with a small group of keyboard-first users. The forward jump is set long enough to clear most spoken-word interludes, ad reads, and intros, while the backward jump is set shorter because people often overshoot a line of lyrics and only need a small step back to catch it. The asymmetry mirrors how listeners actually behave, rather than enforcing a uniform skip in both directions. The reasoning is documented further in the project journal, which includes notes from early user testing sessions.

Audiobooks and music are consumed very differently through Queue Music, and the fixed intervals work for both. A podcast listener in Adelaide can jump past a sponsor segment with one forward press, while a music fan exploring Triple J's unearthed archive can step back a few seconds to hear a guitar line they missed. The values are not adaptive to genre, but the spacing has been chosen to remain useful across content types that vary widely in pacing.

For users who want a different feel, the constants are documented in the project's README and can be changed before the application is built. A user hosting a private instance for a community radio station in Melbourne might extend the forward interval to skip entire blocks, while a listener working through a lecture series might shorten it to scrub more carefully through dense material.

Customisation and persistence

While the defaults suit most listeners, Queue Music offers a settings panel where the intervals can be adjusted without touching the code. Changes are written to local storage, so the same values appear the next time the page loads, and they persist across browser restarts on a single machine. A user can set a generous forward jump for morning commutes and a smaller one for late-night listening without reconfiguring the player each time.

The persistence layer uses the same mechanism that stores saved queues, keeping the data model simple. For Australians working across multiple devices, the settings stay local rather than syncing to a cloud account, which the development team sees as a privacy benefit as well as a technical simplification. Anyone wanting a synced setup can export their preferences and import them on another device manually.

The settings also include a toggle for the screen reader announcement, which some users prefer to silence when they are sharing audio in a shared space like a public library or a quiet study area. This combination of configurable intervals and optional announcements reflects the broader philosophy behind the player: useful by default, adjustable when needed, and never presumptuous about how someone wants to listen.

Looking ahead

The skip controls are unlikely to change dramatically in future releases, but the team is exploring options for users who want preset profiles. A music profile, a podcast profile, and an audiobook profile could each ship with tuned intervals, removing the need to adjust settings manually. Feedback from Australian users has been positive so far, and the project continues to grow through community contributions and ongoing support from the Mozilla Foundation.

For readers curious about the wider local landscape, the Australian registration guide offers practical context on regional account setup and service availability, sitting alongside other entries in the Queue Music journal for anyone configuring the player to suit Australian conditions.