Hi,

I was checking the ARIA Landmarks Examples pages you all have put together, and I was particularly interesting in the way that your developer has implemented the "Skip to" dropdown menu, which is coded up as a Menu widget ala the ARIA Authoring Practices 1.1.

Specifically, I liked the way you used role="separator" on two of the <li> elements in the dropdown menu to visually distinguish groups of menuitems. I was excited to browse this dropdown menu with some UA/AT combos. I was disappointed that only 2 of the 6 UA/AT combos even announced the presence of a separator, and only one combination announced a separator and its label. Here are those results:

• E11+JAWS18 - No announcement of separator or separator label
• IE11+NVDA2017.4 - No announcement of separator or separator label
• FF56+JAWS18 - No announcement of separator or separator label
• FF56+NVDA2017.4 - Proper announcement of both separator and separator label (had to toggle Insert+Space to get the announcement to work)
• Chrome64+JAWS18 - No announcement of separator or separator label
• Chrome64+NVDA2017.4 - Proper announcement of separator, but no announcement of separator label (had to toggle Insert + Space to get the announcement to work)

So here's my question, is the role="separator" element supposed to be announced along with a label (if provided) by UA/AT, but just isn't yet supported by software manufacturers yet? It is very limiting to use this design pattern if we can't group menuitems into labeled groupings that are announced by AT. I guess I could just prepend the category name in sr-only text to the menuitem label as a hack, by that verbose option creates a less than stellar user experience for AT users.

I have included a screenshot of the dropdown menu under review with this issue.

Thanks for your feedback!