thank you so much.
It helped me a lot.
We evaluated such approach and we decided to not follow it because of the accessibility.
This behaviour is already available, the system will reload the view with the first TAB affected by errors open.
For this app we don't have as a target mobile devices, it is responsive for some breakpoints but no mobile gestures (eg tapping).
The UX team fought for such topic with the PM and BIs. At the end, we reached a compromise and we decided to not apply this approach. According to them users, very often, will send the form to the server without in putting any value. Some of the fields are pre-filled and they said that the users want to check which issues are popping-up with the default data set.
I want to thank you for this.
It's like fresh air in a smoking room.
I strongly believe that this is what we should do in our daily job. We should always be able to see things outside the box. We were so focused on how to display notifications and wrong fields that we lost the main goal of the page: to provide an overview of the webforms status.
I will challenge my colleagues to sketch the page from this angle