WAVE Tool Showing Errors on Your Site
WAVE is itself the detection tool. Cross-validate findings with axe DevTools and Lighthouse for comprehensive coverage.
Why it matters
WAVE (Web Accessibility Evaluation Tool), developed by WebAIM, is one of the most widely used accessibility testing tools in the industry. When WAVE shows errors on your site, it means automated detection has found definite WCAG violations — not just potential issues. Each red error represents a failure that blocks real users with disabilities from accessing content. WAVE errors are also frequently used as evidence in ADA demand letters and lawsuits: attorneys run WAVE on target sites and attach the error report to demonstrate violations. A site with 50+ WAVE errors is a clear target for serial ADA plaintiffs. More importantly, these errors represent real barriers: a blind user who cannot identify a form field cannot complete your checkout; a deaf user who cannot find the transcript link cannot consume your video content.
Symptoms — what you'll see
If your site has this problem, you may observe any of the following:
- WAVE browser extension shows red "Errors" count on the page badge
- Yellow/orange "Alerts" indicating potential issues that need review
- Red icons overlaid on the page pointing to specific problematic elements
- WAVE sidebar shows categories: Errors, Alerts, Features, Structural, ARIA, Contrast
- High error counts on forms, images, navigation, and dynamic content areas
- Contrast errors highlighted across multiple text elements
Common causes
- Images uploaded via CMS without alt text (common in WordPress and Shopify)
- Icon-only buttons and links without accessible names
- Form inputs added quickly during development without labels
- Color palettes chosen for aesthetics without contrast checking
- Template-based sites where the base template has accessibility issues that multiply across pages
- Third-party widgets and embeds that introduce their own violations
- PDF links and documents that are not screen-reader accessible
How to fix it
- 1Install the WAVE browser extension (Chrome/Firefox) or use wave.webaim.org for public pages.
- 2Fix Errors first (red icons) — these are definite WCAG violations: missing alt text, empty links, missing form labels, empty buttons.
- 3Empty links ("linked image missing alternative text"): add descriptive alt text to the linked image or aria-label to the <a> element.
- 4Missing form labels: add <label for="..."> elements or aria-label attributes to all inputs.
- 5Missing alt text: add appropriate alt attributes to all <img> elements.
- 6Empty buttons: add descriptive text or aria-label to buttons that contain only icons.
- 7Address Contrast errors: use the WAVE contrast panel to see exact failing ratios and update colors.
- 8Review Alerts (yellow) for structural and best-practice issues: redundant links, suspicious alt text, long alt text, justified text.
- 9Do not over-fix WAVE Alerts — some are informational and may be intentional. Validate each in context.
Code example
<!-- WAVE Error: Empty link -->
<a href="/home"><img src="logo.png"></a>
<!-- WAVE Error: Empty button -->
<button><svg><!-- icon only --></svg></button>
<!-- WAVE Error: Missing form label -->
<input type="text" name="search" placeholder="Search..."><!-- FIXED: linked image with alt text -->
<a href="/home"><img src="logo.png" alt="Acme Co - return to homepage"></a>
<!-- FIXED: icon button with aria-label -->
<button aria-label="Search"><svg aria-hidden="true"><!-- icon --></svg></button>
<!-- FIXED: visible label + placeholder for hint -->
<label for="site-search">Search</label>
<input type="text" id="site-search" name="search" placeholder="Search products...">How to test your fix
After applying the fix, verify it works using these testing steps:
- Install the WAVE Chrome or Firefox extension from wave.webaim.org.
- Visit each key page type: home, product/service, about, contact/form, blog, checkout.
- Click the WAVE icon and review the summary: aim for 0 Errors on all pages.
- Click each error icon on the page to see the HTML and learn the specific violation.
- Use the "Details" panel in the WAVE sidebar for a full list with descriptions.
- Export results: WAVE Pro (paid) allows CSV export for audit tracking.
- Re-run after fixes to confirm errors are resolved.
Frequently asked questions
What is the difference between WAVE Errors and Alerts?+
WAVE Errors (red) are definite WCAG violations that must be fixed — missing alt text, empty links, missing labels. WAVE Alerts (yellow/orange) are potential issues that require human judgment — redundant alt text, very long alt text, possible headings. Alerts are not always violations; some are intentional design choices.
How many WAVE errors is considered serious?+
Any number of WAVE Errors is a problem, as each represents a definite WCAG violation. However, context matters: 5 errors on a simple brochure site vs. 5 errors on a checkout form have different impact levels. For legal purposes, even a single missing form label on a checkout page can be the basis for an ADA complaint.
Can WAVE be used for automated testing in CI/CD?+
WAVE API (wave.webaim.org/api/) is available for automated testing, but requires a paid plan. For CI/CD automation, axe-core (open source) is more commonly integrated into testing pipelines. Use WAVE for manual spot-checks and axe-core or Pa11y for automated pipeline testing.
WAVE says my contrast is failing but our designer says it looks fine — who is right?+
WCAG contrast requirements are mathematical, not perceptual. WAVE uses the WCAG 1.4.3 formula which requires 4.5:1 for normal text. Even if the color combination looks fine to someone with typical vision, it may be unreadable for users with low vision, cataracts, or color blindness. WCAG is the legal standard; aesthetics are secondary.
Does passing WAVE mean my site is fully accessible?+
No. WAVE, like all automated tools, catches approximately 25–35% of WCAG violations. It cannot detect cognitive accessibility issues, keyboard navigation problems in complex widgets, screen reader announcement failures, or content that is technically present but confusing. Automated tools are a starting point — supplement with manual keyboard testing and screen reader testing.