Bugzilla

In Bug 1843320 the WhyPaused is turned into a live region. During tests this works ok with Voice Over on Mac, but does not read properly on NVDA on Windows. 
Some details of the issues from https://phabricator.services.mozilla.com/D223928#7808007
1) It looks like the function name + file + line number get read out directly after "Paused while stepping" with no space in between. For instance, NVDA reads to me "Paused while steppinga.init - fxa.6cacc544775b.js:1:5819". It says "steppinga" not "stepping a" because there doesn't seem to be a space. This might be an NVDA quirk (maybe it ignores the \n?) but seems worth mentioning.
2) When you step through a prettified version of a minified file, the output gets even more verbose. NVDA read me "Paused while steppinga.init - fxa.6cacc544775b.js:1:5819 a.init - fxa.6cacc544775b.js:formatted:289:2" for every line. That's a lot of information for advancing one line. Maybe we could trim it to just the formatted file?

In Bug 1843320 the WhyPaused is turned into a live region. During tests this works ok with Voice Over on Mac, but does not read properly on NVDA on Windows. 
Some details of the issues from https://phabricator.services.mozilla.com/D223928#7808007
1) It looks like the function name + file + line number get read out directly after "Paused while stepping" with no space in between. For instance, NVDA reads to me `"Paused while steppinga.init - fxa.6cacc544775b.js:1:5819"`. It says `"steppinga"` not `"stepping a"` because there doesn't seem to be a space. This might be an NVDA quirk (maybe it ignores the \n?) but seems worth mentioning.
2) When you step through a prettified version of a minified file, the output gets even more verbose. NVDA read me `"Paused while steppinga.init - fxa.6cacc544775b.js:1:5819 a.init - fxa.6cacc544775b.js:formatted:289:2"` for every line. That's a lot of information for advancing one line. Maybe we could trim it to just the formatted file?