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

RE: How Does BETSIE Work?

From: Simon White <simon.white@jkd.co.uk>
Date: Mon, 29 Jul 2002 17:59:04 +0100
Message-ID: <FDFC0668A850D246BC4231715D94904E0CD4BC@uranus.jkd.co.uk>
To: "Jim Ley" <jim@jibbering.com>, <w3c-wai-ig@w3.org>

And once the script issues have been dealt with, test the site with a screenreader, or better still ask someone who uses this type of assistive technology to test the site for you and report any problem areas.

Javascript is very easy to make accessible now, but one wonders why the need for scripting on navigation in the first place if you are looking to create an accessible site. BETSIE, in effect, just delivers a text-only version (and not a great one at that - although it was only designed as a quick fix.

For further information on BETSIE, see: http://betsie.sourceforge.net/

Kind regards
Simon

-----Original Message-----
From: Jim Ley [mailto:jim@jibbering.com]
Sent: 29 July 2002 17:42
To: w3c-wai-ig@w3.org
Subject: Re: How Does BETSIE Work?



"Martin McCormick" <martin@dc.cis.okstate.edu>

> I
> work that are created with Lotus Domino and would be accessible
> via lynx if not for all the javascript navigation.  I would like
> to see something automated because we all know how much trouble a
> second but never equal text site can be.

Why not just fix the javascript navigation, that's the accessibility
problem, and is one that is easily solved.

BETSIE, is a very poor alternative for most users.

Jim.


_____________________________________________________________________
VirusChecked by the Incepta Group plc
_____________________________________________________________________
Received on Monday, 29 July 2002 12:59:13 GMT

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