input validation - should a validation message always be required?

Nobody has claimed this yet.

## 💬 Description
Following on from https://github.com/mi6/ic-ui-kit/issues/2613, which was done to make date-input validation consistent with text-field, select, etc, the question was asked whether the components should enforce a validation message. The guidance site & wcag seem to say that a message should be supplied

Some questions this raises:

1) The site suggests inline validation can be used without a message. However, not all components support inline validation (eg date-input) - do these need to be added (will require design input)
2) Would it be acceptable to on require a message for error & warning states?
3) When should this be done - this would potentially be a breaking change as previously it was possible to not have a message (although this would be bad practice - so can this be an enforced change?)

## 💰 Use value
Enforcing a message would then match the guidance on the site & also wcag criteria. currently it is possible to have a non-compliant app by setting the validation status without a message

Start by reviewing the linked issue 2613, then compare the validation guidance and WCAG expectations with the validation APIs across the affected components. The issue needs a resolved decision on message requirements, inline validation support, design input, and whether the change should be breaking before implementation can be considered done.

Written by the indexing model from the issue text.