TextField (and others) - Error messages not read w/ NVDA/JAWS after another keypress

[jnurthen]

🐛 Bug Report

When an error message is triggered on a textField if there is a 2nd keypress after the message appears then the reading of the message is suppressed with JAWS and NVDA

🤔 Expected Behavior

The error message should be read to the user.

😯 Current Behavior

The user doesn't currently hear the message

💁 Possible Solution

🔦 Context

💻 Code Sample

https://codesandbox.io/s/errormessages-9skph5

Run the testcase and type "test" into the field. Note that JAWS/NVDA so not report an error to the user
Run the testcase again but this time just type "t" into the field. Note that the error is correctly reported here.

🌍 Your Environment

Software	Version(s)
react-spectrum	3
Browser	Chrome/FF w/ NVDA or JAWS
Operating System	Windows

🧢 Your Company/Team

🕷 Tracking Issue (optional)

[LFDanLu]

A possible solution discussed by the team would be to add aria-live but only when field is focused to avoid multiple announcements wheen multiple form fields are marked as invalid at the same time. Any thoughts?

[luisrudge]

I just had a 3rd party company reporting this exact issue on a project I'm working on. Basically the error message is not announced right after the form validation happens. Feels like this behaviour should be baked in the library and not something every project needs to implement from scratch.