CHI-WEB Archives

ACM SIGCHI WWW Human Factors (Open Discussion)

CHI-WEB@LISTSERV.ACM.ORG

Options: Use Forum View

Use Monospaced Font
Show Text Part by Default
Show All Mail Headers

Message: [<< First] [< Prev] [Next >] [Last >>]
Topic: [<< First] [< Prev] [Next >] [Last >>]
Author: [<< First] [< Prev] [Next >] [Last >>]

Print Reply
Subject:
From:
Paola Kathuria <[log in to unmask]>
Reply To:
Paola Kathuria <[log in to unmask]>
Date:
Wed, 11 May 2005 02:20:46 +0100
Content-Type:
text/plain
Parts/Attachments:
text/plain (78 lines)
Doug Heathcoat wrote:
> The three models I can think of are:
> 1. Page Top: error messages are displayed at the top of the page, above
> the form.
> 2. Field Associated: error messages are displayed near the form field with
> which the error is associated.
> 3. Separate Page: error messages are displayed on a separate page and the
> user must go back to the form to correct the error.

In 2000. Scott Luebking sent an excellent message to the
list entitled "Some results from testing forms errors" based
on tests with blind users. The resulting recommendations
would benefit all users.

Original message:
http://listserv.acm.org/scripts/wa.exe?A2=ind0011B&L=CHI-WEB&P=R7305&I=-3

An extract from the original list message follows:

====
Recommendations:

    1.  redisplay form with error messages instead of error messages on a
        separate page

    2.  put a summary of number of error messages as close to the beginning of
        a web page as possible.  (this will help blind users
        more quickly identify what is happening with the page.)

    3.  put a link from the summary to the first error message area.
        (this can also be useful for sighted people who scan if they
        are unfamiliar with the web page.)

    4.  an error message should come before the field with errors

    5.  error messages should be clearly indicated by a color or an
        image to help people who are scanning.  a combination of color
        and image is probably appropriate in case the user is color-blind

    6.  the error messages should be comprehensive enough so that a
        blind user doesn't have to look around the form for information
        to build a context for the error message

    7.  links should be provided after the error field to navigate
        to the previous or next errors. if the error is the last in the
        form, there should be a link to the submit buttons for the form.

    8.  error messages or links should be numbered e.g. (2/7) , to give a
        context when going through errors
====

I applied some of these recommendations to forms I subsequently
programmed, notably the addition of links to the relevant fields
within the error messages.

Examples:

+ http://www.limov.com/ppig2005/
+ http://www.limov.com/rcl20/order.lml
+ http://www.crash.org.uk/homelessness/publications.lml

(In the last two, the fields labels change colour to mark
the error or required information.)

Please note that these are all live forms. Press the submit
(or preview) button without filling in any form information
to see the error messages and form changes.


Paola

    --------------------------------------------------------------
    Tip of the Day: Suspend your subscription if using auto replies
     CHI-WEB: www.sigchi.org/web POSTINGS: mailto:[log in to unmask]
              MODERATORS: mailto:[log in to unmask]
       SUBSCRIPTION CHANGES & FAQ:  www.sigchi.org/web/faq.html
    --------------------------------------------------------------

ATOM RSS1 RSS2