Chrome Version: 61.0.3122.0 (Official Build) canary(64-bit)
OS: Windows 10 Version 1703 (OS Build 16199.1000) 64-bit

What steps will reproduce the problem?
(1) Start Chrome and the NVDA screen reader.
(2) Press f10 and then space to open the Chrome menu.
Expected: NVDA should say "menu"
Actual: It says nothing.
(3) Press down arrow.
Expected: NVDA should say "New tab Ctrl+T"
Actual: It says "list sub menu  New Tab Ctrl+T"
(4) Dismiss the Chrome menu.

(5) Open google.com
(6) Ensure the search box is focused.
(7) Press the applications key or shift+f10 to open the context menu.
Expected: NVDA should say "menu"
Actual: It says nothing.
(8) Press down arrow.
Expected: NVDA should say "Paste Ctrl+V"
Actual: It says "list sub menu  Paste Ctrl+V"

This is a fairly recent regression, though I don't know precisely when. It works as expected in 59.0.3071.86 (Official Build) (64-bit). I'm pretty sure it worked in a Canary build since then, but I don't have the build number.

It occurs because Chrome menus now get a role of list instead of menu. As a result, menu start events aren't valid for them.

Impact: This makes Chrome menus tedious at best for Chrome + NVDA users, very confusing and potentially unusable at worst.