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

Sign-in promo is placed at the bottom of the popover, however, it’s read right after the title and before the body. Repro the issue from the following popover:
- Bookmark
- Extension added
Since the info in the body is likely to be more important than the promo, the visual order should be respected in SR announcement. 

Recommended fix:
- Sign-in promo to be read at the end following the visual order


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


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

Sign-in promo is placed at the bottom of the popover, however, it’s read right after the title and before the body. Repro the issue from the following popover:
- Bookmark
- Extension added
Since the info in the body is likely to be more important than the promo, the visual order should be respected in SR announcement. 

Recommended fix:
- Sign-in promo to be read at the end following the visual order


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


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!