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

Re: hmmm

From: Kynn Bartlett <kynn-hwg@idyllmtn.com>
Date: Fri, 14 Aug 1998 08:48:00 -0700
Message-Id: <3.0.5.32.19980814084800.009d35b0@mail.idyllmtn.com>
To: Jamie Fox <jfox@fenix2.dol-esa.gov>
Cc: "'Web Accessibility Initiative'" <w3c-wai-ig@w3.org>
At 09:30 a.m. 08/14/98 -0400, Jamie Fox wrote:
>A colleague of mine suggested that a good idea would be to implement an 
>automatic feature in browsers and or server software that would strip away 
>the inaccessible stuff from pages to present accessible pages.  Does this 
>seem like a realistic option.  I know it would still leave out users with 
>older browsers.

Accessibility is a case of thoughtfulness, good design principles,
planning ahead, a clean grasp on HTML, and a desire to make pages
accessible.

There's no algorithm to automatically convert inaccessible pages to
accessible pages -- and there never will be.  It's impossible.

The real work is not found in the tags -- if it were, then any
browser could simply make a page accessible.  The hard work of 
accessibility occurs at the _implementation_ level.

Example:  There's no way that a program could make this accessible.

  <IMG SRC="bd32.gif">
  <A HREF="somepage.html"><IMG SRC="lpwf.jpg"></A>

The author didn't include enough information to make it clear what's
happening here -- and no machine can arbitrarily decide what needs
to happen above, enough to make it usable in even Lynx.

(On the other hand, if you're curious, look at my neglected experiment
at http://www.cgu.edu/degrade/ -- a tool for authors.)

--
Kynn Bartlett <kynn@hwg.org>
Vice President, Marketing and Outreach, HTML Writers Guild
  http://www.hwg.org
Received on Friday, 14 August 1998 11:38:46 GMT

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