UbuntuNext

Configuring Ubuntu for accessibility with Orca screen reader

Ubuntu can provide a capable, private desktop for people who rely on a screen reader. Orca reads interface elements, text and speech through synthesised voices, while GNOME handles accessibility settings such as magnification, high contrast and braille. Together, they create a keyboard-friendly environment that can be adjusted to individual needs rather than left at factory defaults.

A useful setup starts with small, repeatable tests: hear a menu, locate a text field, read a paragraph and recover when a window opens unexpectedly. This guide covers those foundations, explains how to combine spoken output with braille, and identifies common causes of missing speech or confusing focus. It also considers Australian conditions, including regional connectivity, Auslan access and the realities of buying a laptop in a market where most machines arrive with Windows.

Prepare a reliable Ubuntu desktop

Use a computer you can still operate visually or with assistance while making the first changes. A recent Ubuntu LTS release on a supported laptop or desktop provides a familiar combination of GNOME and Orca. Check the manufacturer’s documentation for wireless, audio and sleep support, since compatibility varies even when the processor itself is well supported. The UbuntuNext community site provides Linux hardware guidance for readers assessing a separate machine or vendor support before buying.

Orca is normally included with Ubuntu, but it can be installed from the software repositories. Open Terminal with Ctrl+Alt+T and run:

sudo apt update
sudo apt install orca

If apt reports that Orca is already installed, that is expected. The second command ensures the package is present even when the desktop’s accessibility toggle is missing. You can also find the reader through Activities by searching for “Screen Reader” or “Orca”.

Plan for connectivity outside major cities. Fixed-wireless and mobile broadband are common in regional areas, but an outage can interrupt updates or prevent an additional voice from downloading. Install the basic offline voice before relying on the setup, keep support contacts and emergency details in an accessible text file, and test the system on a slower connection rather than only on fast metropolitan fibre. Australian consumer laptops usually ship with Windows, so confirm Ubuntu compatibility and the supplier’s repair options before replacing the original system.

Enable the screen reader and set its behavior

Open Settings, choose Accessibility, select Seeing and switch on Screen Reader. Orca should announce itself with a welcome message and place a small panel near the top of the screen. This panel provides access to preferences, volume controls and help. On a fresh login, try Super+Alt+S, the usual GNOME shortcut for the screen reader, and remember that the same combination can silence a running instance. If no welcome message appears, continue through the visual menu and investigate the audio path later.

Give the first session time to speak. Use Tab to move between controls and Shift+Tab to move backwards; Orca should name the focused widget and its state. Try opening Settings and reaching the Bluetooth panel, then close the window with Escape. This short exercise tests speech, focus announcements and the keyboard without filling the desktop with notifications. Ctrl interrupts the current phrase, which is useful when a window opens over another and you need to hear the new context.

Apply the reader to the login session as well as the desktop. Sign out while it is active, then check the password prompt on a separate screen where possible. Some Ubuntu and GNOME combinations expose an accessibility icon at the sign-in screen, while others require the reader to be enabled for the session first. Avoid storing credentials until the login flow has been heard reliably. A physical keyboard remains valuable even with perfectly clear speech because some system controls still require a key combination to reach.

Tune speech and navigation

Open Orca’s preferences from its application menu and review the Speech tab before changing anything else. Select the headphones, monitor or external speaker you actually use. Raise the volume until a sentence is clear without straining, then set the rate slightly above your normal reading pace. The voices supplied through Speech Dispatcher generally prioritise intelligibility over a natural human sound. Where an Australian English voice is offered, compare it with a British or American voice, since familiar place names and accents can sound quite different.

Verbosity controls how much context Orca adds to each utterance. A compact setting suits experienced users who know the layout, but beginners often benefit from hearing the application name, role and state of a control. Start with the default, then reduce the detail if every arrow-key press triggers a long announcement. Punctuation settings can make full stops and capitals audible, which helps when reviewing code or addresses. Character echo is useful for spelling one word but slows ordinary typing; word echo provides a useful middle ground.

Practise navigation in a document or on a web page instead of trying to memorise every shortcut at once. The Orca modifier is usually Alt+Shift, and these combinations cover common needs:

These shortcuts work best in browse mode. A text editor may expose different controls from a web form, so each application has its own structure to learn. If an unfamiliar page is difficult, use the browser’s normal commands for headings, lists and links instead of assuming an Orca command has failed.

Add braille and visual accessibility tools

Braille provides a second route through the same interface. Connect a refreshable braille display, then open the accessibility settings and enable the braille display. Search for “Braille Monitor” in Activities to check whether the device is transmitting text. This monitor can show the focused text even without a physical display, making it useful for diagnosing a connection. Orca often detects a compatible device automatically, but some Bluetooth models must first be paired through the normal Bluetooth panel. Test short passages, editable fields and lists before changing the display’s table mode.

For low vision, combine speech with GNOME’s High Contrast option, larger text and screen magnification. Check each application separately because a browser’s zoom control, a terminal’s font settings and a word processor’s view options may differ from desktop-wide settings. Magnification can make a window difficult to follow, so test a moderate level and learn how to pan the view. A high-contrast theme can also change colours in editors and colour-managed images, giving you a clearer interface without altering the content.

A screen reader does not replace Auslan or human interpreting. People who use Australian Sign Language may still need an interpreter when the other person does not sign. The Australian Government’s National Relay Service supports options including text relay, internet relay and Auslan interpreting. Its web-based relay options can be used in a browser on an Ubuntu computer, complementing Orca by handling live communication rather than reading the screen.

Test real tasks and fix common snags

Test with the tasks you actually perform. Open a saved text file, check that you can edit a sentence, browse an online shop and complete a form requesting an email address. Try to complete each task without a mouse. Then sign out and return to test the login screen. Include video and audio content in the checks, because captions, transcripts and audio descriptions need separate verification. A page that reads correctly does not guarantee that every download, verification code or embedded form is accessible.

If speech is missing, check the system output and application volume first, then confirm that the desktop is using the expected device. PipeWire, the sound server used by current Ubuntu releases, can be inspected with the PulseAudio Compatibility tool pavucontrol; install it using sudo apt install pavucontrol if necessary. In Terminal, orca --replace starts a fresh instance and often clears a stuck reader. Rebooting can restore the session too, but it should not be the answer to every problem.

Weak or incomplete announcements are often application-specific. GTK applications, browsers and Java or Electron interfaces can expose different amounts of information, while a page drawn onto a canvas may offer no usable text to a reader. Try a text-based alternative or another application before concluding that Orca is faulty. Compare a Snap-packaged Firefox with another browser and check its update status if its behaviour differs. Community support is often practical: a council library in Melbourne or Hobart may help with a form on a public computer, while a local Linux meet-up volunteer can reproduce a shortcut. At a meet-up, saying that “the reader stopped after Alt+Shift+E” gives someone more to work with than saying the computer is playing up.

Keep the configuration reliable

A stable configuration needs occasional care. Keep a short note of your speech rate, verbosity, punctuation and magnification settings. Review updates when the connection is reliable, and avoid changing several options at once; small changes make it easier to identify a useful adjustment. Test the setup after a major GNOME update, particularly when the accessibility panel has moved or a Snap-packaged application has changed. If you rely on a braille display, keep its pairing instructions and firmware details with the system notes.

The next concrete step is to open Settings, select Accessibility and confirm that Screen Reader is enabled.