Using the JAWS Scripts For Audible
Doug Lee
Last Revised September, 2019

This Guide provides tips for using Audible for Windows 10 (Audible) with JAWS For Windows and these scripts. When the scripts are installed and Audible is open and focused, this document can be opened via a double press of JAWSKey+F1 (or Insert+F1).

Table of Contents

System Requirements For JAWS Users

For correct operation with Audible, these scripts require JAWS 18.0 or greater. (JAWS versions prior to 18.0 do not support scripting Universal Windows Platform (UWP) applications.

These scripts were written against the following Audible app versions, most recent first. As a rule, script features are more likely to function as expected with newer versions listed below than with older ones.

Audible VersionDate First Tested 28, 2019 22, 2019 11, 2018

Script Installation Instructions

To install these scripts on a new system:

  1. Load JAWS if this has not already been done. This will require administrative privileges on the computer.
  2. Run JAWS as the user for whom the scripts are to be installed. This and the following steps must be performed for each user of the computer who will be using JAWS with these scripts.
  3. Download and run, or run directly, the JAWS scripts for Audible, and follow the on-screen directions. Be sure to install the scripts in the currently running JAWS version if a JAWS version list is presented.
  4. To verify successful installation, type Ins+Q while Audible is in focus. Part of the JAWS spoken response should be a revision number. If you do not hear a revision number, the scripts are not correctly loaded.

Using Audible With JAWS and the Scripts

This section and its subsections provide tips for using Audible with JAWS and these scripts.

JAWS Script Commands and Features

Audible script commands are key sequences rather than multi-key combinations. This is to avoid collisions between script commands and native application keystrokes. All such key sequences start with a common prefix key, a left bracket ([) by default. Users can change the prefix key if necessary by typing [ followed by JAWSKey+C or Ins+C. The change will survive across script and JAWS updates. In this document, the prefix key will be called Command; thus, by default, Command d means type [ followed by d.

The scripts provide the following commands:

The scripts also provide the following features:

Native Keyboard Shortcuts

Audible supports a number of keyboard shortcuts. To display a list of these

  1. Activate the Help screen, such as by selecting "Help" from the Command t page list.
  2. Arrow to and press Enter on the "Keyboard Shortcuts" entry in the list that appears.
  3. Use the scripted command sequence Command v to virtualize the screen. This will place the keyboard shortcut list in a JAWS virtual view. Press Esc to close this view when finished reading.

The following outline shows the keyboard shortcuts supported as of Audible for Windows 10 version (July, 2019):

* The number of seconds to jump forward and backward via these keystrokes, and via their corresponding buttons, can be configured on the Playback page in Settings.

Useful Tips

If script commands seem not to work, use Ins+Q to check whether JAWS has loaded the Microsoft Edge scripts in order to handle embedded web content. If this happens, use Ctrl+Tab or Ctrl+Shift+Tab to move focus out of the web content area and thus re-enable the commands provided by these Audible scripts.

When a file or stream is playing or paused, Space from most anywhere in the application will play/pause rather than acting on the focused control. Use Enter to press buttons etc.

In the Library list, there are two alternative views: List and Grid. Both work with JAWS and the scripts, but the List view shows more information about each entry in the library.

The standard Ins+B JAWS command for reading a dialog is useful for reading popups in this application. However, it may sometimes be more efficient to use the sequence Command v to show the screen text in a JAWS virtual view. The "Book Details" display is an good example.

Navigation among items in some lists requires use of Left and Right arrows rather than Up and Down arrows. Using Up and Down may work but may miss items in the list. The Library list is an example.

Navigation among pages such as Search and Library require use of Tab and Shift+Tab even though the items are rendered to screen readers as list items. As an alternative, use the scripted command sequence Command t to pick a page from a JAWS popup list.

When changing the narration speed in the full player, press Enter on the Narration Speed button, use arrows to change, then use Esc (not Enter) to return to the player.

If Tab from an episode list in a book or channel does not reach the Play/Pause button, move up and down in the list and then Tab again. Enter should also work without requiring direct focus on the button.

Known Issues

Issues shown in this section may be fixed in future script and/or Audible revisions but are not addressed as of this writing.

Changing the sort order of the Library list may sometimes cause the list itself to become unreachable via Tab and Shift+Tab until the sort order is changed back.

Some screens include points in the tab order that say nothing, because for those points, Audible does not indicate any location of focus.

Some button names appear oddly in Braille at this time.

The currently playing book title is not available to JAWS in the full player, though it is in the compact player and the player that overlays other screens. This is because, in the full player, the book title appears as part of an image of the book's cover art.

JAWS may sometimes say "checked" as you arrow through the Library list. This is caused by a Zoom control that contains the list.

Revision History

This section presents the revision history of these scripts, most recent revision first.

Revision 55, September 20, 2019
Revision 44, September 15, 2019
Revision 21, August 12, 2018
Revision 17, August 11, 2018
First test revision released for public inspection. Thanks to Jessica McKenzie for visual assistance and to Jessica Hodges for help using the app.