06 · Accessible Production
Accessible Music Production
Making music with a screen reader is entirely possible and has been for years, but which tools get you there is not obvious from the marketing. This is a working reference: what the major DAWs actually do with a screen reader, the extensions that make the difference, and where the community lives.
OSARA on Linux
REAPER has run natively on Linux for a while. OSARA — the extension that makes REAPER speak — had not followed it there, which left Linux as the one platform where the DAW ran fine and was unusable if you needed speech. I wrote a port to close that gap.
-
osara-linux (opens in a new tab)
Early — core navigation worksgithub.com/churst90/osara-linux
A port of OSARA to Linux. Speech goes out to Orca through speech-dispatcher, with an AT-SPI bridge underneath. Builds for x86_64, aarch64, armv7l and i686.
What works today
- Focus announcement and AT-SPI integration
- Standard control roles — buttons, checkboxes, radio buttons
- Container navigation and menu navigation
- Dialog announcements
What doesn’t, yet
- REAPER’s custom widgets — the track view, the FX chain, the MIDI editor
- Tab labels and progress bar values
- Non-English menu item state strings
In other words: the dialogs, menus and standard controls talk, and the parts of
REAPER that are drawn rather than built from OS controls do not yet. That is the
honest state of it. The repository has build dependencies, a
setup.sh that autodetects and installs them per distro, and an
installer script that pulls down REAPER and SWS alongside the plugin.
Help wanted
This is a one-person project on a platform with a small user base, and the custom widget work is the hard part. Issues and pull requests are welcome at the repository (opens in a new tab).
REAPER — the essentials
REAPER with OSARA is the most complete accessible DAW setup available on Windows, and the one I use. These four are the stack.
-
REAPER (opens in a new tab)
reaper.fm
The DAW itself, from Cockos. Fully functional evaluation download, and a licence that costs a fraction of its competitors. Windows, macOS and Linux.
-
OSARA (opens in a new tab)
Essentialosara.reaperaccessibility.com
Open Source Accessibility for the REAPER Application. The extension that makes REAPER speak — keyboard access to context menus, and spoken reporting for the actions that otherwise give you nothing. Built for NVDA on Windows and VoiceOver on the Mac; also used successfully with JAWS, and supported by Dolphin SuperNova.
-
OSARA source (opens in a new tab)
github.com/jcsteh/osara
Upstream repository, issue tracker, and the readme — which doubles as the most complete key reference.
-
SWS / S&M Extension (opens in a new tab)
Essentialsws-extension.org
A large collection of extra features that integrate straight into REAPER. Free. OSARA reports on a number of SWS actions specifically, so the two are usually installed together. Source on GitHub (opens in a new tab).
Learning it
-
Reaper Accessibility Wiki (opens in a new tab)
reaperaccessibility.com
The community reference: a getting-started path, the full OSARA readme in browsable form, and a maintained links-and-resources page. Start here if you are setting REAPER up for the first time.
-
REAPER accessibility — a list of resources (opens in a new tab)
soundwithoutsight.org
A curated index of REAPER learning material for blind and partially sighted users, kept current.
-
Reaper Accessible (opens in a new tab)
reaperaccessible.fr
A long-running French resource with a substantial English section, including one of the better plain comparisons of DAW accessibility.
The other DAWs, honestly
REAPER is not the only option, and it is not automatically the right one for everybody — particularly on the Mac, or if the people you work with are all in one program. Here is where the others actually stand.
-
Ableton Live 12
Good, and improvingLive 12 was a genuine turnaround: real screen reader support on both macOS and Windows through the native accessibility APIs, a high-contrast option, and reworked keyboard navigation. Ableton test with VoiceOver on macOS and with NVDA, Narrator and JAWS on Windows. Not everything is covered — some device internals, such as Wavetable’s modulation matrix and parts of Operator, have not been optimised.
Accessibility in Live overview (opens in a new tab) · Manual: accessibility options (opens in a new tab)
-
Logic Pro
Good on macOSStrong VoiceOver support on the Mac, built up over many releases. The key trick most people miss: plug-in and instrument parameters can be shown as a list rather than a graphical panel, which is what makes them fully navigable. Not one hundred per cent — there are still things you cannot do — but a great deal that you can.
Apple: accessibility settings in Logic Pro (opens in a new tab) · Adjusting plug-ins with VoiceOver (opens in a new tab) · Community issue tracker (opens in a new tab)
-
Pro Tools
Workable, with helpAccessible on macOS through VoiceOver, and Avid have worked with blind users on it — but in practice nobody does it bare. Two community projects carry the workflow, and a control surface is widely considered close to necessary for serious work.
PTAccess — a Pro Tools tutorial written for screen reader users (opens in a new tab) · Flo Tools — open-source VoiceOver scripts that automate the tedious parts (opens in a new tab)
-
REAPER
Best all-roundWith OSARA installed, the most thoroughly accessible DAW available, and the only one of these four with a real answer on Linux. It is also the cheapest by a wide margin. The catch is that it arrives as a blank slate: you configure it, and the wiki above exists because that configuration is the actual learning curve.
Where the community is
Most of what is genuinely useful in this field is not documented anywhere official. It is in these.
-
Sound Without Sight (opens in a new tab)
soundwithoutsight.org
The central hub for blind and partially sighted musicians and audio professionals — a knowledge base, discussion, meet-ups and a podcast. Non-profit, hosted by the Technology Association of Visually Impaired People. If you only bookmark one thing on this page, make it this.
-
Reapers Without Peepers (RWP) (opens in a new tab)
groups.io/g/rwp
The long-running REAPER accessibility mailing list — close to a thousand members, beginners through to advanced, on both Windows and Mac. Searchable archives going back years.
-
Blind Producers (opens in a new tab)
blindproducers.org
A community and resource collection aimed squarely at production rather than at any one program.
-
AppleVis (opens in a new tab)
applevis.com
The reference point for anything VoiceOver. The forums carry years of accumulated detail on Logic Pro and Pro Tools that exists nowhere else.
-
An Introduction to Accessible Audio Editing with REAPER (opens in a new tab)
afb.org · AccessWorld
A good plain-English starting article from the American Foundation for the Blind if you are new to all of this.
Why this page exists
Accessibility work in audio is done almost entirely by volunteers, usually one person at a time, usually without anyone asking for it. OSARA exists because someone built it. SWS exists because someone built it. The wiki and the mailing list exist because people kept answering the same questions until it was worth writing down.
The Linux port is my contribution to that, and it is unfinished. But the pattern in this field is that unfinished things get finished when somebody else picks them up, so it is public and it is documented.
Accessibility is most of what I build generally — see Accessible Weather Center (opens in a new tab) and Accessible Trader (opens in a new tab).