Narrator for Windows

A practical guide to Narrator on Windows for desktop web apps, Edge-focused baseline checks, scan mode, forms, tables, dynamic updates, and careful reporting.

This guide covers Narrator for Windows web testing. Full Windows app workflows, Office-specific tasks, touch, braille, image description features, and voice access are outside this basic section.

Orientation

Narrator uses a Narrator key with other keys. Caps Lock and Insert serve as the Narrator key by default. Reports should state the Windows version, browser, keyboard layout, and whether scan mode was active when a result depends on commands.

Scan mode

In web content, scan mode lets users move through headings, links, form fields, tables, and other structures. A defect can appear as missing structure, unexpected mode changes, unclear focus movement, or an action that works only after a manual scan-mode toggle.

Why usage context matters

Narrator is native to Windows, which makes it easy to start and useful for baseline checks. That convenience should be balanced against user evidence: WebAIM's 2024 survey reported Narrator as the primary desktop or laptop screen reader for only 0.7% of respondents, far below JAWS and NVDA.

Browser combinations

Narrator is commonly associated with Microsoft Edge, but teams may also check relevant Windows browser combinations when support commitments or user evidence require it. Record the browser and version instead of reporting a generic Windows result.

Product-team implications

Check headings, landmarks, link purpose, form labels, errors, tables, focus movement, live updates, custom widgets, keyboard traps, and whether task instructions remain available while scan mode and interaction paths change.

Practical route

Run one realistic desktop web task. Start at the page heading, move by headings and landmarks, enter a form, trigger and recover from an error, operate one custom control, inspect any table or list structure, and confirm the final status message.