Your code stays inaccessible
Missing labels, keyboard traps and broken focus order live in your components. A script that runs after page load can't reliably repair them, and every release can bring them back.
An overlay widget adds a script on top of your site and leaves the code underneath unchanged. Wally audits your product against WCAG 2.1 AA, fixes issues in your source code, validates the result and documents it in a VPAT/ACR, in one fixed-price 30-day sprint.
How a code-level audit and remediation sprint compares with a JavaScript overlay on the points buyers and procurement teams check.
| What you're comparing | Wally 30-Day Sprint | Overlay widget |
|---|---|---|
| How it works | IAAP-certified auditors test your product, then developers fix issues in your source code. | A JavaScript snippet loads on top of your pages and adjusts them in the browser. |
| Changes your code | Yes. Fixes ship in your repository and stay fixed through future releases. | No. The underlying code is unchanged. |
| WCAG 2.1 AA conformance | Validated against WCAG 2.1 AA for the pages and flows in scope. | Cannot make a site conformant on its own. |
| Screen reader and keyboard users | Tested with real assistive technology and manual review. | Adds its own controls, which can conflict with the tools people already use. |
| Evidence for RFPs | A documented VPAT/ACR that reflects the audit and validation. | No audit-backed VPAT/ACR. |
| Pricing | Fixed $5,000 for the 30-day sprint. Scope confirmed on the first call. | Usually an ongoing subscription. |
| Time to result | 30 days from discovery to delivered VPAT/ACR. | Installs in minutes, but the code issues remain. |
| Human review | Every audit is led by an IAAP-certified specialist. | Mostly automated. |
Overlay features vary by vendor. Check each vendor's own documentation before you decide.
$1M
FTC order, April 2025
The Federal Trade Commission approved a final order requiring overlay vendor accessiBe to pay $1 million. The order bars the company from claiming its automated product can make any website WCAG compliant without evidence to back it up.
Read the FTC press release (opens ftc.gov in a new tab)Missing labels, keyboard traps and broken focus order live in your components. A script that runs after page load can't reliably repair them, and every release can bring them back.
Screen reader and keyboard users already have tools set up the way they need. A second layer of controls can conflict with those tools instead of helping.
Buyers ask for a VPAT/ACR that reflects a real audit of your product. An overlay subscription doesn't give procurement anything to review.
Display preferences such as larger text or higher contrast can be useful to some visitors. They are a convenience, not WCAG conformance, and they don't replace fixing the product.
One fixed-price sprint, led by IAAP-certified auditors, with fixes made in your codebase.
Week 1
Automated and manual testing of your agreed pages and flows against WCAG 2.1 AA.
Weeks 2–3
Code-level fixes, prioritized by severity, ready for your team to merge.
Week 4
The same auditor re-tests every in-scope page and flow.
Day 30
A completed VPAT/ACR and a published accessibility statement.