- From: Michael Cooper <mcooper@cast.org>
- Date: Fri, 5 Jan 2001 12:18:28 -0500
- To: "Schuur, Shawn M" <schuurs@pluto.dsu.edu>, "'Jim Thatcher '" <thatch@attglobal.net>, "'wai-ig list '" <w3c-wai-ig@w3.org>
Hi - no, your problem with Bobby is not unique, and it certainly is aggravating. There are a number of causes of the problem of Bobby stopping after testing a number of pages, that we're tracking down and fixing one by one. It boils down to, for one reason or another, Bobby runs out of memory and then stops. Each release we make is a little better in this regard. If you would like to send details of your problem to us at bobby@cast.org, including the URLs you're testing, this may help us to further track down this problem. Meanwhile we generally suggest that people simply analyze smaller chunks of the site. I know that's not the perfect workaround, but can help you to get your task done. Michael Michael Cooper Bobby Project Manager Technical Designer CAST, Inc. 39 Cross St. Peabody, MA 01960 Tel +1 978-531-8555 x265 TTY +1 978-538-3110 Fax +1 978-531-0192 Email mcooper@cast.org http://www.cast.org/ http://www.cast.org/bobby/ -----Original Message----- From: w3c-wai-ig-request@w3.org [mailto:w3c-wai-ig-request@w3.org]On Behalf Of Schuur, Shawn M Sent: Wednesday, January 03, 2001 10:58 AM To: 'Jim Thatcher '; 'wai-ig list ' Subject: RE: Methodology Does anybody know why the Java version of Bobby only goes through so many pages before it locks up? Or is it just mine that is having problems? -Shawn Schuur -----Original Message----- From: Jim Thatcher To: wai-ig list Sent: 1/3/01 9:32 AM Subject: RE: Methodology Mike, You can also use Bobby, a tool that checks the checkable accessibility items: http://www.cast.org/bobby. That's right, isn't it, David? Jim jim@jimthatcher.com Accessibility Consulting http://jimthatcher.com 512-306-0931
Received on Friday, 5 January 2001 12:18:51 UTC