E-mail List Archives

Search E-mail List Archives for

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

From: Rakesh.Paladugula
Date: Thu, Sep 23 2010 6:21AM
Subject: Handling with accessible error messages.
No previous message | Next message →

Hi folks,
We have a form which needs to be made accessible.
On submition of the form the errors are appeared as a list before the
form.
User has to read all the error messages and then move to the form to
enter. If we have more than 3 errors an user cannot remember all the
error messages and enter.
So another mechanism also is required to provide the error messages for
the users of screen readers some where near the wrongly entered field.
I prefer providing a hidden span with error message near corresponding
field. Is it okey?
Can any one bring more accessible solution on it without disturbing the
existing layout.
Waiting for your responses.
Thanks in advance.
Rakesh

This e-mail and any files transmitted with it are for the sole use of the intended recipient(s) and may contain confidential and privileged information.
If you are not the intended recipient, please contact the sender by reply e-mail and destroy all copies of the original message.
Any unauthorised review, use, disclosure, dissemination, forwarding, printing or copying of this email or any action taken in reliance on this e-mail is strictly prohibited and may be unlawful.

From: Langum, Michael J
Date: Thu, Sep 23 2010 6:36AM
Subject: Re: Handling with accessible error messages.
← Previous message | Next message →

The critical issue with form error messages, is helping the user get focus to the problematic input field. If you're error message simply reports a list of errors, and then sends the user to the first input field in the form, he/she will have to tab through all the forms until reaching the problematic one. If there were only ONE error reported (instead of a list) you could use JavaScript to send focus directly to the problematic input field.

If I were doing this, I would report errors one-at-a-time. Each error report would give correction instructions and direct the focus back to the problematic input. Where possible, I would also trigger this error report using the onBlur() event so that errors were corrected immediately.

-- Mike

From: patrick dunphy
Date: Thu, Sep 23 2010 6:42AM
Subject: Re: Handling with accessible error messages.
← Previous message | Next message →

In this case I would first inform the user the number of errors encountered so they're aware how many their are. Keeping the list you've mentioned, I'd then make each of the individual error items clickable so that they can focus to the input with the problem. This will assist users in getting direct access to resolving individual errors.

Hope this helps - good luck.

Thanks!
-PD

On 2010-09-23, at 8:20 AM, < = EMAIL ADDRESS REMOVED = > wrote:

> Hi folks,
> We have a form which needs to be made accessible.
> On submition of the form the errors are appeared as a list before the
> form.
> User has to read all the error messages and then move to the form to
> enter. If we have more than 3 errors an user cannot remember all the
> error messages and enter.
> So another mechanism also is required to provide the error messages for
> the users of screen readers some where near the wrongly entered field.
> I prefer providing a hidden span with error message near corresponding
> field. Is it okey?
> Can any one bring more accessible solution on it without disturbing the
> existing layout.
> Waiting for your responses.
> Thanks in advance.
> Rakesh
>
> This e-mail and any files transmitted with it are for the sole use of the intended recipient(s) and may contain confidential and privileged information.
> If you are not the intended recipient, please contact the sender by reply e-mail and destroy all copies of the original message.
> Any unauthorised review, use, disclosure, dissemination, forwarding, printing or copying of this email or any action taken in reliance on this e-mail is strictly prohibited and may be unlawful.
>

From: Tim Harshbarger
Date: Thu, Sep 23 2010 6:48AM
Subject: Re: Handling with accessible error messages.
← Previous message | Next message →

One option might be to make the error messages links. When the user
clicks on the error message focus is then moved to the field with the
error.

How else do you visually notify users which field has the error?

Depending on your audience, ARIA provides some mechanisms that might be
useful. For example, using aria-describedby to programmatically
indicate a relationship between the field and the error message.

If you have a long submission form or there are a lot of fields of
similar type, you might want to provide some kind of mechanism that
allows the user to see the error message next to the field. That might
be useful to people using screen magnification or people who might find
themselves constantly scrolling to the error messages and back to the
fields because they keep forgetting exactly what the error was.

Tim

From: Rakesh.Paladugula
Date: Thu, Sep 23 2010 6:54AM
Subject: Re: Handling with accessible error messages.
← Previous message | Next message →

Ya Patrick,
I do have that thought. But when the user clicks the first error and
fills the field, he/she has to come back to the list of errors to find
the next error message, then for third and so on. When the form have
more fields and errors are more it will be amberasing.
Another way that is running out of my mind is
The list will be as usual. The the text field will have a value in it
with the error message. This appears only with the error field and
disappears when user starts typing in it.
For the dropdowns user will be provided with default option as mandatory
and optional. So the user will not leave it un selected.
Thanks
Rakesh.

From: Info LearnAccessibility
Date: Thu, Sep 23 2010 7:18AM
Subject: Re: Handling with accessible error messages.
← Previous message | Next message →

Rakesh,
If you offer value in the text fields and the same will disappear on
focus, what if user wishes to review all the fields and then wish to
come back and correct the error reported fields? There was similar
discussion we had recently on the list.

I would vote for ara-describedby for this situation

Thanks,
Sri

On 9/23/10, = EMAIL ADDRESS REMOVED =
< = EMAIL ADDRESS REMOVED = > wrote:
> Ya Patrick,
> I do have that thought. But when the user clicks the first error and
> fills the field, he/she has to come back to the list of errors to find
> the next error message, then for third and so on. When the form have
> more fields and errors are more it will be amberasing.
> Another way that is running out of my mind is
> The list will be as usual. The the text field will have a value in it
> with the error message. This appears only with the error field and
> disappears when user starts typing in it.
> For the dropdowns user will be provided with default option as mandatory
> and optional. So the user will not leave it un selected.
> Thanks
> Rakesh.
>
>
>
>

From: Rakesh.Paladugula
Date: Thu, Sep 23 2010 7:27AM
Subject: Re: Handling with accessible error messages.
← Previous message | Next message →

Hi Sri,
With this event the content of the value will not be disappeard
immediately on focus, but when the user starts typing the value will
gets disappeared giving chance for the user to type the correct
information.

Thanks
Rakesh

From: adam solomon
Date: Thu, Sep 23 2010 12:24PM
Subject: Re: Handling with accessible error messages.
← Previous message | Next message →

As far as long error lists are concerned, required fields are going to be
making up the bulk of the list. Therefore, if required fields are marked
clearly, and the validation message adds some message to the effect that
there are many unfilled required fields, then the user should not have to
remember the whole list, rather traverse through the form and fill in any
marked required field. Complex validation can carry with it a large
development price - in such situations I think it fair to throw part of the
responsibility on the user.

On Thu, Sep 23, 2010 at 2:20 PM, < = EMAIL ADDRESS REMOVED = > wrote:

> Hi folks,
> We have a form which needs to be made accessible.
> On submition of the form the errors are appeared as a list before the
> form.
> User has to read all the error messages and then move to the form to
> enter. If we have more than 3 errors an user cannot remember all the
> error messages and enter.
> So another mechanism also is required to provide the error messages for
> the users of screen readers some where near the wrongly entered field.
> I prefer providing a hidden span with error message near corresponding
> field. Is it okey?
> Can any one bring more accessible solution on it without disturbing the
> existing layout.
> Waiting for your responses.
> Thanks in advance.
> Rakesh
>
> This e-mail and any files transmitted with it are for the sole use of the
> intended recipient(s) and may contain confidential and privileged
> information.
> If you are not the intended recipient, please contact the sender by reply
> e-mail and destroy all copies of the original message.
> Any unauthorised review, use, disclosure, dissemination, forwarding,
> printing or copying of this email or any action taken in reliance on this
> e-mail is strictly prohibited and may be unlawful.
>

From: Terrill Bennett
Date: Thu, Sep 23 2010 1:36PM
Subject: Re: Handling with accessible error messages.
← Previous message | No next message

At my previous contract, the developer's handled form errors by:

1) The CGI scripts created skip-nav links at the top of the page, 1
for each field containing an error, in index order. This allowed
anyone with JavaScript disabled to quickly get to the 1st and each
successive each error by fixing 1 error, returning to the top, find
the next skip-nav, repeat.

2) If enabled, a JavaScript iterated through the page looking for
labels with the error-message class and added a hidden
(off-screen/CSS) link immediately after the field to the NEXT field
with an error. After the final field with an error, a hidden link was
added which said all errors were complete, and sent the focus to the
submit button if the link was activated.

If nothing else, perhaps this will give others a seed for a better method(?).

-- terrill --

> Hi folks,
> We have a form which needs to be made accessible.
> On submition of the form the errors are appeared as a list before the
> form.
> User has to read all the error messages and then move to the form to
> enter. If we have more than 3 errors an user cannot remember all the
> error messages and enter.
> So another mechanism also is required to provide the error messages for
> the users of screen readers some where near the wrongly entered field.
> I prefer providing a hidden span with error message near corresponding
> field. Is it okey?
> Can any one bring more accessible solution on it without disturbing the
> existing layout.
> Waiting for your responses.
> Thanks in advance.
> Rakesh