Saving and restoring Queue Music with the keyboard alone

Queue Music turns YouTube into an accessible web-based player, making it important to preserve the order and current selection of a queue for the next visit. A saved queue should return after a browser, kiosk or computer restart, provided the same browser profile and site data are used.

Keyboard-only operation also depends on clear feedback after each action. It helps to treat a queue as browser-local rather than a cloud playlist: closing a tab, restarting an application and changing devices are separate events with different recovery paths.

Establish a dependable browser profile

Use a normal browsing window and a consistent browser profile whenever you save a queue. Private or incognito windows are unsuitable for long-term storage because their data is routinely discarded when the window closes. A named desktop profile can also prevent another person’s browsing activity from making the saved queue harder to identify.

Queue Music relies on the browser’s saved site data. When you open Queue Music, avoid clearing cookies or site data unless you intend to remove every saved queue and playlist. Browser updates may reset storage in rare cases, so keeping the profile current is safer than using an outdated kiosk installation.

Saving queue details is different from downloading the music itself. The queue can be restored without a connection, but playback still needs access to YouTube. This distinction matters for regional Australian journeys, where mobile data may become unreliable between towns even though the saved queue remains intact.

Save the current queue with keyboard controls

Begin with the desired tracks arranged in the queue. Press Tab to move through the player controls and Shift+Tab to move backwards. The accessible name announced for the save control should identify it as the queue-saving action; activate it with Enter, or Space when the control supports that key.

If the save action is inside a menu, open the menu with the keyboard, use the arrow keys to locate the command and press Enter to confirm. Queue Music provides ARIA live regions, so screen-reader users should receive an announcement when a save succeeds. Wait for that confirmation before closing the browser, since a visual change alone may be easy to miss.

Save the queue again whenever tracks are added, removed or rearranged. An explicit save creates a dependable point for recovery, whereas a queue that exists only in the current page may disappear when the tab closes. This applies whether the planned restart involves the tab, the whole browser or the computer itself.

Reload the queue after restarting

Reopen Queue Music at the same address using the same browser profile. Once the player has loaded, it restores the persisted queue. If the queue is not brought forward automatically, navigate to the queue controls and select the restored or saved-queue option using Enter.

Screen-reader users can move through the restored tracks with the application’s keyboard controls and confirm the queue heading before starting playback. The live region may announce the number of restored items or the first track, depending on the browser and screen-reader combination. Playback can then begin without a mouse or touch gesture.

A named playlist provides a useful fallback. Saving the current queue as a playlist creates another app-level copy that can be opened from the playlist controls after a restart. It remains tied to the browser profile rather than syncing automatically across devices, and unavailable YouTube tracks may not play if catalogue access changes.

Keep shared and kiosk setups consistent

Shared computers in Australian cafés, libraries and community centres need a predictable configuration. The guide for configure a kiosk player explains how to make Queue Music the default player while retaining keyboard access and screen-reader compatibility.

Give the kiosk a dedicated browser profile and a fixed, secure address for the player. Avoid private browsing, clear old site data only when necessary and ensure that automatic sign-in does not expose personal accounts to the next user. A dedicated profile makes saved queues easier to audit and restore.

Kiosk operators must also consider the Privacy Act 1988 and the Australian Privacy Principles when applicable. Queue Music’s accessible controls do not replace privacy obligations for organisations that collect sign-in details, analytics or other personal information. Removing personal queues between sessions reduces the amount of information left on a public device.

Diagnose a queue that has disappeared

Begin by checking whether the save action produced an announcement and whether the same browser profile was reopened. Then confirm that the player was not launched in a private window and that site data has not been cleared. Moving Queue Music to a different domain or address can also prevent the browser from finding the original saved data.

Review storage settings, content blockers and extensions that might be preventing the player from loading its saved state. Reopening a recently closed tab may recover an unsaved page session, but it should be treated as a temporary recovery method rather than a substitute for the explicit save action.

The keyboard help guide provides the relevant control and accessibility information. When documenting a problem, note the browser, screen reader, save announcement and restart sequence, but remove personal playlist names and account details from the report.

Follow a repeatable save and restore sequence

A short routine makes queue persistence predictable on a commuter’s laptop in Melbourne, a phone used on Brisbane buses or a shared computer at home. Keep the browser profile stable and complete the save before closing anything.

Before closing

After restarting

This sequence preserves queue order across a restart while keeping every essential action within keyboard and screen-reader reach.