RE: Single Browser Intranets (was: Web Accessibility Myths)

>
> when you do that, you can communicate effectively and easily with
> whatever user
> agent comes down the pike...
>
> gregory.
>
> --------------------------------------------------------

I am sorry to interrupt this idealistic statement, but in the realm of
computer support, this is simply not true.   Different agents come with
their own baggage.  As someone who must oversee computer support in our
department, I can report firsthand the near impossibility of supporting
whatever software the user decides to put on their machine.  Yes, if
accessibility is an issue, support has top priority.  If it is a case of
mere preference, less priority is attached.

More so, stepping outside of computer support into communication theory, I
can't think of one theoretical model that does not consider the
agent/medium's outlet as a very important consideration.

I would have to agree with the person who stated earlier that this is
delving into an non-accessibility issue. Sure, accessibility should be there
within the organization -- but that accessibility would better be achieved
by an effective use of the organization's computer support and communication
resources.

Yes, the long-term implications of establishing software/hardware standards
should be considered heavily when establishing said standards, but to say
that this standardization in itself is bad for accessibility merits a
challenge.

Wayne

Wayne Crotts
Information/Computer Services
Institute on Human Development and Disability
College of Family and Consumer Sciences
The University of Georgia
Athens, GA 30602

Received on Tuesday, 26 October 1999 02:32:08 UTC