Re: SC 1.3.1 Failure: Using Scripting Events instead of anchors to create links

So, how can we characterize the difference between processing information
and pure navigation in our test procedure, so that it is clear that this
failure doesn't prohibit Next and Prev buttons in wizards?


On 4/7/06 8:50 AM, "Gez Lemon" <gez.lemon@gmail.com> wrote:

> On 07/04/06, Loretta Guarino Reid <lguarino@adobe.com> wrote:
> <quote>
> The wizard example seems compelling to me. The distinction between a link
> action and other actions seems to get blurry as we consider web
> applications.
> </quote>
> 
> Unfortunately, badly written web applications are blurring good
> usability practice.
> 
> Next and previous buttons on wizards are (or should be) actions, as
> they're processing information. If they're not processing actions
> (rather than merely fetching a resource), why was it a wizard in the
> first place? Just jump to the last page, and you're done. If the
> buttons are purely for navigational purposes, then the usual approach
> is to show the visited stages of the process as a list of links, so
> that people can easily navigate through the wizard, which is what you
> would expect from a navigation aid. Suppose a user is on step 7 of a
> multi-stage wizard and wants to review what they entered for stage 2 -
> displaying the links allows users to quickly go back and review any
> stage, and continue through the wizard. If a previous button is used
> purely for navigation, then the user needs to press the previous
> button 5 times.
> 
> Best regards,
> 
> Gez
> 
> --
> _____________________________
> Supplement your vitamins
> http://juicystudio.com

Received on Friday, 7 April 2006 16:01:30 UTC