I recently finished up a web app that allows breast cancer patients to find
matching clinical trials (breastcancertrials.org) They do this by entering
in a (potentially) lengthy health history first. One trick I used is to only
expand the sections where they had detail to supply ("Have you had
chemotherapy?") but this still made for a long page. So I mocked up two
versions, one long page, and one with tabs that chunked the history into
more manageable sections.
So I did some usability testing, and with our typical users (middle aged
women) the tabbed design was the clear winner. I ended up tweaking the
design to put a "Go to the next tab" link at the bottom of each page,
because with a lengthy history, the tabs often scrolled out of view, plus it
reinforced that the tabs were working like wizard pages. (We considered the
idea of a wizard, but realized that fairly often users would want to go back
to a prior section and update their answers.
Hope that helps.
Michael Moore
--
Michael B. Moore • Pure InfoDesign • www.pureinfodesign.com
On Wed, Mar 11, 2009 at 1:54 AM, rejeeb <[email protected]> wrote:
> Can anyone refer me to some material that explores, what are the
> heuristics of when to use along page with scroll v/s Tabbed Page?
> ________________________________________________________________
> 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
>
________________________________________________________________
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
