Accessible music production tools: a practical guide for screen reader and keyboard users

Most music software was designed around one assumption: that you can see a screen full of tiny knobs and drag them with a mouse. Plenty of musicians can't, or would rather not. Blind and low-vision producers, people with motor impairments, and people with repetitive strain injury all need a way to make records that does not depend on precise pointing.

The good news is that this is no longer a fringe workaround. There are now two mainstream routes into a full digital audio workstation (DAW) using a screen reader and the keyboard, and both are mature enough to finish real releases. This guide explains what they are, what each still cannot do, and how to set up a first session. It is aimed at beginners and intermediate producers, and at sighted producers who work with, teach or collaborate with disabled artists.

The building blocks: screen readers and keyboard focus

A screen reader turns what is on screen into speech or braille. On a Mac and on iPhone and iPad, the built-in one is VoiceOver; Apple describes it as a screen reader that tells you what is on your screen "audibly, in braille, or both". On Windows, the free NVDA and the built-in Narrator are common choices.

A screen reader can only read what an application exposes to it. A plug-in window that draws its own custom knobs as pictures is often silent: the reader sees nothing to announce. That single fact explains most of the frustration in accessible production. The DAW itself may be fine; the third-party synth you just loaded may not be.

So when you judge a tool, ask two questions. Can I reach every control from the keyboard? And does the screen reader announce what that control is and what value it has?

Route 1: REAPER with OSARA

REAPER is a full-featured DAW from Cockos. On its own it is not especially friendly to screen readers. What changes that is OSARA, an extension whose stated aim is to "make REAPER accessible to screen reader users".

The key facts, from the project's own page:

• It runs on Windows and Mac.
• Its developers test with NVDA and VoiceOver. On Windows it uses the standard MSAA and UI Automation interfaces, so it should work with other screen readers that support them properly.
• It is free and open source, licensed under the GNU General Public License version 2.0, with its source on GitHub.

REAPER itself gives you 60 days of full-function evaluation. After that, a discounted licence costs $60 (for personal use, or businesses grossing under $20,000 a year) and a commercial licence costs $225, before local taxes.

What it is good for. REAPER is extremely customisable: almost every action can be bound to a key, and its action list is searchable. That suits keyboard-first work. Because OSARA is open source and has been around for years, there is a large body of user-written key maps, tutorials and community help.

Where it bites. The burden of learning is real. You are learning a deep DAW, an extension and a set of key commands all at once. Expect the first few weeks to be about navigation rather than music.

Route 2: Ableton Live 12

With Live 12, Ableton built screen reader support into the product itself. Its reference manual says Live 12 "offers new accessibility features on both macOS and Windows", working with screen readers that use each system's native accessibility protocols, and that most of Live's views, controls and devices can be used with one.

The practical setup steps, from the same manual:

1. Turn on Use Tab Key to Move Focus (in the Navigate menu or Display & Input settings).
2. Use Tab and Shift+Tab to move between controls, and the arrow keys to move around views such as Session and Arrangement.
3. Jump straight to individual views with Alt+1 to Alt+7 on Windows, or Option+1 to Option+7 on Mac (the Control Bar is Alt+0 or Option+0).
4. Open the Navigate menu with Alt+N on Windows, or VoiceOver+M then N on Mac.

Where it bites. Ableton is unusually candid about the gaps. The manual lists as not yet supported for screen readers: browser tagging and filters, MPE editing in Clip View, Max for Live, and some third-party plug-ins. Some device features (such as Wavetable's modulation matrix) are not optimised, and control surface support varies by manufacturer.

Which should you choose?

• You want the deepest keyboard control and a cheap licence: REAPER with OSARA. It rewards patience.
• You want clip-based, loop-driven production or your collaborators already use Live: Live 12. Sharing projects with sighted collaborators in the same DAW removes a lot of friction.
• You are not sure: try both. REAPER's 60-day evaluation is full-function, so you lose nothing by starting there.

Whichever you pick, the same habits help.

Habits that make any setup work

Audit plug-ins before you buy. Load the demo, close your eyes or unplug the mouse, and try to change three parameters. If the reader stays silent, that plug-in will cost you time on every session. Stock plug-ins from the DAW maker are usually the safest bet.

Use hardware for continuous controls. Turning a knob on a MIDI controller is easier than nudging a value with arrow keys, and it gives you physical feedback. Our MIDI controller basics covers mapping. Check controller support with your screen reader before buying, since Ableton notes it varies by manufacturer.

Keep sessions small and named. Name every track and bus as you create it. "Audio 7" is meaningless when it is read aloud. Use consistent names across projects so your ears learn the layout. Our guide to bus processing and groups helps keep track counts down.

Set latency once. Speech output adds load. Pick a buffer size that is stable before you start recording; see latency and buffer size.

For motor access, think in key commands. If pointing is hard, the same keyboard-focus features that help screen reader users help you. Bind your ten most frequent actions to single keys and you remove most mouse work.

What we think

The industry tends to treat accessibility as a feature list to tick. The more useful way to see it is that the DAW is no longer the weak link: plug-ins are. Both REAPER and Live can now be driven without sight, but a blind producer still has to vet every third-party instrument by trial and error, because plug-in makers rarely say whether their interfaces work with a screen reader.

That is fixable, and cheaply. We think plug-in developers should publish a plain accessibility statement on every product page, as Ableton has done in its manual, including what does not work. And we think buyers, disabled or not, should ask for it. Ableton's list of unsupported features is more useful than any marketing claim, precisely because it is honest. If more of the industry wrote that kind of list, accessible production would stop being a research project and start being a purchase decision.