What the Queue Announces When Arrow Keys Move Focus

Queue Music makes the queue an interactive keyboard space rather than a visual playlist that merely responds to clicks. When a screen reader user presses the arrow keys inside the Queue, speech identifies the item that now has focus, along with useful context such as the track name, artist or YouTube channel, and position in the queue.

The wording is not identical in every screen reader and browser. Some place the position first, others add “selected”; a few include a duration or current-playback state. The consistent information is the same: which song is focused, where it sits, and whether it has a state that affects the queue.

That separation between navigation and playback matters. Moving through a list is a way to inspect and choose songs, not a request to skip the current track. Queue Music was developed by Thomas Logan with Mozilla Foundation funding, and its semantic controls and ARIA live regions are designed to make that distinction clear without sight or a mouse.

Moving focus through the queue

Queue entries are exposed to assistive technology as labelled options or rows. When focus enters the list, the screen reader may announce the list’s role and size, such as “list, 12 items.” A press of Down then moves the active option to the next song; Up returns to the preceding song. The speech follows the movement immediately rather than waiting for a click elsewhere.

Each move is based on the focused element’s accessible information. Its name normally comes from the visible song title, while metadata supplies the performer or channel. Position metadata can produce a phrase equivalent to “3 of 12.” The screen reader does not need to count the rows aloud, and it will not normally describe cover art, colours or the YouTube URL.

What each announcement contains

A typical announcement therefore contains the title first or near first, followed by the artist, position and any relevant state. It might be heard as “Blue Sky, Missy Higgins, 4 of 12, selected,” or in the same information in another order. An exact quotation would be misleading because NVDA, JAWS and VoiceOver package the same ARIA data differently.

If the queue marks one entry as the current track, “now playing” may be added to that entry. If duration is part of the item’s accessible description, it may also be spoken. These additions are helpful when reviewing a long queue, although they can make one row noticeably longer to announce than another.

Up, down, left and right

Up and Down are the primary keys for moving between queue items. They change focus, or the active descendant in a composite widget, and the spoken output changes to match. Repeated presses can be used to scan titles quickly, pause on one entry, and continue without activating anything.

Left and Right depend on what is focused. When an entry offers inline actions, those keys can move into controls such as “Move up,” “Move down” or “Remove from queue.” At that point the screen reader announces the control’s name and role, not the full song description again. On other focused elements, Left and Right may have no queue effect.

Enter and Space then behave according to the focused role. A button is activated, while a selected song is played only when Queue Music’s play action is chosen. Arrow navigation by itself should stay silent about playback changes, preventing a scan through titles from sounding like a sequence of skipped tracks.

Choosing a track and starting playback

“Selected” and “now playing” describe different conditions. Selection marks the entry under review; now playing identifies the track whose audio is active. A screen reader user can therefore arrow through future songs without interrupting the current one. The playback control carries its own accessible name and pressed or unpressed state.

Changes that do not move focus are handled separately by live regions. Adding a result might produce a brief “added to queue” announcement, and removing or reordering an entry can report the new position. When playback starts, a polite status message may identify the track. These messages are short status updates, while the longer item description belongs to the focused queue control.

Listening to the queue in Australia

Australian setups vary widely: a user may pair NVDA with Firefox or Chrome, JAWS with Chrome, or VoiceOver with Safari on a Mac or iPhone. An Australian English voice may pronounce “queue” as “cue,” but imported artist names and song titles can still sound awkward. Checking the speech settings before a long trip avoids mistaking pronunciation for a different track title.

The setting is practical in cities such as Sydney, Melbourne and Brisbane, where a short queue can fill a train, tram or bus journey. Headphones keep announcements and music from leaking into a carriage, and low-volume speech output remains audible above traffic. A saved queue also keeps the same list available after the screen is locked or the device changes hands.

Local listening habits are reflected in the sort of music people queue. A new release heard on Triple J might sit beside a work from ABC Classic, an Australian-chart single or a song by a First Nations artist. Each title enters the spoken queue as searchable text, even when the screen reader cannot reproduce the artist’s intended pronunciation perfectly.

Australian listeners already have familiar choices such as Spotify, Apple Music and YouTube Music. Queue Music’s YouTube foundation makes it easy to place within that local market, while its defining feature is a keyboard-and-screen-reader queue rather than a conventional music player.

Verifying what is spoken

The Queue Music keyboard guide maps the available shortcuts and queue controls, making it the best reference for the exact browser experience. Because screen readers can differ in verbosity, users can adjust punctuation and level of detail, but that setting should not remove the song title or queue position.

A useful check is to queue three tracks with clearly different titles, enter the list, and move Down twice. The first movement should identify the next item, the second should announce the third item and a position such as “3 of 3,” and no track should start merely from those presses. The sequence should remain repeatable with JAWS, NVDA or VoiceOver, with only presentation differences.