W3C home > Mailing lists > Public > w3c-wai-eo@w3.org > July to September 2001

Fw: Building a business case for web accessibility

From: Laux <laux@mho.net>
Date: Sat, 11 Aug 2001 15:06:42 -0600
Message-ID: <005401c122ad$956cb2e0$a52e9dd0@uswc.uswest.com>
To: "EOWG" <w3c-wai-eo@w3.org>

----- Original Message -----
From: "Jim Thatcher" <thatch@attglobal.net>
To: <sec508@trace.wisc.edu>
Sent: Friday, August 10, 2001 8:38 PM
Subject: RE: Building a business case for web accessibility


> Glenda,
>
> If you have to repair pages assuming the work was initially done poorly,
> very inaccessibly, figure .5 hour per page to fix. And you put the $ value
> on those hours. It is relatively expensive to correct existing sites.
>
> Almost all sites have some form of template that most pages are based on
or
> grow from. In the grand scheme of things it costs nothing to get that
> template correct and then produce pages ad nauseum that are accessible.
The
> net - costs next to nothing.
>
> I have often heard a 10% - 15% figure for the cost of accessible stuff
(web,
> software). But I think that is too high. Almost all access issues are
found
> in the templates and when access is fixed there, hundreds/thousands of
pages
> go by for free.
>
> So I am going to place a stake in the ground and estimate that generally
> accessible web is almost negligible. If you are producing page at a time
and
> doing it accessibly it is just not that much work. If you are using
> templates it is even less.
>
> Think of a complex table. Think of how much time goes into planning on how
> to present that table, and how to code it. Then add a bit to have the
> correct accessibility coding. A nit relatively.
>
> Why don't people say that? Do y'all disagree?
>
> Jim
> jim@jimthatcher.com
> Accessibility Consulting
> http://jimthatcher.com
> 512-306-0931
>
> -----Original Message-----
> From: owner-sec508@trace.wisc.edu [mailto:owner-sec508@trace.wisc.edu]On
> Behalf Of Glenda Watson Hyatt
> Sent: Thursday, August 09, 2001 4:49 PM
> To: sec508@trace.wisc.edu
> Subject: RE: Building a business case for web accessibility
>
>
> Ok, let's try this perspective...how would you respond to a web developer
> who says its too expensive to make a site accessible, particularly an
> existing site?  How do you convince him otherwise?
>
> As analogy, it costs something to comply with the ADA -- ramps, grab bars,
> visual signals, etc etc etc.  There's definitely a cost involved.  Isn't
it
> the same with web accessibility?
>
> Cheers,
> Glenda
> > >
> > >  -----Original Message-----
> > > From: Glenda Watson Hyatt [mailto:Glenda@eaglecom.bc.ca]
> > > Sent: Thursday, August 09, 2001 2:43 PM
> > > To: Webwatch; WebAIM accessibility forum; Sec508@Trace. Wisc. Edu;
> > > Disacc@Yahoogroups. Com
> > > Subject: Building a business case for web accessibility
> > >
> > > Hi all,
> > >
> > > Please pardon this cross-posting.  I'm seeking some information and
need
> > to
> > > cast my net as widely as possible.
> > >
> > > I am attempting to build a business case for web accessibility
> > and am look
> > > for actual dollar costs [or percentage of total cost] of making sites
> > > accessible, both new and existing sites.  We all know the legal
> > > ramifications, but has any research been done into the actual cost to
> > > business?  I'd appreciate any and all leads to information.  And, as
> > usual,
> > > time is a factor here.  Thanks.
> > >
> > > Looking forward to hearing from you.
> > >
> > > Cheers,
> > > Glenda
> > >
> > > *********
> > > Glenda Watson Hyatt
> > > Soaring Eagle Communications
> > > "Creating freedom and power through accessible communications"
> > > E Mail: mailto:Glenda@eaglecom.bc.ca
> > > Website: http://www.eaglecom.bc.ca
> > > Want to know how to make your website accessible to more people?
> > > Subscribe to our FREE newsletter by emailing
> > > mailto:newsletter@eaglecom.bc.ca
> > >
> > > *********
> > >
> >
>
>
Received on Saturday, 11 August 2001 17:34:46 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Friday, 27 April 2012 10:33:31 GMT