From Audacity Manual
- Technical support for visually impaired users is provided on the audacity4blind mailing list.
A large number of keyboard shortcuts are available for those who can't use a mouse, and for those who find it quicker to use the keyboard. These keyboard shortcuts are described throughout the manual, and in the Keyboard Shortcut Reference. They can be customized on the Keyboard page of the Preferences dialog.
Parts of Audacity which are not fully accessible using the keyboard include:
- Clips: An audio track can contain any number of clips – sections of audio data that can be manipulated independently. If a track contains more than one clip, there is no way of moving easily through the clips using the keyboard. For example, there isn't a keyboard shortcut to move to the beginning of the next clip.
- Time Tracks: These can control the speed of audio tracks in a very flexible manner.
- Tools Toolbar: Only Selection Tool can be worked with using the keyboard.
The following methods of keyboard navigation which are standard on Windows and Linux work differently on Mac OS X.
- ALT key navigation of menus and buttons is not supported by Apple. To access menus, hold CTRL and press F2 then type the first few letters of the root menu item, then type the first few letters of the item required in that menu.
- Tabbing between buttons in dialogs is off by default. Tabbing can be enabled by opening the System Keyboard Preferences, choose the "Keyboard Shortcuts" tab, then under "Full Keyboard Access", choose the radio button "All controls".
Large parts of Audacity are accessible to users of screen readers on Windows or Mac, but unfortunately this isn't the case on Linux. The accessibility on Windows and on Mac is outlined in the next two sections.
On Windows Audacity is known to work well with the Jaws, Window-Eyes and NVDA screen readers. There is a Jaws Guide to Audacity, most of which is also applicable to users of Window-Eyes and NVDA.
The following parts of Audacity are not accessible to users of screen readers on Windows:
- Label Tracks: These contain labels for times and/or time ranges. If you Tab through a label track, then the labels are not read by any of the screen readers. However, it is possible to work around this using the Edit Labels dialog, which is opened on the Tracks menu.
- Clips: As noted above, there's no way of moving easily through the clips in a track using the keyboard.
- Time Tracks
On Mac OS X
The following parts of Audacity are either not accessible or have accessibility issues for users of VoiceOver on Mac:
- As in the case of Windows: Label Tracks, Clips, and Time Tracks.
- Metadata Editor
- Edit labels dialog, which is opened on the Tracks menu.
- The input and output sliders in the Toolbars. As an alternative, on Mac laptops with integrated keyboards you can adjust the output volume using function keys (F11 and F12 on recent models, F3, F4 or F5 on G3 and G4 machines) - read this page for help. In addition you can adjust the input volume on the Input tab of the Sound Window of System Preferences.
- When you change whether a track is selected, solo or mute, VoiceOver does not automatically read out the new state of the track. However, provided you are interacting with the scroll area, you can manually read this by pressing VO-W, or VO-A, or VO-S, or VO-L.
- The edit-spinbox controls which are used for example in Selection Toolbar for Selection Start and Selection End/Length are only partially accessible.
- When you move to one of these controls, VoiceOver reads out the time. However, when you move between the digits using the left and right arrow keys, or change the time using the up and down arrow keys or typing in digits, then VoiceOver does not give any feedback. You can manually read the time by pressing VO-W.
- When you TAB forwards from Audio Position, the "Selection End" or "Selection Length" radio button is read as "Selection Start". When you use COMMAND + F6 or COMMAND + SHIFT + F6 to move directly into "Selection End" from another toolbar, the button is read as "Selection Start".
- For VoiceOver to read any minus sign or decimal point in a text box, then in VoiceOver's verbosity settings, punctuation should be set to All. Note than when this is set, VoiceOver reads a minus sign as a dash.