Jim,

I think there is a major potential accessibility issue, or at least one of
"equivalent access" with .net that needs to be addressed.

One feature of .net, as I have seen it explained, is that a user can log in
to "his or her" desktop from any computer on the network.  For the user of
the conventional keyboard, monitor, and mouse, this would be easy.  But if
you use alternative access technologies, then those would have to also be
available.  Your screen reader would have to be resident on the system, and
be part of your log-in preferences.  Your alternative input system drivers
would also have to go with you from computer to computer.  That would mean a
very tight integration for AT and the environment.

Microsoft has said that they don't want to be in the AT business, and we
generally agree that we don't want them to be there either.  But how could
they not in this case?

Denis Anson, MS, OTR/L
Assistant Professor
College Misericordia
301 Lake St.
Dallas, PA 18612
 

-----Original Message-----
From: * EASI: Equal Access to Software & Information
[mailto:[log in to unmask]]On Behalf Of Jim Rebman
Sent: Monday, January 29, 2001 7:38 AM
To: [log in to unmask]
Subject: .net and accessibility?

Can anybody comment on .net and any potential accessibility issues that you
may see.

Just heard of this and don't really even know what it is all about, but it
is starting to get some attention around this campus.

Thanks,

Jim

---------------------------
James A. Rebman

Cognitive Levers Project
Center for Life-Long Learning and Design (L3D)
University of Colorado, Boulder

"In times of change, the learners will inherit the earth, while the learned
will find themselves beautifully equipped for a world that no longer
exists."
- Eric Hoffer