WAVE Updates Coming
Now that the first version of the WAVE Toolbar for Firefox has been released, we’re shifting our development attention back to the main server-side WAVE application. Updates being prepared include several bug fixes, a few new tests (plus tweaks to existing tests), and numerous performance improvements. However, we still have time to add things to that list, so if there’s a particular WAVE bug you really want fixed, or a feature you’d love to see implemented, now is your chance to let us know. (Just add a comment to this post).
March 31st, 2008 at 10:53 am
I would really like to have the ability to select a particular standard for testing (Section 508, WCAG A Compliance, WCAG AA Compliance, WCAG AAA Compliance).
It would also be nice to have an alternate report view that displays the standard checkpoints and indicates the code line numbers where errors are occurring.
I teach accessibility at a community college and am looking forward to seeing this product develop into a great tool for students and web professionals.
March 31st, 2008 at 3:24 pm
Both server-side and toolbar WAVE get confused by IDs being case-sensitive when evaluating labels.
Recently in this form:
https://www.applyweb.com/public/contribute?s=lawcont
I noticed it was flagging the labels for LAWCONT-DESIGNATE_GIFT_Other and LAWCONT-DESIGNATE_GIFT_OTHER as being a ‘multiple form label’ error, when in fact these are 2 separate labels for 2 separate form elements.
April 27th, 2008 at 12:45 am
I did send a message via your feedback form but didn’t get a reply and then I saw this post. I am having trouble with the page:
http://www.hazleceramicsguide.com/join.php
which reports 1 accessibility error but doesn’t place any red markers on the page. Hopefully that is something you can fix.
There is a small WAVE referrer link at the bottom for you to try it yourself.
April 27th, 2008 at 7:10 am
Chris-
The error does not show because it is flagging an error within a
April 28th, 2008 at 12:44 am
Many thanks, Jared
“within a” script?
I did wonder whether it might be in the reCAPTCHA widget. But it would be really nice to know what the error is exactly so that I can report the problem to the reCAPTCHA people or fix or work around it in my PHP code or whatever. Would it be possible to place a red marker beside the script somewhere?