When the server validates a form, the UX requirement is different from client-only validation: the server’s response is authoritative and may contain many errors. The pattern I recommend uses three cooperating pieces: a structured server payload, a page-level summary announced in a live region, and short inline messages attached to each control.
Implementation summary
Server payload: return an array of field errors in the shape { name: 'email', message: 'Enter a valid email.' } and a separate representation for non-field errors (quota, upstream failures). Avoid opaque banners like “Please fix the form.”
UI presentation: render a concise summary at the top (heading + list). Each summary item should reference the field label and link to the control.…