JAWS

JAWS — Job Access With Speech — is the longest-running commercial screen reader still in active use. Originally released in 1995 by Henter-Joyce (now Freedom Scientific, part of Vispero), JAWS has been the historical market leader in enterprise screen-reader use for roughly three decades.

Where JAWS sits in the ecosystem

The WebAIM Screen Reader User Survey has consistently shown JAWS in the top two desktop screen readers globally, with NVDA close behind. Among users employed in enterprise jobs (government, finance, education), JAWS’s share is meaningfully higher than its overall share — historically because the licence cost was paid by the employer.

JAWS runs only on Windows and pairs most commonly with Chrome or Edge, though Firefox support is solid. It does not run on macOS or Linux; VoiceOver and Orca cover those platforms respectively.

Pricing and access

JAWS is sold by Freedom Scientific on three tiers:

• Home Annual — roughly $90 USD per year. Discounted from the perpetual licence on the explicit premise that home users will upgrade through annual updates rather than buy outright.
• Home Perpetual — historically around $1,100 USD with annual Software Maintenance Agreement (SMA) fees of roughly $200 to continue receiving updates.
• Professional / Enterprise — used in workplaces and educational institutions, typically $1,200+ USD with annual SMA, often paid by employer or vocational-rehabilitation programme.

For users in regions where Freedom Scientific does not maintain strong distribution or where the price is prohibitive, NVDA is the practical alternative — its free-and-open-source status is the single biggest reason NVDA closed the market-share gap with JAWS over the past decade.

ARIA support and quirks

JAWS has the longest ARIA-implementation history of any commercial screen reader, and consequently has accumulated some quirks that developers learn to test against:

• Verbosity defaults. JAWS announces a lot by default — role, state, and sometimes redundant attributes. Users adjust verbosity per their preference; developers should not assume any specific verbosity setting in testing.
• Live regions. JAWS handles aria-live="polite" reliably. aria-live="assertive" is interrupt-driven and should be used sparingly; JAWS surfaces the most aggressive interruption behaviour of the major screen readers.
• Reading modes. JAWS toggles between virtual cursor mode (for reading static content like web pages, where arrow keys move through the rendered text) and forms mode / application mode (for filling forms or interacting with custom widgets, where keystrokes reach the page). Mode switching is partially automatic, partially user-controlled, and a frequent source of bugs in complex widgets.

Cross-pairing testing

For accessibility QA work that needs to cover JAWS specifically, the common pairings are:

• JAWS + Chrome — most common in enterprise.
• JAWS + Edge — increasingly common on Windows 11 deployments.
• JAWS + Firefox — historically the developer-favoured pairing for spec compliance; less common in the general user base.

A reasonable cross-screen-reader test plan covers at least one JAWS pairing alongside NVDA + Firefox and VoiceOver + Safari.