Overview

Narrator is Microsoft's built-in screen reader that enables users who are blind or have low vision to interact with applications using speech output and keyboard navigation. Accessibility testing with Narrator helps verify that application content, controls, and workflows can be understood and operated without relying on visual cues.

Purpose

Use Narrator to:

• Verify that content is announced correctly.
• Confirm that interactive elements are keyboard accessible.
• Validate accessible names, labels, and instructions.
• Ensure proper reading order and navigation.
• Identify screen reader usability issues.
• Support WCAG accessibility compliance testing.

Prerequisites

Before testing:

• Use a Windows 11 device.
• Have a keyboard available for navigation.
• Close unnecessary applications that may interfere with Narrator announcements and focus.

Relevant Web Content Accessibility Guidelines (WCAG) Success Criteria

Narrator testing helps validate compliance with several WCAG requirements including:

• 1.1.1 Non-text Content - Images have meaningful alternative text
• 1.3.1 Info and Relationships - Structure and relationships are programmatically determined
• 1.3.2 Meaningful Sequence - Content is presented in a logical reading order
• 2.1.1 Keyboard - All functionality is available from a keyboard
• 2.4.3 Focus Order - Focus moves in a meaningful order
• 2.4.6 Headings and Labels - Headings and labels describe purpose
• 2.4.7 Focus Visible - Keyboard focus is visible
• 3.3.2 Labels or Instructions - Inputs include appropriate labels
• 4.1.2 Name, Role, Value - User interface components expose accessible information

Back to Top

Starting Narrator

Method 1: Keyboard Shortcut

1. Press: Ctrl + Windows Key + Enter to start Narrator automatically.

Method 2: Windows Settings

1. Open Settings
2. Select Accessibility
3. Select Narrator
4. Turn Narrator on

Back to Top

Basic Narrator Commands

⚠️ Note: The Narrator key is typically the Caps Lock key or Insert key.

Test your page by pressing the Tab key to navigate through it. You should be able to reach every button, link, and form field sequentially.

• Visual focus - The element currently selected by the keyboard should always have a clearly visible highlight or outline around it so the user knows where they are.
• No keyboard traps - Users should never get stuck in one part of the page (such as a dropdown menu or video player) and be unable to move on using only the keyboard.

⚠️ Important: Nothing on the page should require a mouse.

Back to Top

Accessibility Testing Procedure

Step 1: Verify Page or Screen Loading

1. Navigate to the screen being testing.
2. Confirm Narrator announces:
   • Screen Title
   • Page Heading
   • Initial focus location
3. Expected Results: Users should immediately understand:
   • Where they are
   • What screen is displayed
   • What action can be performed next

Step 2: Test Keyboard Navigation

1. Using only the keyboard:
   1. Press Tab repeatedly.
   2. Navigate through all interactive elements.
   3. Use Shift + Tab to move backward.
2. Verify:
   • All controls receive focus
   • Focus order is logical
   • Narrator announces each element
3. Expected Results: All functionality must be operable without a mouse.

Step 3: Verify Accessible Names

1. Move focus to:
   • Buttons
   • Links
   • Icons
   • Form controls
2. Expected Results: Controls should have descriptive names that communicate purpose.

Important: Be sure to listen to Narrator announcements.

Step 4: Verify Form Fields

1. Navigate to all input fields. Confirm Narrator announces:
   • Label
   • Control type
   • Required status (if applicable)
2. Expected Results: Users must understand the purpose of each field.

Step 5: Verify Images and Icons

1. Navigate to images and icon-based controls. Confirm Narrator announces:
   • Meaningful alternative text for information images
   • Appropriate labels for icon buttons
2. Expected Results: Non-text content should convey equivalent meaning.

Step 6: Verify Heading and Structure

1. Navigate through content using Narrator reading commands. Verify:
   • Headings are announced correctly
   • Heading hierarchy is logical
   • Sections are easy to understand
2. Expected Results: Users can understand content organization without visual cues.

Step 7: Verify Reading Order

1. Use Narrator's continuous reading feature. Listen to the order content as it is announced. Verify:
   • Content follows a logical sequence
   • Instructions are announced before controls
   • Labels are read before form fields
2. Expected Results: The reading order matches the intended visual and functional experience.

Step 8: Verify Error Messages

1. Trigger validation errors. Confirm Narrator announces:
   • Error messages
   • Validation instructions
   • Error status
2. Expected Results: Users should immediately understand:
   • What went wrong
   • Which field contains the error
   • How to fix it

Step 9: Verify Dynamic Content

1. Verify Narrator announces changes automatically:
   • Pop-up dialogs
   • Notifications
   • Toast messages
   • Modal windows
   • Expanding menus
2. Expected Results: Users are informed when content changes without moving focus.

Step 10: Verify Focus Indicators

1. While navigating by keyboard, confirm:
   • Focus remains visible
   • Focus is not trapped
   • Focus moves predictably
2. Expected Results: Users can always determine their current location within the interface.

Best Practices

• Perform testing using only the keyboard.
• Listen to all Narrator announcements without relying on visual information.
• Test every user workflow from start to finish.
• Validate accessibility in all supported browsers and application views.

See Also

• Microsoft Narrator Support Article (open in a new tab)
• WebAIM Article about Narrator (Opens in a new tab)

Contact Information

For further assistance:

• Email the UAH Accessibility Mailbox
• Visit the Accessibility at UAH Website (opens in a new tab)