E-mail List Archives

Search E-mail List Archives for

Number of posts in this thread: 2 (In chronological order)

From: Joseph Sherman
Date: Tue, Jun 18 2019 9:35AM
Subject: Success Criterion 3.3.1: Error Identification
No previous message | Next message →

3.3.1 states that "If an input error is automatically detected, the item that is in error is identified and the error is described to the user in text. "

The Understanding document for 3.3.1 states that "re-displaying the form and indicating the fields in error is insufficient for some users to perceive that an error has occurred."

G83 states that "Another approach, using server-side validation, is to re-display the form (including any previously entered data), with ... a text description that identifies the omitted mandatory fields". That's pretty vague.

There's a note about best practices to include a message or alert, etc. but that is not part of the Technique.

Does that mean that simply re-displaying the form and indicating the fields in error is a failure of 3.3.1? It's a bad user experience, and it seems to violate the intent of 3.3.1, but not necessarily 3.3.1 itself?


Joseph

From: Mallory
Date: Wed, Jun 19 2019 3:35AM
Subject: Re: Success Criterion 3.3.1: Error Identification
← Previous message | No next message

I have a guess that:
"re-displaying the form and indicating the fields in error is insufficient for some users to perceive that an error has occurred."
*might* mean showing the form as it was, but with the error fields looking all error-y is not enough... and perhaps that text should mention what would make it right (changing the <title> and <h1> texts, listing the errors at the top of the page or before the form (we're assuming a new page load where focus was brought to the top of the page), etc.

And the G83 might be a poorly-worded thing saying similar "text description..." saying what's wrong.

That's my opinion, it's flexible.

cheers,
_mallory

On Tue, Jun 18, 2019, at 5:35 PM, Joseph Sherman wrote:
> 3.3.1 states that "If an input error is automatically detected, the
> item that is in error is identified and the error is described to the
> user in text. "
>
> The Understanding document for 3.3.1 states that "re-displaying the
> form and indicating the fields in error is insufficient for some users
> to perceive that an error has occurred."
>
> G83 states that "Another approach, using server-side validation, is to
> re-display the form (including any previously entered data), with ... a
> text description that identifies the omitted mandatory fields". That's
> pretty vague.
>
> There's a note about best practices to include a message or alert, etc.
> but that is not part of the Technique.
>
> Does that mean that simply re-displaying the form and indicating the
> fields in error is a failure of 3.3.1? It's a bad user experience, and
> it seems to violate the intent of 3.3.1, but not necessarily 3.3.1
> itself?
>
>
> Joseph
>
> > > > >