SC 3.3.1. and G83: no error description when input fields aren't completed

[Vfmj]

I'd like to suggest a clarification in sc 3.3.1., so that it ties in with G83 (required input fields not completed).

SC 3.3.1. error Identification seems to suggest every auto-detected error has be described. I get this is important when actual input isn't valid for whatever reason. But is an error description necessary when someone left a required input field blank? An error description seems only good for pointing fingers. Not user-friendly.

I've been advised to use a validation message like "This field hasn't been completed." or "Incomplete field" based solely on SC 3.3.1. But this is user-unfriendly. And dificult: a person still has to think what they should do next.

Something like "Add your phone number to continue", or "Add your phone number." doesn't strictly follow sc 3.3.1., but is in line with [G83](technique G83 (input field not completed)), because it clearly explains which field hasn't been completed. And what should be done.

[detlevhfischer]

The reference in G83 to using an alert dialog box in client side validation (something which is probably very rare now) indicates that this technique is quite dated.

The note

Some screen readers may not notice and announce the change to the label so screen reader users may be unaware of the error.

also appears to indicate that probably at the time of writing, there were no techniques like aria-describedby to programmatically link error messages to labels (unless they were made part of the label).

I think there are several acceptable ways to supply error messages if a field has been omitted. If the label is clear and no further hints are necessary or even helpful (say, for a field like "First name") any kind of hint like "this field is required" seems sufficient to me, especially if the message is also programmatically associated with the input so that label, input and error message will be rendered on focussing the field.

[mbgower]

Working Group Draft Response

It's important to remember that Error Identification and Error Suggestion are two different requirements.

G83 is only listed as sufficient for identification, not error suggestion. There is some overlap between these two criteria, but where you begin suggesting you need to say "Add your phone number", that has clearly moved to making a suggestion rather than simply identifying an error that is the result of a missing required field.

That said, it is possible to meet both criteria at the same time with a message like "You must add your phone number". That will meet the test of G83 and also provides a suggestion of what the user needs to do.