Course progress: 0 / 20 lessons

LESSON 13 OF 20

Narrator

Narrator is Microsoft's built-in Windows screen reader. It is useful for baseline Windows checks because it requires no installation, but WebAIM's 2024 survey reported Narrator as the primary desktop or laptop screen reader for only 0.7% of respondents.

  • 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 Narrator on Windows for desktop web apps, Edge-focused baseline checks, scan mode, forms, tables, dynamic updates, and careful reporting.

What Narrator testing depends on

Built-in availability

Narrator ships with Windows, so teams can use it when installing NVDA or JAWS is not possible. Availability does not make it representative of most Windows screen reader users.

Scan mode

Narrator uses scan mode for reading and navigating web pages, documents, and some apps. Scan mode affects how arrow keys, single-letter commands, and activation work.

Microsoft browser context

Narrator is especially relevant with Microsoft Edge, but browser, Windows version, settings, and web semantics still shape the result.

Usage context

WebAIM survey data shows low primary usage for Narrator compared with NVDA and JAWS. Record why it is included and avoid treating it as the only Windows test.

One reader, focused Windows baseline

EnvironmentPrimary inputWhat shapes the experience
WindowsKeyboardDesktop web apps, Microsoft Edge, scan mode, item navigation, forms, headings, landmarks, tables, and no-install baseline testing

TRY THIS NOW

Use Narrator as a scoped baseline

Choose one Windows web flow and decide what Narrator can and cannot tell you about it.

  1. RationaleRecord why a built-in Windows baseline is useful for this product or release.
  2. Usage limitNote that low primary usage means Narrator does not replace NVDA or JAWS coverage.
  3. Scan modeCheck headings, links, form fields, tables, and landmarks with scan-mode navigation.
  4. EvidenceRecord Windows build, browser, task result, focus movement, announcements, and recovery.

What product teams should take from this

  • Narrator is useful for a no-install Windows baseline and for products that explicitly support built-in assistive technology.
  • Because reported primary usage is low, Narrator should not replace NVDA or JAWS when Windows screen reader users are in scope.
  • Test scan-mode reading, focus movement, headings, landmarks, forms, tables, dynamic updates, and recovery in a representative web 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 Microsoft changes Narrator guidance or Windows releases.

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. How should a team treat Narrator in Windows web testing?

2. What should a Narrator report include when scan mode affects the result?

NEXT STEP

Continue to Part 3: Interface patterns

Connect screen-reader concepts to structure, forms, updates, controls, navigation, and complex widgets.