JAWS Scripts For Winlink Express
Doug Lee
Last Revised September, 2025
This document describes the JAWS scripts for Winlink Express and provides
tips for using this application with JAWS.
This document can be opened from within the application via a double press
of JAWSKey+F1 (or Insert+F1)
when the scripts are running.
Table of Contents
System Requirements For JAWS Users
In addition to any system requirements for the application, the following
apply for JAWS users:
- The computer should be running Windows 10 or later.
Older Windows versions may also work but have not been tested.
- JAWS 2018 or later should be used. The scripts will not work with or install into older JAWS versions.
Script Installation Instructions
To install these scripts on a new system:
- Install JAWS if this has not already been done. This will require
administrative privileges on the computer.
- 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.
- 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.
- 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 incorporate commands that consist of sequences of keystrokes, all beginning with a common prefix, or "command keystroke."
This approach allows many script commands without the risk of conflicting with application keystrokes.
See the "Multi-Key Command Sequences" section of the "Common Script Elements" document for further details, including
how to explore the available script commands (similar to exploring a menu system),
and how to change the Command keystroke if necessary.
By default, the Command keystroke for these scripts is [.
This document may refer to this keystroke as [ or Command;
so, for example, [ Tab and Command Tab both refer to typing the prefix keystroke, then separately the Tab key.
Some sequences may consist of more than two keystrokes, or "levels"; for example, [ d r would refer to typing [, then d, then finally r.
Script Commands and Features
These scripts provide the following commands and features beyond those provided by JAWS and the application:
- Tab will reach the license text box on the initial License Agreement screen.
- The JAWS command for reading the bottom or status line of a screen, JAWSKey+PgDn, reads the
status bar for this application when the main screen has focus.
- JAWSKey+F8 or Insert+F8, or the key sequence [ B, brings up a list of
toolbar items for activation.
- Some screens,
notably the initial data entry screen required on first application launch,
have custom tab orders and field announcement features. For a screen coded in this way:
- The tab order is controlled by the scripts rather than by the application, to make sure that all fields
are reachable.
- Some fields may be better named, and some will speak hint or further explanation material after the normal
field announcement.
- The Accent key above Tab (`) acts like an alternate tab key, moving through fields
by searching for them rather than by following the application's native tab order. This tends to find fields
that were left out of the application's tab order, though the order of fields is likely to be somewhat
peculiar.
This feature is included in case the application is updated and new fields are not otherwise reachable from
the keyboard.
Shift with this key moves in the opposite direction, just as Shift+Tab does with the
application's native tab order.
- Many fields report their names correctly.
- JAWSKey+Q, along with announcing the active configuration name, will announce the revision number of these scripts.
- Insert+F1, typed twice in quick succession, opens this document in the default browser.
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.
The initial License Agreement screen's tab order is fixed by these scripts so that the license text itself
is tabbable, but the JAWS "Say All" command (Insert+Down) does not work in this text box.
A workaround is to use Ctrl+A then Ctrl+C to place the entire text on the clipboard,
then paste it into Notepad or a similar application for easier reading.
The "Additional Data" field on the initial Properties screen does not speak its name when reached via
Tab or Shift+Tab. Use Insert+Tab to read the field name.
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 28, released September 10, 2025, tested against application version 1.7.26.0
- This is a FlexStable release that may
change over time to accommodate more fixes and features until this notice is removed.
- The tab order on the initial License Agreement screen includes the license text box.
- JAWSKey+PgDn reads the status bar.
- JAWSKey+F8 or Insert+F8, or the key sequence [ B, brings up a list of
toolbar items for activation.
- Some screens have custom tab orders and field announcement.
- Field naming is more efficient.
- The Accent key (`) provides an alternate path through fields that catches
fields not in the application's native tab order.
Shift with this command moves in the opposite direction.
Revision 6, released June 21, 2022, tested against application version 1.6.4.0