RE: My TextOnly (text-equiv) Filter

> The index.html seems accessible to me. So why translate it into text-only
> version.

THIS one does, yes, at least kind of. Others less. If you look at index.html
in lynx, you will see [IMAGE] for the bullets etc. Other pages, for example
using frames, are not at all and a TextOnly (text-equiv) Filter could do
something about that and other things. Another idea I had recently, is
including a link to pdf2txt@adobe.com for PDF links. Or a warning before
binary links. -- Plus, TextOnly (text-equiv) page also loads faster, and
displays in EVERY browser, including hand-held small display thingies, not
just most recent 4.x. That's accessibility as well, isn't it?

> To make two versions of a website, graphical and text-only, cost to much
> time and money on maintanance. So I think this is not the way to go.

If the tool is fully automatical, it does not cost any time. If the tool is
completely free, it does not cost any time. So I think this is the way to
go. :-)

> practice. The major problem with accessibility of webpages at this moment
> is NOT there are graphics, but there are no ALT tags include with these
> graphics.
> I think a tool that let webmasters interactively enter ALT tags has the
> highest priority. If all graphics on the Internet has a good ALT tag and
> image map were handled well, I think the Internet is more accessible and
> there is no need for an alternative text-only version.

Interesting point, please read next msg to the list where I suggest two
study projects.

Regards,
Michael

----
Michael Vorburger <mike@vorburger.ch> & <michael.vorburger@epfl.ch>
QUOTE: "There is one thing stronger than all the armies of the world and
that is an idea whose time has come." (Victor Hugo)
HOMEPAGE: http://www.vorburger.ch

Received on Tuesday, 20 October 1998 19:10:00 UTC