Version: 54.0.2837.0 canary (64-bit)
OS: Windows 10 64 bit

STR:
1. Start the NVDA screen reader.
2. Ensure that NVDA's "Report spelling errors" and "Play sound for spelling errors while typing" settings are enabled; this is the default, so if you haven't changed it, there's nothing to do.
3. Start Chrome.
4. Open this URL: data:text/html,Text: <textarea></textarea>
5. Focus the textarea.
6. Type "This is a tset" and press space.
Expected: NVDA should "buzz" indicating that you just typed a spelling error.
Actual: It doesn't.

This occurs because the invalid:spelling text attribute isn't exposed until after the next change to the text. So, if you type one more character after step 6, invalid:spelling is then correctly exposed for "tset". Instead, it should be exposed as soon as you press space, full stop, etc. after misspelling a word.

Note that Chrome seems to be aware the word is misspelled, as you can move back to the word and press the applications key to see suggestions. However, even after you do this, the invalid:spelling attribute still isn't exposed until the next change to the text.