When a feedback form cannot be completed, its message should point to the particular field that needs attention and explain the problem. “Something went wrong” leaves the reader searching, while “Note is empty” gives a clear place and reason to correct. An identified error is not proof of a stored submission or a resolved issue.
What a useful error message tells you
For a detected input error, the message should identify the affected item in text and describe what is wrong. The W3C explanation of error identification distinguishes this from merely showing the form again without useful information.
The field name and problem should be recognisable together. “Note is empty” is more useful than “Invalid input”, because it tells the reader which control to revisit and what change is required.
Hypothetical comparison: Article title and Note
Hypothetical example: imagine a feedback form with two fields, “Article title” and “Note”. The title contains text, but Note has been left empty.
| Message | What the reader can tell |
|---|---|
| Something went wrong | No field or cause is identified. |
| Note is empty | The Note field needs attention, and text is required. |
In the second case, the reader can locate the relevant field without checking each control. If several fields have errors, each one should receive its own understandable identification rather than a single general warning.
Do not confuse input errors with network failures
A missing required value is an input error, but every failed action is not. A connection problem, server failure, or interrupted request may need a different message, such as “The response could not be sent; try again later.” That message should not falsely claim that a field is empty.
Correction suggestions are a separate concern: “Enter a short note” can help, but first the form must identify the problematic field. These examples are hypothetical and do not describe a tested Jai Club Games form.