JAWS Scripting: Better Support for JAWS Screen Reader Users

For people who are blind or have low vision, workplace software should be a productivity aid, not a barrier. An essential part of workplace technology is assistive technology, such as the JAWS Screen Reader.

What is the JAWS Screen Reader?

JAWS (Job Access With Speech) is the leading screen reader software that automatically outputs digital content in speech. JAWS allows users to access, navigate and interact with digital content using keyboard commands, making it an essential tool for productivity at work and beyond.

Screen readers work best with digital content and applications that are designed with accessibility in mind. However, many workplace applications still present accessibility and usability challenges that can hinder screen reader users.

While fixing the root issues is always the best approach, that’s not always possible – especially when it’s an application provided by a third party or when it’s an internal application that you don’t have the time or expertise to fix. In that case, it might be time to consider JAWS Scripting as part of your accessibility strategy.

This article provides more details on how JAWS Scripting can help make the digital workplace more inclusive for screen reader users and help employees who are JAWS users be more productive.

What Are JAWS Scripts?

When JAWS encounters inaccessible content, it tries to interpret that content and fill in accessibility gaps by making best guesses, but this approach isn’t always accurate and sometimes can’t work. JAWS scripts provide an alternative approach.

JAWS scripts are custom instructions written in JAWS’ scripting language to improve accessibility and efficiency by addressing specific usability challenges. JAWS scripts are installed and run locally on a JAWS user’s machine, and work with specific application.

When Should You Use JAWS Scripts?

JAWS scripts are required when JAWS users need to use software or digital content that cannot be made accessible through remediation. This often happens with third-party applications where only the vendor can modify the code. It can also occur with legacy internal applications where there is no in-house expertise or capacity for making accessibility fixes.

In some cases, upgrades to a previously accessible application introduce severe accessibility regressions, making it difficult or impossible for screen reader users to use the application. When remediation isn’t an option, JAWS scripts provide a way to improve accessibility and usability.

JAWS scripts can be written to provide a wide range of actions, such as:

  • Providing details about a custom control’s purpose, type, and current state when the underlying code lacks this information.
  • Defining keyboard shortcuts to move the focus to different content areas of a complex screen.
  • Making it possible to use a keyboard to open and interact with a menu that was developed only to be operated using a mouse.
  • Announcing the presence of search suggestions, error messages, or other information that is visually displayed when the user interacts with a control.

What Does the Typical JAWS Scripting Journey Entail?

Contact us as soon as you discover, or suspect JAWS users are having difficulty using a Windows-based software application. This can be any Windows desktop software or web application, such as a customer relationship management system, softphone, or Human Resources tool.

When TPGi provides JAWS scripting, we go through a standard process of several stages.

1. Defining the Problem

TPGi’s experts will have several conversations with your team and, ideally, with the JAWS user(s), to learn more about the technical details of the application, including whether any existing scripts are available that may need replacing or updating.

From a user perspective, we’ll seek to understand which parts of the application the user needs to interact with and for what purpose. We’ll find out whether any existing scripts are in place that may need updating or replacing. We’ll use this information to gather a technical understanding of how the application is built and create a prioritized list of issues to investigate.

2. Accessing and Analyzing the Application

Once we finalize the scripting plan, we begin interacting with the inaccessible application and analyzing what is causing the issues. To do this, we’ll need access to the application. The most feasible approach may be dictated by security and other constraints. Some options include remotely accessing the application, working on a laptop that you send us with the software installed, or, if necessary, we can travel to your premises to do our work on-site.

3. Writing and Testing Scripts

Once we understand the cause of each individual problem and the extent to which we can address the problem through JAWS scripting, we’ll write scripts to overcome the issue. This is an iterative process, so we work closely with your JAWS users to make sure the scripts behave as expected in their environment and provide genuine help. We’ll make tweaks where necessary to improve performance.

4. Delivering Scripts and Documentation

Finally, we’ll provide your team with the scripts and information explaining how to install and use them. We’ll also provide training to help JAWS users make the best use of the scripts.

Supporting JAWS Users: Scripting as a Solution for Inaccessible Software Challenges

In an ideal world, all software applications and digital content would be accessible, and JAWS scripting would not be needed. Given that scripting is an attempt to compensate for inaccessible software, there are situations where the complexity of the application and its accessibility issues may make full fixes with scripting a very challenging task.

But until we have born-accessible software, JAWS Scripting can play an important part in providing inclusive employment for people who are blind or have low vision, making it possible for them to do their work, earn a living, and flourish in the workplace.

Have questions? Schedule a call and speak with a scripting expert today!

Categories: Accessibility Strategy, Business
Tags: , , , ,

About David Sloan

David Sloan is Vispero's Chief Accessibility Officer and Manager of TPGi's User Experience Practice. He joined the company in 2013, after nearly 14 years as an accessibility researcher, consultant and instructor at the University of Dundee in Scotland.