Today we launched some web site changes.

Cosmetic and Client-side Changes

• Fixed some layout issues to resolve overlapping page elements at very low resolutions. WAVE pages now span the entire screen width.
• Fixed some minor script compatibility issues with Internet Explorer 6.
• Added a few script-driven accessibility enhancements.
• Dramatically optimized and cleaned up the scripting used on the site. It now uses 2 .js files instead of 6. Progressive enhancement of WAVE functionality (streamlined interface, tooltips, accordian effect on homepage, automatic toggling of page styles, etc.) is done using the MooTools framework.

Updated Help Page

One of the most common questions we get from WAVE users is, “What guidelines does WAVE use? WCAG? Section 508? Others?” This question is now properly addressed on the Help page. In short, WAVE does not limit itself to specific guidelines. We use common guidelines to help develop WAVE tests, but WAVE includes as many real life aspects of accessibility as we have been able to come up with. WAVE also flags some accessibility issues as errors even though they are not identified in any set of guidelines. Our approach with WAVE is to help web content become accessible, not merely compliant with guidelines or standards. While WAVE is a powerful tool in determining compliance, it does not directly identify aspects of compliance or non-compliance to specific guidelines.