W3C home > Mailing lists > Public > w3c-wai-gl@w3.org > April to June 2000

RE: Bobby output daunting on accessible page

From: <pjenkins@us.ibm.com>
Date: Mon, 15 May 2000 19:39:59 -0400
To: w3c-wai-gl@w3.org
cc: chuckop@coppersoftware.com, uaccess-l@trace.wisc.edu, basr-l@trace.wisc.edu, "Michael Cooper" <mcooper@cast.org>, w3c-wai-er-ig@w3.org
Message-ID: <852568E0.0082026D.00@d54mta04.raleigh.ibm.com>



>Yep.  The Bobby report is verbose to the point of being useless.  The CAST
>folks think that this is a feature.  What can be done?

I put more of the "blame" on us WAI folks for forcing or at least
requesting that CAST make Bobby check every little thing that the WCAG
guidelines ask for - even if it had to be a manual check.  Sometimes we err
on academic purity rather than practical usefulness.  But the good news is
that the next release of Bobby will allow one to select which checks to
conduct.  For example, you could ask Bobby to only check the machine
checkable priority one items.  You will even be able to select which
priority one items to check.  Of course CAST have been working to improve
the algorithms of the checking that it does.  So most of the problems that
Charles noted should be fixed as well as others he didn't note.

What else can be done you ask?  - review and comment on the Evaluation and
Repair Techniques document - upon which Bobby will be basing it's checking
algorithms.  See http://www.w3.org/TR/AERT

Regards,
Phill Jenkins, IBM
Received on Monday, 15 May 2000 19:41:08 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Monday, 7 December 2009 10:47:04 GMT