Using VoiceLink with VoiceOver

This guide covers the main VoiceOver tasks for servers, rooms, messages, and audio controls.

Intro

VoiceLink is intended to work well with VoiceOver. This guide covers the main tasks, navigation patterns, and spoken cues you need to move between servers, review room details, join rooms, manage audio, and send diagnostics.

Basics

  • The server list is the first major area to check when the app opens.
  • The rooms view updates to match the selected server or the current federation view.
  • Room details tell you which server a room belongs to, which matters when rooms with the same name exist on more than one server.
  • Settings should remain available while you are in a room so you can change audio or diagnostics without leaving.

Getting Started

  1. Open VoiceLink and wait for the startup sound to finish.
  2. Move to the server list and choose the server you want.
  3. Move to the rooms list and review the focused room name and server source.
  4. Use the default action or VoiceOver actions to preview, open details, or join.
  5. After joining, confirm the room title, users, bots, and system messages are present.

Servers

Each server should be announced by its display name. If descriptions are configured, read them before joining rooms so you know whether you are on Main, Community, or another linked server.

Rooms

Rooms should announce the room name and enough detail to distinguish rooms with the same name on different servers. In federation views, the server source is part of the room context.

Settings

Settings should stay reachable while you are in a room so you can change announcement preferences, diagnostics, or audio behavior without navigating away from the active room.

Working with Rooms

Previewing a room

Use Preview when you want a short background listen before joining. The preview should end automatically after the preview interval.

Opening room details

Use room details to confirm the room name, server, access level, visibility, and any current background media before you join.

Joining a room

Join the room from the room row or details screen. The room header should then identify the active room and server.

Reviewing people in the room

Move to the user list after joining. Users, bots, and supported system entries should appear there instead of a generic empty-state message when the room is active.

Reading room and system messages

If chat is enabled for the room, messages should appear above the message field. System messages should also be readable when the room configuration allows them.

Adjusting room audio controls

Show audio controls only when needed. Room media, user volume, mute, and monitoring should be available through the room menu or user actions without forcing a room disconnect.

VoiceOver and Keyboard Notes

  • VO-Space activates the selected item.
  • VoiceOver actions on a room row can expose Preview, Join, Share, or Details.
  • VoiceOver actions on a user row can expose actions such as profile, direct message, or audio controls when supported for that user type.
  • Sliders should announce percentage values and adjust in consistent steps.
  • Escape closes dialogs or sheets where the platform supports it.

Troubleshooting

  • If no room users are shown, refresh the room once and then send diagnostics.
  • If no audio is heard, check mute state, output selection, and whether room media is enabled.
  • If a secure connection fails, the app may retry the fallback transport when the server allows it.

Contact and Feedback

When reporting a VoiceOver issue, include the platform, build number, server name, room name, and the exact control label or spoken phrase that did not match the guide.