Orientation
JAWS uses a JAWS key with other keys. Insert is common in desktop layout and Caps Lock is common in laptop layout. Because keyboard layout and settings can vary, reports should state the layout and browser before describing a command result.
Virtual cursor and forms
In web pages, JAWS users often read with the virtual cursor and use quick navigation keys to move through structure. Forms and application widgets introduce a different interaction path, so tests should check both discovery and operation.
Browser combinations
JAWS is commonly used with Edge, Chrome, and Firefox. A product can pass in one browser and fail in another because the browser, accessibility tree, scripts, and screen reader interpretation all contribute to the result.
Product-team implications
Check headings, landmarks, link purpose, form labels, required and invalid states, error recovery, table headers, dialogs, focus return, keyboard traps, live updates, and custom widgets that may need native semantics or established ARIA patterns.
Enterprise constraints
Some teams encounter JAWS through managed licences, locked-down browser versions, or line-of-business applications. Record those constraints and avoid generalising from a single internal machine.
Practical route
Run one realistic Windows web task. Use quick navigation to find the main page structure, open element lists where useful, complete a form, trigger and recover from an error, operate one custom component, check any table context, and confirm the final status message.