Google Chrome 64.0.3250.0 (Official Build) canary (64-bit) (cohort: 64-Bit)
Windows 10 Enterprise Version 1607 Build 14393.1770
NVDA 2017.3
JAWS 2018.1710.42 private preview release

This is reporting potential confusion from the way that the Customize and Control Google Chrome menu in the upper right corner. Here's how to reproduce:

# Navigate to the Customize and Control Google Chrome menu
# Press space to collapse
# Press the down arrow keys to start reading items in the list
# Note that after reading the menu item and its keyboard shortcut, it also reads the letter that is a quick key for that action. The letter is visually underlined. An example verbalization would be "New incognito window Ctrl + Shift + N, I"
# Press i, incognito window opens 

In this case, pressing I opens the incognito window but as a JAWS user, I might expect I to jump to the next item in a list per the JAWS navigation keyboard shortcuts: https://www.freedomscientific.com/Training/Surfs-Up/Quick_Keys.htm 

We need to consider which 


 

Google Chrome 64.0.3250.0 (Official Build) canary (64-bit) (cohort: 64-Bit)
Windows 10 Enterprise Version 1607 Build 14393.1770
NVDA 2017.3
JAWS 2018.1710.42 private preview release

This is reporting potential confusion from the way that the Customize and Control Google Chrome menu in the upper right corner. Here's how to reproduce:

# Navigate to the Customize and Control Google Chrome menu
# Press space to collapse
# Press the down arrow keys to start reading items in the list
# Note that after reading the menu item and its keyboard shortcut, it also reads the letter that is a quick key for that action. The letter is visually underlined. An example verbalization would be "New incognito window Ctrl + Shift + N, I"
# Press i, incognito window opens 

In this case, pressing I opens the incognito window but as a JAWS user, I might expect I to jump to the next item in a list per the JAWS navigation keyboard shortcuts: https://www.freedomscientific.com/Training/Surfs-Up/Quick_Keys.htm 

We need to consider which behavior is correct and if we are adhering to the correct behavior. 


 

Google Chrome 64.0.3250.0 (Official Build) canary (64-bit) (cohort: 64-Bit)
Windows 10 Enterprise Version 1607 Build 14393.1770
NVDA 2017.3
JAWS 2018.1710.42 private preview release

This is reporting potential confusion from the way that the Customize and Control Google Chrome menu in the upper right corner. Here's how to reproduce:

# Navigate to the Customize and Control Google Chrome menu
# Press space to collapse
# Press the down arrow keys to start reading items in the list
# Note that after reading the menu item and its keyboard shortcut, it also reads the letter that is a quick key for that action. The letter is visually underlined. An example verbalization would be "New incognito window Ctrl + Shift + N, I"
# Press i, incognito window opens 

In this case, pressing I opens the incognito window but as a JAWS user, I might expect I to jump to the next item in a list per the JAWS navigation keyboard shortcuts: https://www.freedomscientific.com/Training/Surfs-Up/Quick_Keys.htm 

Alternatively, if I didn't know about the internal quick keys, I might wonder why my screen reader is speaking a letter at the end of the verbalization without explanation. The spoken text doesn't give context about why that letter is spoken, but a visual user sees the underlined character within the word and knows that it represents a keyboard shortcut. 

We need to consider which behavior is correct and if we are adhering to the correct behavior.