What is the "page info separator"?
Are you talking about the <hr> element. If so, other Windows screen readers such as NVDA and Jaws do read that.
I started Narrator on Win 10 pre-anniversary update and tried to browse a bit both through the web contents and through Chrome's toolbar / address bar.
I haven't come across anything unusual or noisy.
Please re-open if you have more information.

Are you talking about the image that you come across when tabbing from the web contents to the address bar and that opens a dialog with permission settings for the current site?
Actually, that shouldn't be skipped because those settings need to be accessible via the keyboard. What needs to happen is for us to label the image to say something like "Page info"?

I am testing with version 56.0.2914.

No, I mean this one.

(Sorry, I usually file detailed repro steps. But Windows Narrator highlighting is broken in HiDPI in VMWare, so I couldn't get an easy screenshot, and filed a stub so I don't forget.)

Mac and Chrome OS skip this separator.

Deleted: Screen Shot 2016-11-15 at 18.08.30.png 97.5 KB

	Screen Shot 2016-11-15 at 18.08.30.png 97.5 KB View Download

Also:

> Actually, that shouldn't be skipped because those settings need to be accessible via the keyboard.

This is Issue 536158.

Reopening, since this is inconsistent across platforms, for one.

nektar@: Should the separator be read on all platforms or none? (Or is there possibly a weird reason for different behaviours?)

#6: The separator should not be read. It isn't read with VoiceOver; I don't know why it's read with Narrator.

I agree that it should be removed.
I suspect that it simply involves replacing  the following line in
ui/views/controls/separator.cc line:54
node_data->role = ui::AX_ROLE_SPLITTER;

with
node_data->role = ui::AX_ROLE_UNKNOWN;

This needs to be tested though and especially that it doesn't affect other parts of Chrome where separators are used.

Looking at the code more closely, I don't think the fix would be that simple because other parts of the browser seem to be using separators legitimately and we should not hide them from everywhere.
For example, as far as I remember, separators are used on Chrome OS on the Launcher and Chromevox does announce them.
@Dominic, In your experience, is it common in dialogs to have separators that are not announced by screen readers?