Re: How to demonstrate how well disabled people understand

["David Poehlman" <poehlman1@home.com>]

so we are speaking the same language after all.  Well, the only thing
most phones do is allow you to enter and start over or cancel if you
will.  so in that case, it is a short list.  I live in the computer
world so understand What is said if it is said clearly as this is.
Thanks.

----- Original Message -----
From: "Scott Luebking" <phoenixl@sonic.net>
To: <uaccess-l@trace.wisc.edu>
Sent: Wednesday, November 07, 2001 9:54 PM
Subject: Re: How to demonstrate how well disabled people understand


Hi, David

I agree.  Part of the problem is that we use terminology in different
ways.  In the computer world, "functionality" and things like
"functional specs" have particular meanings.  Maybe I should just try
describing a little how I would approach evaluating text entry in an
interface.

One thing I would probably do is identify appropriate functionality.
What functionality needs to be provided for a user to enter text in it?
Another way to look at the question is what does a user do when entering
text?  The functionality should include:

    a.  enter text

    b.  review text

    c.  edit text

    d.  clear text

    e.  get help while performing functions

    f.  reorient back to task when disrupted

    g.  complete entering text

    h.  cancel the task requesting text

How do I know this is desirable functionality?  I know from various
HCI readings and watching users.  People not familiar with the field
might need to do a lot of "hitting walls" to get the same info.
It would be kind of like designing something and ignoring the
research that has been done in failure analysis.

If an interface provides a text entry feature, there needs to be a way
to access each of the desired functions in this list.  The access also
needs to be efficient, with minimum vulnerability to error and easy to
learn.

Some phone interfaces let you use the number pad for entering text.
How would the list of functionality be used for evaluating
the text entry feature of a phone interface for sufficiency, efficiency,
accuracy and and ease of learning?

Scott


> what are the functional barriers being reduced?  Let us say that it is
> blind ness.  In my interface, I have done several things to
lower/remove
> barriers.  I have provided tactile guidance and audio interactivity
and
> tactile interactivity in forms that I have found to be most effective
at
> reducing/eliminating barriers posed by functional limitations due to a
> complete lack of vision.
>
> I don't remember how we used the trace interface.  It did leave out
> those who cannot use synthesized speech as a means of interaction but
it
> provided for audible review and correction if necessary.  I know I
will
> miss key points.  I am not even sure what this exercise is leading to
> because I have already pointed out that I am not an chi person but I
> have had a lot of good experience in what does and what does not work
> from many sides of the issue and many of my pre-conceptions have been
> replaced by experiences.  Some have even been borne out but that is
due
> in part to the fact that I don't jump to conclusions where design is
> concerned but rather apply a bit of deduction to te process of
> developing a response to a need.
>
> I will impart this bit of anecdota and we'll leave it here.
>
> I was traveling on a plane and in the seats next to me were two women
> who spoke in german from the time they sat down till the time the
flight
> was over.  Although I could hear every thing they wre saying clearly
and
> caught the rythm of their conversation, inflection and could
understand
> some of the mood of the discussion, I could in no way begin to
> understand the content of the conversation.  This has relivance here
> because You as a person who has knowledge in a particular field in a
> particular way can talk to someone else with those properties and I
can
> listen in and would most likely not understand much.  In some ways,
> We've been having two one sided conversations.