GUI Standards are however very not.
Accessibility standards tend to be legislative.
Stlying is generally a branding , look and feel, corporate / company standard if it exists and even more to the point applied.
Then there are domain standards, fior instance engineers prefer status indicator to dialogs.
Then there is a natural implementation path which generally is based on the OS version and locale.
Doing business windows apps I tend to use the same features the OS would use to report it's errors. It's a lot less work, but I constantly run into people who want to make my life a lot harder. Especially the ones who want a common standard across operating sytems and versions.
So without limiting yourself to a particular GUI domain, I don't see a suitable starting point for your project.
Best practice is to report the error in a way that makes sense to the user.