Chrome Version       : Stable 61.0.3163.100
OS Version           : Win10
Screenreader         : NVDA

The issue occurs when a modal is announced as ‘Alert’, not when announced as ‘Dialog’. Repro the issue from the following modals:
- Resubmit form
- JS Alert
Compare them to the correct behavior e.g. Add extension via a page or Webstore: "Dialog, [Title], [Body], [Focused button]”


Recommended fixes:
- Title to announce before body at dialog opening
- Focused button to announce at the end


Video* (issue):
https://drive.google.com/open?id=0B1VXa3kr2lYjT3ZEeWRyUmNNMVU

Video* (not issue, correct reference):
https://drive.google.com/open?id=0B1VXa3kr2lYjMk93b1YzTy0yVTg

Full doc*: go/ar-dialogs-win-2017
*: Docs and videos are google internal


Recommended fixes:
- If an implementation to fix this bug covers all other dialogs in the same type, it will be ideal.
- If it's a spot fix for a listed dialog, we can still use the fix as a reference for future fixes for others. 
- Please discuss if the issue needs to be clarified further, and/or if there's an alternative fix. 
- Independently, expanded tests are needed for 1) Harmony flag enabled, 2) Win10+JAWS, 3) CrOS+ChromeVox, and 4) OSX+VO, and also modification of this bug is needed if the same issue occurs on 1)-4).

Thanks!

 

Chrome Version       : Stable 61.0.3163.100
OS Version           : Win10
Screenreader         : NVDA

The issue occurs when a modal is announced as ‘Alert’, not when announced as ‘Dialog’. Repro the issue from the following modals:
- Resubmit form
- JS Alert
Compare them to the correct behavior e.g. Add extension via a page or Webstore: "Dialog, [Title], [Body], [Focused button]”


Recommended fixes:
- Title to announce before body at dialog opening
- Focused button to announce at the end


Video* (issue):
https://drive.google.com/open?id=0B1VXa3kr2lYjT3ZEeWRyUmNNMVU

Video* (not issue, correct reference):
https://drive.google.com/open?id=0B1VXa3kr2lYjMk93b1YzTy0yVTg

Full doc*: go/ar-dialogs-win-2017
*: Docs and videos are google internal


Related notes:
- If an implementation to fix this bug covers all other dialogs in the same type, it will be ideal.
- If it's a spot fix for a listed dialog, we can still use the fix as a reference for future fixes for others. 
- Please discuss if the issue needs to be clarified further, and/or if there's an alternative fix. 
- Independently, expanded tests are needed for 1) Harmony flag enabled, 2) Win10+JAWS, 3) CrOS+ChromeVox, and 4) OSX+VO, and also modification of this bug is needed if the same issue occurs on 1)-4).

Thanks!