Ray Olszewski wrote:
> >This thread is about creating web pages that are usable by blind
> >people and others.
>
> You've only discussed issues relating to blind people, so I wonder if you
> could expand a bit on the "others".
Well, how about people who don't have any money, and use lynx
on a 386sx running Linux?
It doesn't have to be about physically disabled people. It is,
to me, just as much about monetarily disabled people, or
disabled equipment. Or the guy who's at his friend's house,
setting up a LEAF system, using his web-cellphone to read the
howto. How about that one? Could get pretty common.
> The main other group I see discussed in usability articles and such is
> people with impaired motor skills who use alternate pointing devices and
> typing devices (like mouth sticks). Lynx doesn't seem particularly
> beneficial to them ... I'd guess that they gain more than they lose from a
> well-designed GUI ... but what GUI issues do they face that we should think
> about? (For example, one alternate pointing device is something that tracks
> eye movement. Does a GUI make use of this easier or harder?)
I beg to differ. Choosing a target and pointing a mouse requires
precision, no matter what pointing and display devices are used;
but lynx has very simple movements - up, down, left, right keys.
Try getting really drunk and really cold, and tell me which one
is easier: point or keypress... ;->
> There are the deaf too, of course, who will become more important to the
> design debate as sound itself becomes more important to design, but that's
> not yet, at least not for a development site like LEAF.
Egads! Sound? When? What for?
> Related to that ... since you raised this question ... how usable is
> Sourceforge itself by various disabled groups? Having an access-friendly
Good question.
> home page for LEAF does seem to me like a good thing, but the meat is in
> places like the download page and the documentation page, which are
> (currently, at least) embedded in the Sourceforge structure.
Well, as we come across a need for this, we can deal with it.
> Finally, we seem to be thinking about dsabled *users* of LEAF and the LEAF
> site. What issues are there with respect to a disabled *developer* wanting
> to participate in LEAF?
Again, I think that's a bridge we should cross when we come to it.
We can't prepare for every possibility; instead, we should allow
the possibilities to present themselves and then we come up with
practical solutions.
If a blind person has trouble using SF to download, that is the
time when we say "Okay, it's time for us to stop depending on
SF for our downloads; we'll make a page at c0wz". If somebody
wants to help develope who can't use SF, we'll work with them.
Then again, maybe we won't. Maybe we'll say, sorry, too much
work for us.
Either way, there's no need for us to prepare in detail for all
of those events...instead, we lay down a good framework (pages
that look good in lynx, for example) and build on that when we
need to.
> --
> ------------------------------------"Never tell me the odds!"---
> Ray Olszewski -- Han Solo
> Palo Alto, CA [EMAIL PROTECTED]
> ----------------------------------------------------------------
--
rick -- A mind is like a parachute... it only works when it's open.
ICQ# 1590117 [EMAIL PROTECTED] (work) [EMAIL PROTECTED] (home)
Help with LRP: lrp.c0wz.com 68 Camaro wanted: dingo.mcrnet.net
Windows users: Please delete me from your contact list when done
corresponding with me. You should trim your contact list often anyway.
My opinions don't exist, and as such, are not anyone elses. I don't
represent anyone, not even myself, and especially not my employer..
_______________________________________________
Leaf-devel mailing list
[EMAIL PROTECTED]
http://lists.sourceforge.net/mailman/listinfo/leaf-devel
