I have no connection to CAST.

I haven't gave Bobby much thought. Simply because good web page design takes care of most of these issues.

For example "If an image conveys important information beyond what is in its alternative text, provide an extended description." Use the "longdesc" tag ..."Most current web browsers do not yet support the "longdesc" attribute. In order to provide for both the present and the future, we recommend using both the "longdesc" attribute and following the image by a descriptive (or D) link. The d link, a convention established by the CPB/WGBH National Center for Accessible Media, is a way for you to link manually to the target of the LONGDESC by linking a small "d" positioned near the image"

-If we use that tag it wont pass other wc3 compliancy tests.

Also, "Mark up any quotations with the Q and BLOCKQUOTE elements." - Why I always thought " and " do just fine

"If the submit button is used as an image map, use separate buttons for each active region." Why would you use an image map for any navigational purposes without providing a textual navigation for backup?

I personally view Bobby as a suggestion tool and not the law. You want your site to be accessable to everyone. So look at what warnings you have and think of things you can do to make it easyer for the surfer. For example a textual version of the navigation should be provided. You can just add text links at the bottom of the page as a footer.

If you're using pictures of charts, provide a link to a table version of the data. Within the image or a link bellow it.

What do you guys think?

[This message has been edited by xelA (edited 02-25-2001).]