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

There’s no direct way to the foreground popover. It takes 2+ keystrokes(e.g. F6 to Omnibox, and Tab keys).

Recommended fixes:
- Consider an existing shortcut to stop at a foreground popover:
--- Idea 1: ‘Ctrl+L and Tabs’ to stop at popover
--- Idea 2: F6 to stop at popover before cycling through Omnibox, Bookmarkbar, and document
--- Idea 3: Alt+Shift+T to stop at popover first as first toolbar item
- Announce the shortcut at the end of popover’s initial announcement for SR
- Provide a help center article about the shortcut


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


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

There’s no direct way to the foreground popover. It takes 2+ keystrokes(e.g. F6 to Omnibox, and Tab keys).

Recommended fixes:
- Consider an existing shortcut to stop at a foreground popover:
--- Idea 1: ‘Ctrl+L and Tabs’ to stop at popover
--- Idea 2: F6 to stop at popover before cycling through Omnibox, Bookmarkbar, and document
--- Idea 3: Alt+Shift+T to stop at popover first as first toolbar item
- Announce the shortcut at the end of popover’s initial announcement for SR
- Provide a help center article about the shortcut


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


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!