A rule needs context

A value can be well formed and still be unsuitable for its purpose. A date may be recognizable but fall outside an allowed period. A required field may contain text without answering the question. It helps to distinguish a formatting check from a check about meaning or context.

Make correction possible

A useful message identifies the input, explains the issue and describes a correction. It should preserve existing input when possible. Timing matters: interrupting every keystroke can make a simple task difficult, while waiting until the end may hide an easily corrected problem.

Validity has limits

In a hypothetical event planner, an end date earlier than a start date could prompt a correction. Passing that check would establish only that the dates are in order. It would not prove the event is feasible. A validation result establishes compliance with a particular rule.