W3C home > Mailing lists > Public > w3c-wai-ig@w3.org > October to December 1999

RE: single browser intranets

From: Scott Luebking <phoenixl@netcom.com>
Date: Tue, 26 Oct 1999 14:25:03 -0700 (PDT)
Message-Id: <199910262125.OAA06869@netcom3.netcom.com>
To: kynn-hwg@idyllmtn.com, phoenixl@netcom.com
Cc: W3c-wai-ig@w3.org, asgilman@iamdigex.net, cynthia.waddell@ci.sj.ca.us, sweetent@home.com
Hi, Kynn

I know of a couple situations where a company upgraded the software
dvelopment environment to a windows based one and the developers
had to move to companies which were still using old DOS environments.
I've also heard of problems withh upgrades in call center software.

A common problem in technology is that the developers are often little
obligation to address accessibility.  It is their customers who have
that challenge.  However, if the technology consistantly remains
inaccessible, the customers have an "out" via "reasonableness".

Scott


> At 01:57 PM 10/26/1999 -0700, Scott Luebking wrote:
> >What happens when a company needs to
> >switch to software which has become a standard for their industry,
> >but which is inaccessible?
> 
> Smart companies will put industry pressure on the creators of their
> software to promote accessibility, so that they don't have to worry
> about facing lawsuits because of the software they buy.
> 
> Does the scenario you describe above exist in practice today?  I
> think it might be better to look at what companies ARE doing rather
> than what they COULD be doing or SHOULD be doing; so examples (and
> I don't doubt they exist) would be useful.
> 
> --
> Kynn Bartlett <kynn@hwg.org>
Received on Tuesday, 26 October 1999 17:24:52 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Tuesday, 19 July 2011 18:13:45 GMT