UserAgent: Mozilla/5.0 (Windows NT 6.1; WOW64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/55.0.2883.87 Safari/537.36

Steps to reproduce the problem:
1. Open up a website that has screen alerts on change or that throws an error
2. Turn on your screen reader
3. Submit a form that is invalid
4. Visually, you should see an error but using a screen reader you should hear one as well

What is the expected behavior?
You should hear a screen reader alert that something has changed and or is invalid

What went wrong?
Nothing is read by the screen reader, as it used to be in November, and as it continues to do in other browsers.

Did this work before? Yes 54

Chrome version: 55.0.2883.87  Channel: stable
OS Version: 6.1 (Windows 7, Windows Server 2008 R2)
Flash Version: Shockwave Flash 24.0 r0

In November, using Angular v 1.4.5 I helped develop a number of pages and forms as part of an application for a large utility provider which had accessibility alerts integrated into the application. Google Chrome and JAWS screen reader were the main targets and all application and accessibility requirements were met. In late December the features were revisited and the screen reader JAWS was no longer able to read the alerts coming from the Google Chrome browser. Internet Explorer and Firefox, which were not used during the development process, still continue to successfully read the alerts.

After hours of recording and trying other solutions, I believe that the issue is with the latest Chrome browser update.
There was an update to the Chrome version from when the application was under development (November 2016) to when the issue was discovered (December 2016).

Reviewing the list of updates, I was unable to determine which updates would have had any impact on the alerting of changing elements in the Angular website application which was previously working and continue to works for other browsers.