Category: Testing and Evaluation
WAVE
Also known as: WAVE, Web Accessibility Evaluation Tool
Simply put
WAVE is a web accessibility evaluation tool used to help identify potential accessibility issues on web pages. The evidence provided does not contain authoritative details describing WAVE as an accessibility tool, so this entry cannot be fully substantiated from the supplied sources.
Formal definition
The evidence packet does not include any source describing WAVE as a web accessibility evaluation tool; the provided sources address unrelated meanings of the word 'wave' (dictionary, physics, and a small-business software application). A precise, practitioner-level technical definition cannot be produced from this evidence without introducing unsupported facts. Note that automated evaluation tools generally detect only a portion of accessibility issues and that manual and assistive technology testing are also required; this guidance is not legal advice.
Why it matters
The evidence digest supplied for this entry does not contain any authoritative source describing WAVE as a web accessibility evaluation tool. The available sources address unrelated meanings of the word "wave", a dictionary definition of the gesture, a small-business accounting software application, and physics descriptions of waves as propagating disturbances that transfer energy. Because of this, the significance of WAVE as an accessibility testing tool cannot be substantiated from the provided material, and this section cannot responsibly elaborate on its importance without introducing unsupported claims.
Who it's relevant to
Accessibility engineers and QA testers
Practitioners who evaluate web content for accessibility may use automated evaluation tools as one part of a broader testing process. Because automated tools detect only a subset of issues, they should be paired with manual and assistive technology testing. Note that this entry cannot describe WAVE specifically, as the supplied evidence does not substantiate its features or methodology.
UX designers and developers
Teams building and maintaining web interfaces often incorporate automated checks into their workflows to surface potential accessibility problems early. Any specific claims about WAVE's capabilities would require authoritative sources not present in the evidence digest.
Compliance officers and legal counsel
Those assessing conformance to standards such as WCAG should understand that passing automated checks does not guarantee full accessibility or immunity from legal claims. Requirements evolve through regulation and case law, and qualified legal counsel should be consulted. This entry does not offer legal advice and cannot verify details about WAVE from the sources provided.
Inside WAVE
Automated Evaluation Engine
WAVE (Web Accessibility Evaluation Tool), developed by WebAIM, programmatically analyzes a page's rendered content and markup to surface potential accessibility issues against criteria commonly aligned with WCAG.
Errors
Flags for issues that are likely to create barriers for users, such as missing alternative text or empty form labels, which generally warrant remediation.
Alerts
Indicators of elements that may cause problems and require human judgment to confirm, such as redundant links or possible heading structure concerns.
Features and Structural Elements
Highlights of items that support accessibility when used correctly, including alternative text that is present, ARIA usage, and document structure elements like headings and regions.
Contrast Checking
A component that evaluates text color contrast against background to identify potential shortfalls relative to WCAG contrast expectations.
Visual Overlay and Code View
An interface that places icons over the rendered page and links findings to the underlying markup, helping reviewers locate and interpret each reported item.
Delivery Formats
Available as a browser extension and a web-based tool, allowing evaluation of publicly accessible pages and, via extensions, pages behind authentication or in local environments.
Common questions
Answers to the questions practitioners most commonly ask about WAVE.
Does passing WAVE with no errors mean my website is fully WCAG compliant?
No. WAVE, like all automated testing tools, can detect only a portion of potential accessibility issues. A clean automated scan does not confirm conformance with all applicable WCAG success criteria, because many criteria require human judgment. Achieving accessibility generally requires combining automated tools like WAVE with manual review and assistive technology testing.
Does using WAVE guarantee protection from ADA-related legal claims?
No. WAVE is a testing tool that helps identify certain accessibility issues; it does not confer legal compliance or immunity from claims. Legal exposure under the ADA and related authorities is shaped by regulation, agency guidance, and evolving case law. Organizations should treat WAVE as one part of a broader accessibility program and consult qualified legal counsel for advice specific to their situation.
How is WAVE typically used in an accessibility testing workflow?
WAVE is commonly used for an initial or ongoing automated evaluation of individual web pages, helping teams surface issues such as missing alternative text, certain contrast problems, and structural concerns. It is generally paired with manual testing and assistive technology testing to address issues that automated tools cannot detect.
What kinds of issues can WAVE help identify?
WAVE can help flag a range of potential issues that lend themselves to automated detection, which may include missing form labels, missing alternative text, some color contrast concerns, and heading or structural markup problems. It reports the results visually against the page, but the presence or absence of flags does not represent a complete assessment of all applicable WCAG success criteria.
Can WAVE test an entire website at once?
WAVE generally evaluates one page at a time in its common form. Testing a full site typically requires running the tool across multiple representative pages and templates. Teams often supplement page-level checks with broader processes to cover different page types, states, and user flows.
Should WAVE be the only tool used to evaluate accessibility?
No. Because automated testing detects only some issues, WAVE is best used alongside other methods, including manual code and content review, keyboard-only testing, and testing with assistive technologies such as screen readers. Relying on a single automated tool leaves gaps that only human evaluation can reliably address.
Common misconceptions
A page with no WAVE errors is fully accessible and WCAG conformant.
Automated tools like WAVE detect only a portion of accessibility issues. Many WCAG success criteria require human judgment, and manual testing with assistive technologies such as screen readers and keyboard-only navigation is generally needed to assess actual usability and conformance.
Passing WAVE checks guarantees legal compliance and protection from ADA claims.
Meeting the criteria a tool can measure does not guarantee compliance with the ADA or immunity from legal claims. Legal obligations depend on the applicable authority and evolve through regulation and case law; this is not legal advice and qualified counsel should be consulted.
WAVE alerts are false positives that can be ignored.
Alerts flag items that may cause problems and that WAVE cannot automatically confirm. They require a human reviewer to determine whether an actual barrier exists rather than being dismissed by default.
Best practices
Use WAVE as one part of a broader evaluation process that also includes manual review, keyboard testing, and testing with assistive technologies rather than relying on it alone.
Treat reported errors as candidates for remediation and manually investigate each alert to confirm whether a real barrier is present before deciding on action.
Verify color contrast findings against the specific WCAG level you are targeting, most commonly AA, and confirm which criteria apply to your context.
Use the browser extension to evaluate pages that require authentication or exist in staging or local environments, since the web-based tool is limited to publicly reachable URLs.
Review the structural elements WAVE reports, such as headings and landmark regions, to confirm they convey a logical and meaningful document structure to assistive technology users.
Document tool findings and remediation decisions, and consult qualified legal counsel and current agency guidance for questions about applicable legal requirements.