Microsoft Narrator is extremely slow on webpage with Office Mix

Issue #15938604 • Assigned to Bogdan B.


Nathan A.
Feb 13, 2018
This issue is public.
Found in
  • Microsoft Edge
Found in build #
Reported by 1 person

Sign in to watch or report this issue.

Steps to reproduce

  1. Log in to Dynamics 365 for Talent by signing up for a free trial at and signing in to the application.
  2. Once it loads, click “Click here to get started” in the banner at the top. (A screenshot of this page is attached.)
  3. Turn on Microsoft Narrator and tab through the page using it.

Results: There is consistently several seconds of lag to tab through the elements in the page, making it unusable for visually impaired users. This does not repro in Chrome.


1 attachment

Comments and activity

  • Microsoft Edge Team

    Changed Assigned To to “James M.”

  • Hello,

    Thank you for providing this information about the issue. We are seeing a delay on the sample page, but after a minute Narrator is able to catch up and read each focus point instantly. This delay is also experienced in Chrome during our tests. Can you please use the Feedback Hub to collect more information?

    1. Open the Feedback Hub app on your device 
    2. Click on the “Feedback” tab 
    3. Click on the " Add new feedback" button 
    4. Click "Problem", fill in the title/details and select “Accessibility” as the category and “Narrator” as the sub-category 
    5. Under "Recreate the problem", press “Start capture” 
    6. Once the capture has started, run through the steps required to reproduce your issue 
    7. Click “Stop capture” back in the Feedback Hub app 
    8. Attach a screenshot of the behavior (if it’s not a crash or hang) 
    9. Press “Submit” 

    This will provide us with a trace we can use to debug the issue further. Once you’ve submitted this, please paste a link to the newly created Feedback Hub issue in this bug so that we can link the two together and continue to investigate.

    Best Wishes,
    The MS Edge Team

  • I just tried waiting 2-3 minutes to see if it would eventually start working as you described, but it was still extremely slow and using a lot of CPU. I’m not experiencing the lag at all in Chrome (version 64.0.3282.186).

    I’ve submitted the issue on Feedback Hub. Thanks for looking into it!

  • Microsoft Edge Team

    Changed Assigned To to “Bogdan B.”

  • This issue appears to be fixed in Windows 10 RS4 (Microsoft Edge 42.17127.1000.0, Microsoft EdgeHTML 17.17127).

You need to sign in to your Microsoft account to add a comment.

Sign in