IntelliSense suggestions are not accessible to a screen reader

[jayspadie]

monaco-editor version: 0.8.3
Browser: Any
OS: Windows 10

During Accessibility testing, it was found that IntelliSense suggestions are not read correctly by a screen reader. Using Narrator with Edge, nothing is read while arrowing up/down the selections. Using NVDA with Chrome or Firefox, the current line of code is repeated while arrowing through each suggestion instead of the suggestion itself, as shown below from the Monaco playground using NVDA with Chrome.

[egamma]

// fyi @chrisdias

[chrisdias]

Related to microsoft/vscode#3787

[alexdima]

The root problem here is that in the monaco editor we don't have an aria-alert dom node configured. I am not sure if we are allowed to have multiple aria-alert dom nodes on a single page. i.e. what should happen if one host instantiates two monaco editors on a single page, should we create a single aria-alert dom node or should we create two. Should this be configurable such that we reuse the aria-alert dom node of the host...

[jayspadie]

It is not uncommon for us to have multiple aria-live="polite" (with aria-atomic="true") divs on a page, and they seem to work. We also have cases of reusing the same aria-live div from multiple controls. I am not aware of any restrictions with having more than one.

[alexdima]

@jayspadie In your experience, does role="alert" work on Narrator + Edge ? I could not find any way to make Narrator read an alert. (see #481)

e.g. from https://www.w3.org/TR/WCAG20-TECHS/ARIA19.html

Nevermind. A restart later ... Narrator started reading role="alert" content...