WAVE accessibility tool: how to read the report, and what to test after zero errors


Front-end developers who clear every WAVE error get a congratulations banner that still says manual testing is necessary. WAVE, WebAIM's free-to-run accessibility tool, marks a page with icons and counts the failures it detects in the code. Only humans, WebAIM says, can determine whether a page is accessible. Red icons mark what to fix, the others what to judge, and the manual testing can start in the same report.
From the first report to the keyboard test
#What the WAVE accessibility tool is and how to use it?
WAVE is WebAIM's free accessibility evaluation tool: it marks issues with icons on the page itself, red for errors that likely block people with disabilities. It runs from the form at wave.webaim.org for public pages, or as a Chrome, Firefox or Edge extension for private or dynamic ones. WAVE cannot tell whether a page is accessible or compliant; WebAIM says that takes manual testing.
#How to run the WAVE extension on a page before launch?
- Install the WAVE extension in Chrome, Firefox or Edge.
- Open the page and click WAVE's icon right of the address bar, or press Ctrl+Shift+U (Cmd+Shift+U on a Mac).
- Read the sidebar and the page's icons.
- Click the icon again, or refresh, to clear the report.
Edge uses that shortcut for Read Aloud, so set WAVE's own on its Manage Extensions page. WebAIM recommends the extension, especially for dynamic or private pages: it checks the page as the browser renders it and sends nothing to WebAIM.
Our demo is the “Book a groom” page of Biscuit & Bath, a dog grooming salon in Columbus, Ohio, still on the development server. Our extension, version 3.3.1.0, asked for no payment and no account.
#Which WAVE errors, contrast errors and alerts to fix?
Fix the red icons, errors and contrast errors alike, and judge each yellow alert. Only the error icons should go, WAVE's help page says, and a person still judges whether each affects users. The Details panel sorts findings into six counts: Errors, Contrast Errors, Alerts, Features, Structure and ARIA; green features probably help but need checking. On our first build, WAVE counted 3 errors, 1 contrast error and 1 alert. All four red items rank among the six most common failures on the million home pages WebAIM checks with WAVE yearly. In the WebAIM Million 2026, 95.9% of them had detected failures.
Marker 1. The summary counts: 3 errors, 1 contrast error, 1 alert. Marker 2. The red Missing form label icon under the Phone field. Marker 3. The red Empty button icon beside the next-week arrow.| WAVE item | Element | Fix |
|---|---|---|
| Linked image missing alternative text | Logo in the home link | alt="Biscuit & Bath, home" |
| Missing form label | Phone field, placeholder only | Visible <label>, “Phone” |
| Empty button | Next-week arrow | aria-label="Next week" |
| Very low contrast | Gray price note | #b3a993, 2.28:1#6b5f4e, 6.11:1 |
Both ratios are from WAVE's Contrast panel, against the 4.5:1 normal text needs; the label follows our guide to accessible forms. A zero in Contrast Errors leaves out text over background images, gradients, filters or background transparency, which WAVE does not check. For such text, measure both colors with the eyedropper in WAVE's color picker. If they fail, drag WAVE's Lightness sliders until they pass, or let our contrast checker suggest the closest passing colors.
The alert, “Redundant alternative text”, flagged the salon photo: its alt repeated the caption beside it, so a screen reader would repeat those words. We set alt="", and WAVE moved the photo to its features, as “Null or empty alternative text”.
Your images don't need alternative text
#Is a page accessible once WAVE shows zero errors?
Not necessarily: the absence of errors does not mean a page is accessible or compliant, WebAIM states, and WAVE never reports a page as “passed”. With the fixes in, our page showed zero errors, contrast errors and alerts. Its AIM Score rose from 7.6 to 10 out of 10, on a scale where 5 is about average. Above the score sat WebAIM's banner: “Congratulations! No errors were detected! Manual testing is still necessary to ensure compliance and optimal accessibility.”
#What the WAVE Order panel lists?
Manual testing starts one tab away. The Order tab lists every navigable element in tab order, the path of the Tab key, with its role and the name a screen reader reads. On our page it held 16 entries, from the logo link to “Book appointment”, day buttons included.
None of the five time slots made the list, though the mouse clicks them without trouble: entry 12, “Button: Fri 20”, leads straight to entry 13, “Text input: Your name”. The panel tells testers to look for listed elements that do nothing. Reading it for a missing control is the habit that found this page's problem.
Marker 1. The five time slots, with no order marker. Marker 2. Entries 12 and 13 in the list: “Button: Fri 20”, then “Text input: Your name”.So one report holds both, a tab apart: 10 out of 10 with no error or alert, and a booking page whose time slots the keyboard never reaches.
#What the keyboard test finds on the booking page?
Several kinds of people rely on the keyboard, the W3C notes. Blind people do, since aiming a mouse takes sight, and so do some people with hand tremors and people whose speech input software acts as a keyboard. For all of them, the booking has to work from the keyboard.
WebAIM's evaluation guide lists the keys to test with. Our test used four: Tab forward, Shift+Tab back, Enter for links and buttons, Space for buttons and checkboxes. From “Fri 20”, one press of Tab landed in “Your name”. With the form filled in, “Book appointment” answered “Choose a time to book.”, so the keyboard alone could not book.
Past the menus and four days, focus reaches “Fri 20”.
Focus jumps to “Your name”. No slot gets it.
Back to “Fri 20”. The slots are skipped again.
With the fields filled in, “Book appointment” answers “Choose a time to book.”
#Why the keyboard skips the time slots, and what it takes to fix them?
Each slot was a div with a click handler added by script. Without tabindex, a div stays out of the tab order, and no key press fires its click handler. WCAG, the W3C's accessibility guidelines, has a criterion named Keyboard: every function must be operable from a keyboard. It sits at Level A, the minimum level. Its one exception, input that depends on the path of a movement such as freehand drawing, does not cover a click on a slot.
Avoid
Marker 1. The five time slots, with no order marker.<div class="slot" data-time="9:00 AM">9:00 AM</div>
<div class="slot" data-time="10:30 AM">10:30 AM</div>Correct
Marker 1. The five time slots, with markers 13 to 17.<button type="button" class="slot" data-time="9:00 AM">9:00 AM</button>
<button type="button" class="slot" data-time="10:30 AM">10:30 AM</button>We changed one tag per slot and left the script alone: a native <button> gets focus by default and fires the same click handler for Enter and Space. The Order panel grew from 16 entries to 21. From “Fri 20”, Tab now lands on “9:00 AM”, Space picks a slot, and the keyboard alone booked a full groom at 10:30 AM. What the keyboard can reach now matches what the mouse can click. The new buttons keep the page's visible focus style, and what a screen reader says about the chosen slot is the next check.
#What to tell a client who wants a clean WAVE report?
Tell the client what WAVE covers, what the keyboard test found and what comes next, so a clean report reads as one step of testing. WAVE errors line up with WCAG 2.2 failures, and WebAIM says no automated tool, its own included, can check every issue in those guidelines. The AIM Score rates only what WAVE detects: errors, their density and alerts, against the million home pages WebAIM tests yearly. A high score “does not necessarily indicate that the page is highly accessible or compliant”, WebAIM warns.
Marker 1. The congratulations message, which says manual testing is still necessary. Marker 2. The AIM Score, 10 out of 10.WebAIM's terms of use call these machine-generated reports “not conclusive” and guarantee compliance with no standard or law. They also require WebAIM's written permission to use WAVE results for anything related to a legal action.
For a client worried about the ADA, the Justice Department's web guidance says a “clean” automated report does not necessarily mean everything is accessible. A few errors do not necessarily mean barriers either, and the guidance pairs a manual check with the checkers. WebAIM's guide also lists a screen reader pass.
NVDA screen reader: how to install it, set it up and test a web page
Biscuit & Bath's other pages still need the same pass. Includdy scans a page or a component and turns each non-conformity into a test plan anyone on the team can replay and a guided fix split into tickets. Both come from its AI and need a check before use.


