Custom JAWS Scripts For Dixa
Doug Lee
Last Revised December, 2019

This document describes the custom scripts for Dixa and provides tips for using this application with JAWS. This document and the scripts cover the Dixa app, not the Dixa website interface.

This document can be opened from within the application via a double press of JAWSKey+F1 (or Insert+F1) when the scripts are running.

This document is laid out for easy navigation using JAWS HTML heading navigation commands: h will move through all headings, 2 through major sections, and 3 and 4 through any subsections and subsubsections.

Table of Contents

System Requirements For JAWS Users

In addition to any system requirements for the application, the following apply for JAWS users:

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 installer for these scripts; 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 Insert+q from within the application. 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. In some cases, restarting JAWS may fix this issue.

Key Sequences

These scripts may incorporate commands that consist of sequences of keystrokes, all beginning with a common prefix, or "command key." This approach allows many script commands without conflicting with application keystrokes. By default, the command key is the left bracket ([) key; see below for how to change it if necessary. This document may refer to this key as [ or Command; so, for example, [ Tab and Command Tab both refer to typing the prefix key, then separately the Tab key. Some sequences may consist of more than two keys, or "levels"; for example, [ d r would refer to typing [, then d, then finally r.

In addition to the commands documented elsewhere, the following commands are also available, at any level, for exploring what script commands are available for this application:

If you need to change the command key, type the current command key followed by either JAWSKey+c or Insert+c. An edit box will appear into which you may type your desired command key. The current key will initially appear in the box. Then Type or spell out your desired command key and press Enter to apply the change. If the keystroke requires modifiers like Shift or Ctrl, spell those out; do not simply type, for example, A when you mean shift+a. Example keystrokes exactly as they should be typed:

Warning: If you accidentally set the command key to something you cannot type, you will currently need to edit it in these scripts' .jcf file in the JAWS user directory under the MKCSOptions section.

Script Commands and Features

These scripts provide the following commands beyond those provided by the application itself:

These scripts also provide the following features:

Tips For Using This Application With JAWS and the Scripts

To change availability between Away and Working:

To change the phone status between Gray and Green:

Known Issues

The following issues are known and may be encountered during use of the application with these JAWS scripts. These issues may be fixed in a future update to the scripts or to the application itself.

There is currently no known way to close the application from the keyboard. Alt+F4 and Ctrl+w migrate the application to the Windows system tray rather than exiting. See also the next item. Use the Windows Task Manager to shut down the application as needed.

The system tray menu for this application is not accessible:

Braille support is not well tested and is likely incomplete.

Revision History

This is the revision history of these scripts, most recent revision first:

Revision 38, December 30, 2019, tested against application version

Revision 36, December 24, 2019, tested against application version