Course progress: 0 / 20 lessons

LESSON 12 OF 20

JAWS

JAWS is a commercial Windows screen reader used widely in professional, enterprise, education, and government settings. It is an important Windows web-testing reference when those audiences or procurement environments matter.

  • Reading: about 3 minutes
  • Knowledge check: 2-3 minutes
  • Platform guide and cheat sheet are optional

This reference assumes that you have completed the foundation course and understand names, roles, states, focus, and dynamic updates.

Choose an environment

Keyboard

Windows

A practical guide to JAWS on Windows for desktop web apps, enterprise browser testing, virtual cursor navigation, forms, tables, custom widgets, and reproducible reporting.

What JAWS testing depends on

Virtual PC cursor

JAWS commonly presents web pages through a virtual cursor model for reading and quick navigation, with separate interaction behaviour for forms and application widgets.

Quick navigation keys

Single-letter commands and element lists help users move by headings, links, forms, tables, buttons, landmarks, and other page structures.

Enterprise context

JAWS is often encountered with Windows, Microsoft Office, Google Workspace, enterprise web apps, line-of-business software, and managed device policies.

Configuration and licence context

JAWS version, keyboard layout, browser, verbosity, scripts, settings, and whether Fusion or ZoomText is involved can all affect testing evidence.

One reader, several Windows work contexts

EnvironmentPrimary inputWhat shapes the experience
WindowsKeyboardDesktop web apps, enterprise workflows, virtual cursor navigation, forms, element lists, tables, and browser-specific behaviour

TRY THIS NOW

Account for enterprise Windows use

Choose one Windows web flow where JAWS is relevant and record what makes the environment specific.

  1. AudienceIdentify whether enterprise, education, government, or professional users make JAWS important.
  2. ConfigurationRecord JAWS version, browser, keyboard layout, scripts, and managed-device constraints.
  3. NavigationUse quick navigation and element lists before judging page structure.
  4. InteractionCheck forms, custom widgets, tables, dialogs, live updates, and recovery paths.

What product teams should take from this

  • JAWS should be added when Windows enterprise, education, public-sector, or professional assistive-technology use is in scope.
  • Do not assume that NVDA and JAWS expose the same web-app behaviour even when the browser is the same.
  • Test quick navigation, forms mode, virtual cursor behaviour, element lists, tables, and custom widgets with a representative task.
  • User observations will be added after credited research with regular users; they are not inferred from documentation.

Editorial model reviewed 4 August 2026. Command sheets must be rechecked when Freedom Scientific changes JAWS training or keystroke references.

Knowledge check

Answer every question, then use the forward lesson button to record this lesson as complete. The check is not scored and can be repeated.

1. When is JAWS especially important to include?

2. What should JAWS testing use before judging page structure?

NEXT STEP

Continue to lesson 13: Use Narrator for Windows web testing

Move on when you are ready. Your knowledge-check answers are not stored.