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

Re: How to convince businesses to be accessible...

From: Ryan Eby <ebyryan@msu.edu>
Date: Fri, 6 Oct 2000 17:25:02 -0400
Message-ID: <006401c02fdb$e37a72d0$c3b90a23@bob>
To: <w3c-wai-ig@w3.org>
A friend of mine did this on his site with ASP (as a learning tool - his
site is not commercial). He wrote all his content in XML pages and then used
a ASP page to check the HTTP header to find the browser version and then
apply a different XSL stylesheet depending on the browser. It was then sent
off to the browser as HTML. If the browser was one that didn't support
images than he used a stylesheet that left out the images and HTML that
might have been a hindrance. It may seem like a lot of work but it really
wasn't. He only created the content once and about a half dozen stylesheets.
And the ASP code he wrote once and then copy and pasted it for the other
pages changes the content variable to point to the proper file. It worked
quite well as far as I could see (on lynx, NS, and IE). I'd give you the
link but he is running it locally on his machine now because of lack of
extra funds for hosting). Are there any problems with this approach that I
am missing.
Ryan Eby
----- Original Message -----
From: "Reidy Brown" <rbrown@blackboard.com>
To: <w3c-wai-ig@w3.org>
Sent: Thursday, October 05, 2000 8:24 PM
Subject: RE: How to convince businesses to be accessible...

> I'm a little surprised that no one (especially Kynn) has talked about
> server-side logic to create customized pages based on user preferences.
> true that many small business web sites are static, but a growing number
> commercial sites use Cold Fusion, ASP, JSP, cgi,php or other server side
> technology. It's not a trivial matter, certainly, but it is possible to
> up the site to generate no-image, low-bandwidth, and high-bandwith pages
> demand. With a little additional thought, you can set the system to handle
> client-side logic (javascript) where possible or desired (and many people
> _do_ want this) and server-side logic where necessary.
> Admittedly, it's not a quick-fix solution, but it is a viable option for
> well-engineered web sites. And for those that don't have the capability
> in-house, something like Edapta is an up-and-coming solution. I'm not
> familiar enough with Edapta's functionality, but I suspect that this is
> sort of thing it's designed to do for existing sites.
> Reidy
> -------------------------------------------
> Reidy Brown
> Accessibility Coordinator/
> Software Engineer
> Blackboard, Inc.
> -------------------------------------------
> -----Original Message-----
> From: David Poehlman [mailto:poehlman@clark.net]
> Sent: Thursday, October 05, 2000 6:24 PM
> To: Anne Pemberton
> Cc: Dave J Woolley; w3c-wai-ig@w3.org
> Subject: Re: How to convince businesses to be accessible...
> I think we need to carefully define accessability.  it is no more just a
> question of who need what to access in terms of disability.  it is fast
> becoming what will the software and hardware will bear and I am here to
> tell you that that will decrease drastically over time.  graphics should
> get out of the way of information and lower costs for the connection
> mean more buying power for those businesses trying to sell to us.
> --
> Hands-On Technolog(eye)s
> ftp://poehlman.clark.net
> http://poehlman.clark.net
> mailto:poehlman@clark.net
> voice 301-949-7599
> end sig.
Received on Friday, 6 October 2000 17:23:06 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 13 October 2015 16:21:10 UTC