>
>  I'm designing a simple registration process, four steps, each a small
>> form.
>> I want to create one page, with each step appearing below the other.. so
>> the
>> process sort of 'slides down' one page.
>
>
It sounds like all you're doing is creating a single-screen version of a
wizard. Some design criteria, should you take a crack at this:

1. Set expectations: make sure you tell people throughout the process how
many steps there are, what step they're on now, how many more there are to
go, etc. If you use an accordion design, this isn't really an issue, because
the number of panels answers the question.
2. Keep them moving forward: make sure the "Next" buttons trigger the next
screen state so people don't have to take a separate action to get to it. In
an accordion design, for example, the Next button in one panel should
collapse that panel and open the next one.
3. Keep the promises you make: if you set an expectation in the first screen
state that each form will be, say, 5 or so inputs long, then keep that in
tact throughout the other screen states. In other words, don't let people
think that each part will be short and easy and then spring a long form on
them in one of the steps.
4. Eliminate as much of the form as humanly possible. This is a registration
form—it's the barrier that will stop visitors from becoming customers. *Get
out of the way.* I can't stress this enough.
5. Provide feedback: use inline validation. This is a must-have form. Make
sure it does everything right.

I don't have an example of this I can point to without making you purchase a
license to a web app you'll probably have no interest in using, but I've
done this before, and it's worked very well, but only by strictly following
this criteria.

Hope that helps!

-r-
________________________________________________________________
Welcome to the Interaction Design Association (IxDA)!
To post to this list ....... [email protected]
Unsubscribe ................ http://www.ixda.org/unsubscribe
List Guidelines ............ http://www.ixda.org/guidelines
List Help .................. http://www.ixda.org/help

Reply via email to