Embarrassing

I have a problem with cutesy copy, particularly when it comes to error messages. I understand that they are trying to be friendly and personable, but it’s usually not what the user wants or needs. Often, a friendly error message just leads to more confusion.

Take Firefox’s “well, this is embarrassing”.

I was once asked for advice about this error message.

“Should I be embarrassed?”, I was asked.

A New Best Practice for User Friendly 404 Page Design?

https://kerrick.blog/posts/2025/a-new-best-practice-for-user-friendly-404-pages/

#Development #Techniques
Accessible form validation · How accessible error messages build trust https://ilo.im/167t5t

_____
#Accessibility #Forms #Validations #ErrorMessages #Browser #WebDev #Frontend #HTML #ARIA #JavaScript

Somebody else got problems with the reviewlink system of #adobe recently?

Everytime I change something miniscule in my file it's this undescriptive error message. Kills the workflow I currently got ( and surely need to change now ) = #affinity here I come

A rule of #UX – Give the user all the necessary information to fulfill their task. #errormessages should be descriptive to get more information – that's just basic #uxwriting. An error number with more details would be helpful to see what can be done.

Could hope for more using PAID software of a billion dollar company. On the other hand it is #adobe ...

#uxdesign #creativecloud #indesign #editorial #design #graphicdesign #uxfails

Error messages should be independent. If you solve the underlying issue of one, it should not also solve another error message. Reporting multiple errors with the same underlying cause will just overload your users.

I think that's what's happening here: https://stackoverflow.com/q/79816819/15207568. You can solve 4/5 errors by just adding an extra argument to the `foldr` call.

#haskell #errormessages #usability