Scans and reports that help you find and fix barriers.
webada opens one page in a real browser, runs axe-core, and lists what those automated checks found, with guidance for each fix. An automated scan cannot certify WCAG or ADA compliance. There is no overlay widget.
A scan covers one page, the URL you submit. It does not
crawl other pages on the site. Run it yourself with
webada https://example.com.
These numbers come from three different counts. Do not add them together. Seyfarth ADA Title III, March 25, 2026 reports 3,117 federal lawsuits, 27% more than 2024. UsableNet’s 2025 year-end report counts 1,427 suits against companies that had already been sued, which it describes as 45% of federal filings in its own count (3,195 federal cases). That report does not say the repeat suits happened within a set number of years. EcomBack’s mid-year 2025 report counts 653 Shopify lawsuits, 32.42% of the 2,014 lawsuits in that first-half report.
From a URL to a prioritized fix list in three steps
The product is an automated scan plus a report a developer can work from. It is not a conformance certificate.
Send one page
Give webada one URL. Chromium renders the page, including markup produced by JavaScript, and axe-core checks that DOM. One page per scan.
Read the fix list
Each finding names the element, the axe-core rule, the WCAG success criterion when the rule has one, and how to fix it. Best-practice checks are listed as low hints, not as WCAG failures.
Hand off the report
Share the dated list with the developer who will edit the site. Running the scan again checks that same URL. Scheduled monitoring is not available yet.
What an automated scan can check
axe-core covers the rules a browser can test reliably. A person still has to review the rest of WCAG.
Rendered page
The scan runs after the browser load event, so client-rendered markup is part of the DOM axe-core sees.
Fix guidance
Each finding includes the element, a short fix, and the axe-core help page for that rule.
Severity, not a legal rank
High and medium follow axe-core impact for rules that map to a WCAG success criterion. Best-practice rules stay low.
One score, explained
Start at 100. Subtract 20 per high finding, 10 per medium, and 1 per low. The same formula is in the CLI, the API, and this site. It is not a certification.
CLI exit code
webada <url> prints the report and exits non-zero when any high-severity finding is present. There is no separate flag to turn that on.
Text or JSON
The CLI writes either format. A PDF report is not available.
Any stack, one URL
Shopify, WordPress, Squarespace, Webflow, or a custom app: the scan reads the DOM the browser built for the URL you gave it.
No overlays. Ever.
webada does not inject a widget. A widget does not change the underlying page, and a scan does not make a site compliant.
What a report looks like
These cards are webada’s own demo pages, not client sites. The broken demo is missing alt text, a page language, a form label, and link names. The empty-alt demo is a decorative image marked the way WCAG technique H67 describes, with alt="", and that is not a finding.
Agency pricing for a small client roster
Automated scans and written fix reports. Not a conformance certificate, and not an overlay.
Free scan
- One rendered page, checked with axe-core
- Issue list with fix guidance
- Text or JSON from the CLI
- Not a conformance certificate
Agency
- A scan of one URL per client site, up to 10 sites
- A written report per site: findings and fix guidance
- Delivered by email during the pilot
- Automated scans do not certify compliance
- No overlay widget
Scheduled re-scans, regression alerts, white-label PDFs, self-serve billing, and live calls are not part of this plan. Billing is not self-serve yet.
Request a homepage scan
Send one page URL and an email. The form stores the request. It does not run the scan, it does not crawl other pages, and sending it does not certify anything. To scan a page on your own machine, run webada https://example.com.
Questions, answered directly
What the scan does, and what it does not do.
Does a webada scan mean the site is compliant?
No. Automated scans cannot certify WCAG or ADA compliance. The score only counts what axe-core reported on that page. We are not lawyers. A record of findings and fixes can be useful context for counsel.
Why not use an accessibility overlay widget?
webada does not add an overlay. A widget sits on top of a page and does not fix the underlying markup. In April 2025 the FTC approved a final order requiring accessiBe to pay $1 million over claims that its widget made websites compliant. FTC press release, April 22, 2025.
What standard do you check against?
axe-core 4.14.0, running in Chromium after the page loads. That bundle includes automated WCAG 2.0, 2.1, and 2.2 rules plus best-practice checks. Best-practice rules are reported as low-severity hints and are not labeled as WCAG failures. Automation covers only part of WCAG. Manual testing is still required.
How long does a fix take?
It depends on the finding and the CMS. The report lists each one so a developer can work through them. webada does not offer live fix calls.
The site is on Shopify or WordPress. Can the scan read it?
Yes. The scan reads the rendered DOM, so the CMS does not change how a finding is detected. Applying the fix in a theme or plugin is work for the agency or the site owner. The report points at the element.
What if the scan reports nothing?
Then those automated checks found nothing on that page. Other pages were not crawled, and many WCAG criteria need a person. A clear automated result is not proof of conformance.
Scan one page. Get a fix list a developer can use.
The report says what axe-core found and how to fix it. It does not certify the site.
Request a one-page scan