RE: Forms and error messages

Ø  and not point out the specific field in which the error occurred if the input was entered incorrectly. However, field level errors should be identified for items that can't be entered into the field like special characters.

Mary, it's interesting that you say this because this has come up recently with a client.  WCAG would appear to provide and exception for these situations.  Authors though should be careful between what they say and what fields they actually highlight in error.  For example, I've seen some sites say the username/password was in error but the site only displayed a red box around the username.   So the visual messaging was different from the actual error message and thus didn't provide an equivalent experience if you couldn't see the color.

Jonathan

--
Jonathan Avila
Chief Accessibility Officer
SSB BART Group
jon.avila@ssbbartgroup.com<mailto:jon.avila@ssbbartgroup.com>
Phone 703.637.8957
Follow us: Facebook<http://www.facebook.com/#!/ssbbartgroup> | Twitter<http://twitter.com/#!/SSBBARTGroup> | LinkedIn<http://www.linkedin.com/company/355266?trk=tyah> | Blog<http://www.ssbbartgroup.com/blog> | Newsletter<http://eepurl.com/O5DP>

From: Wishnew, Mary [mailto:mary.wishnew@citi.com]
Sent: Friday, April 10, 2015 1:30 PM
To: Jonathan Avila; Madhavi Herle; w3c-wai-ig@w3.org
Subject: RE: Forms and error messages

Johnathan,

I agree with your thoughts I would also suggest to make sure the security of the form fields in question is also considered when placing an error message.  For fraud reasons entry items such as a user id and password should have page level error messages and not point out the specific field in which the error occurred if the input was entered incorrectly. However, field level errors should be identified for items that can't be entered into the field like special characters.

Regards,

Mary Wishnew

From: Jonathan Avila [mailto:jon.avila@ssbbartgroup.com]
Sent: Thursday, April 09, 2015 8:11 AM
To: Madhavi Herle; w3c-wai-ig@w3.org<mailto:w3c-wai-ig@w3.org>
Subject: RE: Forms and error messages


> If testing a large form with a lot of input fields, where would you prefer to see the error messages?

Is it before the start of the form with links to the form fields or error messages just before the form fields?



With a large form I agree it makes sense to warn the user about the issues as they occur so they can address them.  Also leaving in the errors at the top of the form will provide a summary for people who have trouble locating the fields in error after submit.



I wrote a blog on this topic called How to Provide Accessible Error Identification<https://urldefense.proofpoint.com/v1/url?u=http://www.ssbbartgroup.com/blog/how-to-provide-accessible-error-identification/&k=wdHsQuqY0Mqq1fNjZGIYnA%3D%3D%0A&r=BZ6CdqPuZxsk4U7Iz0ccrx2LhXuvsPtUHXMi0Eoaai4%3D%0A&m=sKLWFlIWxBj0TaP%2FdI7MVw9wnOauF5vd5AUcB5wo%2Fhg%3D%0A&s=91e0600e54e372050aab711d0eb5b875eafd198a12084c288d8edb54d86b4052> last year.  It covers a few other topics such as submit buttons that are disabled until the user fills the form correctly.



Jonathan



--

Jonathan Avila

Chief Accessibility Officer

SSB BART Group

jon.avila@ssbbartgroup.com<mailto:jon.avila@ssbbartgroup.com>



703-637-8957 (o)

Follow us: Facebook | Twitter | LinkedIn | Blog | Newsletter





-----Original Message-----
From: Madhavi Herle [mailto:Madhavi_Herle@infosys.com]
Sent: Thursday, April 09, 2015 3:09 AM
To: w3c-wai-ig@w3.org<mailto:w3c-wai-ig@w3.org>
Subject: Forms and error messages



Hello everyone,



If testing a large form with a lot of input fields, where would you prefer to see the error messages?

Is it before the start of the form with links to the form fields or error messages just before the form fields?



I am currently testing a huge form with over 30 fields. The error messages are before the form and are links to the form fields. The fields are not marked as mandatory, so the chances of human error is high. Each mandatory field has a hazard sign saying that there is an error with the information provided which is positioned after the fields.



With a long list of error messages linking back to the fields, I think keyboard and screen reader users will find this difficult.



I am suggesting the following:

- include * for each mandatory field, so the users can avoid errors to start with.

- Define the meaning of * before the start of the form

- Move the hazard icon before each mandatory field and change the alt of each hazard icon to be field specific.

- Since the forms are quite old, I am asking them to retain the links as is. This might help some user groups.



What are your thoughts on this?



Thanks in advance.



Regards,

Madhavi



**************** CAUTION - Disclaimer ***************** This e-mail contains PRIVILEGED AND CONFIDENTIAL INFORMATION intended solely for the use of the addressee(s). If you are not the intended recipient, please notify the sender by e-mail and delete the original message. Further, you are not to copy, disclose, or distribute this e-mail or its contents to any other person and any such actions are unlawful. This e-mail may contain viruses. Infosys has taken every reasonable precaution to minimize this risk, but is not liable for any damage you may sustain as a result of any virus in this e-mail. You should carry out your own virus checks before opening the e-mail or attachment. Infosys reserves the right to monitor and review the content of all messages sent to or from this e-mail address. Messages sent to or from this e-mail address may be stored on the Infosys e-mail system.

***INFOSYS******** End of Disclaimer ********INFOSYS***