Well trust me that I would not have proceeded further one single inch if any red thing appeared anywhere in my field of vision. So maybe the problem is
- red things occur in an area already scrolled out of the small window of view, even on desktop.
- red things occur asynchronously, not always fast enough for the user to see before he has scrolled them past the small window.
Also the moment the asynchronous check comes back with bad results, the entire form should lock up and turn red… No point in the user continuing to fill out the form when it is already doomed for failure, and the form already knows that.
Or, perhaps
- just wait for the check to succeed before allowing the user to go on to the next question. Surely the connection between the form and the database is higher bandwidth than between the form and user, so no need to allow the user to fill in the form so fast.