W3C home > Mailing lists > Public > public-wcag-teamc@w3.org > September 2005

Action - propose techniques from harvest to develop

From: Sofia Celic <sofia.celic@nils.org.au>
Date: Tue, 13 Sep 2005 18:46:03 +1000
To: <public-wcag-teamc@w3.org>
Message-ID: <LJEEKBBBNGHHOJHGKNLFOECJDLAA.sofia.celic@nils.org.au>
Hi everyone,

The Techniques harvest document [1] for Guideline 2.5 currently has the
following for each SC:

[start harvest]

L2SC1 - If an input error is detected, the error is identified and provided
to the user in text.

General:
(a) validation of credit card formats;
(b) writing understandable 401 or 404 pages;
(c) provide a guess when desired page is not found "smart 404".

HTML: none.

CSS: none.

Script:
(a) client side validation and scripting alert;
(b) client side validation and add error text via the DOM.

Other: none.

L2SC2 - If an input error is detected and suggestions for correction are
known and can be provided without jeopardizing the security or purpose of
the content, the error is identified and the suggestions are provided to the
user.

General:
(a) Google "did you mean" example;
(b) Provide a list of words that are similar;
(c) Type 3 letters and provide a list of choices that begin with those
letters;
(d) Use soundex codes;
(e) Google suggest? http://www.google.com/webhp?Complete=1&hl=en;
(f) Show similar search results/matches;
(g) In page link from error message to field with the error;
(h) A featured link in amazon?;
(i) Query enhancements.

HTML: none.

CSS: none.

Script: none.

Other: none.

L2SC3 - For forms that cause legal or financial transactions to occur, that
modify or delete data in remote data storage systems, or that submit test
responses, at least one of the following is true:
(a) Actions are reversible.
(b) Actions are checked for errors before going on to the next step in the
process.
(c) The user is able to review and confirm or correct information before
submitting it.

General:
(a) Dividing processes into steps and allowing forward and backward nav.;
(b) Return a new form with only the incorrect fields available;
(c) Programmatically provide supplemental information - tooltips with
additional info or help.

HTML: none.

CSS: none.

Script:
(a) Alert/pop-up with "Are you sure?" and ok, cancel.

Other:
(a) Server side tech that allows users to log back in, see past transactions
and cancel.


L3SC1 - Additional context-relevant assistance is available for text input.

General:
(a) Confirmation window opens to show user action has completed;
(b) Provide spell checking;
(c) Help bubbles;
(d) Tooltips using title;
(e) Do not use same words or letter combinations to begin each item of the
list;
(f) Providing help link on every page;
(g) (annoying) assistant in the corner of the page.

HTML: none.

CSS: none.

Script: none.

Other: none.

[end harvest]


I propose the following initial items:
1. To discuss the appropriateness of some of the general items at a meeting.
I believe some may fall under general usability and as such would be out of
scope.
2. To develop techniques for the following categories:
 2.1 Identification of error occurrence only (e.g. username/password errors)
 2.2 Identification of error occurrence + where it occurred (e.g. omission
of required form fields)
 2.3 Identification of error occurrence + where it occurred + suggestions
(e.g. incorrect input format)
 2.4 User input review and correction.

I am a new member of the group (so lots of discussion I have not been a part
of), so I hope other people in the group will send amendments, suggestions,
information, etc as they feel is needed.

Thanks,
Sofia

[1]: http://www.w3.org/WAI/GL/2005/06/30-tech-harvest.html
Received on Tuesday, 13 September 2005 08:46:29 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Tuesday, 8 January 2008 14:18:47 GMT