Chrome Version: 63.0.3205.0 (Official Build) canary (64-bit)
OS: Windows 10 Version 1703 (OS Build 16251.0) 64-bit

What steps will reproduce the problem?
(1) Start Chrome and the NVDA screen reader.
(2) Open this URL: https://www.nvaccess.org/about/our-story/
(3) Close the tab.
(4) Open a new tab.
(5) In the address bar, type: our-story
(6) Press down arrow.

What is the expected result?
NVDA should report something like "nvaccess.org/about/our-story/ - NV Access | Our Story  1 of 4"

What happens instead?
NVDA just reports the full URL in the address bar: "https://www.nvaccess.org/about/our-story/"

Here's how this should be done at present:
1. Give the suggestions list a role of list and the items a role of list item.
2. Ensure all text of the suggestion is exposed via accName/accDescription. If in doubt, expose the full string via accName.
3. When the user presses down arrow or up arrow, focus the active suggestion for accessibility.
4. If the user does anything else (e.g. types a character or presses left arrow, right arrow, escape or backspace), focus the address bar for accessibility.

Ideally, it would be possible to do this without messing with accessible focus based on key presses (e.g. using the controller for relation and selection on the active suggestion), but unfortunately, this isn't currently how ARIA specifies autocomplete behaviour (and thus it isn't supported by AT).

Impact: This makes address bar autocomplete far less useful for screen reader users, since the only thing they can access is the URL in the address bar. When using the address bar to search history, the title of the page is far more useful.