WebAIM - Web Accessibility In Mind

E-mail List Archives

Re: Handling with accessible error messages.

for

From: Rakesh.Paladugula@cognizant.com
Date: Sep 23, 2010 7:27AM

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

-----Original Message-----
From: <EMAIL REMOVED>
[mailto: <EMAIL REMOVED> ] On Behalf Of Info
LearnAccessibility
Sent: Thursday, September 23, 2010 6:44 PM
To: WebAIM Discussion List
Subject: Re: [WebAIM] Handling with accessible error messages.

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 REMOVED>
< <EMAIL 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.
>
>
>
> -----Original Message-----
> From: <EMAIL REMOVED>
> [mailto: <EMAIL REMOVED> ] On Behalf Of patrick
> dunphy
> Sent: Thursday, September 23, 2010 6:12 PM
> To: WebAIM Discussion List
> Subject: Re: [WebAIM] Handling with accessible error messages.
>
> 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 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.
>>