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

With or without screenreader, the following popovers are not keyboard-navigable when they’re on foreground and not focused:
- Save credit card
- Translate

Recommended fixes:
- When the popover is on foreground and the keyboard navigates to their anchor icons, set focus to the initial focus item in the popover, e.g. Save password
- Once the focus enters the popover, trap the focus


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

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

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

With or without screenreader, the following popovers are not keyboard-navigable when they’re on foreground and not focused:
- Save credit card
- Translate

Recommended fixes:
- When the popover is on foreground and the keyboard navigates to their anchor icons, set focus to the initial focus item in the popover, e.g. Save password
- Once the focus enters the popover, trap the focus


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

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

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!