My question is: Why does NVDA not read 'alert. The span and div construction surrounding the error messages is the same in production and in my snippet. Chrome reads it only once and omits the second message starting with 'alert'. Once only the messagetext and then the second time 'alert' and then the message text.

Here Firefox reads the error message twice. This reduced demonstration snippet behaves slightly different. The following section has been edited, please see edit below. The same case in Firefox causes NVDA to read 'alert. In production when selecting the 'No' selection the error message is added to the HTML, but no error message is read at all by NVDA. This HTML has a problem in combination with Google Chrome and an NVDA screen reader. In production there are 5 to 6 of these selections one below the other and it is embedded into a greater HTML structure (with multiple parent divs which also have navigation elements and other stuff). This is an extracted and simplified version of our production HTML / JS. Var errMsg = document.createTextNode('Very long error message with special red font, details, paragraphs and recovery suggestion is displayed here') Var spanTwo = document.createElement('span') Var spanOne = document.createElement('span') Var newDiv = document.createElement('div')

Var errorDiv = document.getElementById('lblErr') I added it to the onChange of the radio buttons: The JavaScript code which adds the error message. Screenreader Errormessage Test with Radiobuttons

Uninstall nvda screen reader