Skip to main content
Accessibility.com, LLC
Category: Assistive Technologies

Narrator

Also known as: Windows Narrator
Simply put

Narrator is a screen-reading application built into Windows 11 that reads aloud on-screen text and describes interface elements, helping people who are blind or have low vision use their computer. Because it comes with Windows, there is nothing to download or install to use it.

Formal definition

Narrator is Microsoft's built-in screen reader for the Windows operating system (included in Windows 11), providing spoken and braille output that conveys text, controls, and interface state to users who rely on assistive technology. It is one of several screen readers used to evaluate and interact with digital content; note that the presence or use of any single screen reader does not by itself establish WCAG conformance, and thorough accessibility testing generally involves multiple assistive technologies alongside manual review. This entry describes the software tool and should not be confused with the general literary or narrative sense of the word 'narrator'.

Why it matters

Narrator is one of the assistive technologies that people who are blind or have low vision rely on to read on-screen text and understand interface elements. Because it is built into Windows 11 with nothing to download or install, it lowers the barrier to accessing a screen reader for users who might not otherwise obtain one, and it gives developers and testers a readily available tool for checking how content behaves with spoken output.

For teams working toward accessible digital products, understanding how content is announced by a screen reader like Narrator helps surface problems that visual inspection alone cannot reveal, such as unlabeled controls, missing text alternatives, or interface state that is not conveyed to assistive technology. It is important to be clear about scope, however: the presence or use of any single screen reader does not by itself establish WCAG conformance. Automated checks and testing with one tool detect only a portion of potential issues.

Thorough accessibility evaluation generally involves multiple assistive technologies alongside manual review, since different screen readers can interpret and announce the same content differently. Treating Narrator as one input among several, rather than as a definitive measure of accessibility or legal compliance, gives a more accurate picture of the experience real users may have. This entry describes the Windows software tool and is not legal advice; requirements evolve through regulation and case law, and qualified counsel should be consulted on compliance questions.

Who it's relevant to

People who are blind or have low vision
Narrator provides spoken and braille output that lets users who cannot rely on the visual display read text and operate their computer. Because it is included with Windows 11, it is available without any separate download or installation.
Accessibility engineers and QA testers
Narrator offers a readily available screen reader for evaluating how content is announced. It should be used as one of multiple assistive technologies in testing, since a single tool detects only part of potential issues and does not on its own establish WCAG conformance.
UX designers and developers
Understanding how Narrator announces controls, text alternatives, and interface state helps teams identify labeling and coding gaps that visual review may miss, and reinforces the need to test with more than one screen reader.
Compliance officers and legal counsel
Narrator can support accessibility efforts, but use of any single screen reader does not guarantee compliance or immunity from legal claims. Conformance requirements evolve through regulation and case law, and qualified legal counsel should be consulted for specific obligations.

Inside Narrator

Built-in screen reader for Windows
Narrator is the screen reader that ships with the Microsoft Windows operating system, allowing users to operate the computer and access on-screen content through synthesized speech and, where supported, braille output.
Speech and audio output
Narrator conveys text, controls, and interface elements aloud, enabling users who are blind or have low vision to navigate applications, the desktop, and web content without relying on the visual display.
Keyboard and input navigation
Users interact with Narrator primarily through keyboard commands and modifier keys, and on touch-enabled devices through gestures, to move through elements, read content, and activate controls.
Reliance on the accessibility API
Like other screen readers, Narrator interprets application and web content through the underlying accessibility programming interfaces exposed by Windows, so the accessibility of the content it encounters depends on how that content is coded and exposed.
Assistive technology used in testing
Narrator is one of several screen readers practitioners may use when performing manual and assistive technology testing to evaluate how content behaves for users of these tools.

Common questions

Answers to the questions practitioners most commonly ask about Narrator.

Does using Narrator guarantee that a website or application is accessible?
No. Narrator is one screen reader among several, and testing with it does not guarantee an accessible experience for all users. Different assistive technologies can behave differently, and passing checks with a single tool does not confirm broad usability. Comprehensive accessibility work generally requires manual testing across multiple assistive technologies, keyboard-only testing, and evaluation against relevant WCAG success criteria. Automated checks and single-tool testing detect only a portion of potential issues.
Is Narrator the same as, or interchangeable with, other screen readers like JAWS, NVDA, or VoiceOver?
No. Narrator is Microsoft's built-in screen reader for Windows, while JAWS and NVDA are separate Windows screen readers and VoiceOver is Apple's built-in screen reader for its operating systems. Although these tools serve a similar purpose, they can differ in behavior, supported features, keyboard commands, and how they interpret content. Testing with one does not reliably predict results in another, so testing across multiple screen readers is commonly recommended.
How is Narrator typically turned on?
Narrator is included with Windows and can generally be enabled through the operating system's accessibility or ease-of-access settings, or through a keyboard shortcut. Because the specific steps and shortcuts can vary by Windows version, consult current Microsoft documentation for the version you are testing.
Where should Narrator fit into an accessibility testing process?
Narrator is often used as one part of manual screen reader testing on Windows. Because different screen readers can produce different results, it is commonly paired with testing in other tools such as NVDA or JAWS, along with keyboard-only navigation testing and evaluation against applicable WCAG success criteria. Relying on any single tool is generally not sufficient.
What kinds of issues can Narrator testing help reveal?
Screen reader testing with Narrator can help surface issues in how content is announced, whether interactive elements are reachable and operable, whether names, roles, and states are conveyed, and whether reading and focus order make sense. It does not, by itself, confirm conformance or legal compliance, and manual review of context and user experience remains important.
Does testing with Narrator satisfy legal accessibility requirements?
Testing with Narrator does not, on its own, establish legal compliance or immunity from claims. Legal obligations in the US may arise under authorities such as Title II or Title III of the ADA or Section 508, depending on the entity and context, and requirements evolve through regulation and case law. This entry is not legal advice; organizations should consult qualified legal counsel and current agency guidance regarding their specific obligations.

Common misconceptions

Testing only with Narrator confirms a page is accessible to all screen reader users.
Different screen readers can behave differently with the same content, and passing checks with one tool does not guarantee an equivalent experience across others. Practitioners generally test with more than one assistive technology and combine automated, manual, and assistive technology testing.
If Narrator can read a page, the content meets WCAG and is legally compliant.
Conformance, usability, and legal compliance are distinct. Successful reading by a screen reader does not establish conformance with WCAG success criteria, guarantee a usable experience, or provide immunity from legal claims. Automated and single-tool testing detect only a portion of potential issues.
Narrator being built into Windows means the operating system handles accessibility for developers.
Narrator can only convey what content and applications expose through the accessibility API. Poorly structured or improperly coded content may not be announced correctly regardless of the screen reader used, so responsibility for accessible implementation remains with the content and application authors.

Best practices

Include Narrator as one of several screen readers in your testing matrix rather than relying on it exclusively, since screen reader behavior can vary across tools and browsers.
Combine automated checks with manual and assistive technology testing, recognizing that automated tools detect only a portion of accessibility issues.
Verify that interface elements, controls, and content are correctly exposed through the accessibility API so that Narrator and other screen readers can announce them accurately.
Test key user flows end to end with Narrator using keyboard navigation to confirm that users can perceive, operate, and complete tasks without the visual display.
Document the Narrator version, Windows version, and browser used during testing, since results can differ across configurations and requirements evolve over time.
Treat screen reader testing as evidence of usability and conformance progress, not as proof of full WCAG conformance or legal compliance, and consult qualified legal counsel for questions about legal obligations.