RE: Methodology

Mike,

I am get trashed for saying this, but I think the easiest way of getting a
quick overview is to use a text-based browser like Lynx. This will give you
a baseline overview of the understandability of a page and the major areas
that need work.

Once this is done, you can go  on and use an audio browser like IBM's
Homepage Reader.

Hope this helps.

dc

---------------
David M. Clark
16 Harcourt Street, #2I
Boston, MA  02116
617-859-3069 : 401-679-0239 (eFax) : 617-290-3410 (cell)
http://www.davidsaccess.com
david@davidsaccess.com

-----Original Message-----
From: w3c-wai-ig-request@w3.org [mailto:w3c-wai-ig-request@w3.org]On Behalf
Of Mike Baker
Sent: Wednesday, January 03, 2001 4:42 AM
To: w3c-wai-ig@w3.org
Subject: Methodology


Can anyone share a methodology for testing and analyzing existing sites for
accessibility? I'm curious as to which specific steps you feel are
essential and where the majority of your focus lies.
Thanks,
Mike Baker
bakerm@zin-tech.com
ZIN Technologies, Inc.
3000 Aerospace Parkway ~ Brook Park, OH 44142
Phone: 216/977-0363 ~ Fax: 216/977-0421

Received on Wednesday, 3 January 2001 09:32:12 UTC