The following revision refers to this bug:
  https://chromium.googlesource.com/chromium/src.git/+/668725525cd8bdcc7eef5d5e27564a9e1c07f026

commit 668725525cd8bdcc7eef5d5e27564a9e1c07f026
Author: dmazzoni <dmazzoni@chromium.org>
Date: Wed Apr 27 23:22:50 2016

Don't suppress the load complete accessibility event

Get rid of code that suppresses the load complete accessibility
event when the window isn't focused. It was added when we
suppressed focus events inside a tab when that window doesn't
have focus, and that part of the change was valid - but that
logic is now implemented in browser_accessibility_manager.cc,
so this code here is redundant. Suppressing the load complete
event was a speculative fix at the time but we now believe it
was the wrong idea, it should fire even when the window is not
currently focused.

BUG= 606949 

Review-Url: https://codereview.chromium.org/1923663002
Cr-Commit-Position: refs/heads/master@{#390230}

[modify] https://crrev.com/668725525cd8bdcc7eef5d5e27564a9e1c07f026/content/browser/accessibility/browser_accessibility_manager_win.cc

Google Chrome 65.0.3294.2 (Official Build) canary (64-bit) (cohort: 64-Bit)
Windows 10 Enterprise Version 1607 Build 14393.1770
NVDA 2017.4
JAWS 2018.1712.10 Private Beta 

# Launch JAWS
# Load Chrome with a page with lots of headings like https://en.wikipedia.org/wiki/Chrome
# Listen for announcement after completion of loading
Works as expected: 
https://en.wikipedia.org/wiki/Chrome
Chrome - Wikipedia
Page has 12Regions, 20headings and 137links