Find out if your site is a lawsuit risk in 60 seconds.
We scan for WCAG 2.1 AA and EN 301 549 violations and fix them in your actual HTML, CSS and templates. Not an overlay widget layered on top of code that stays broken.
Free scan. Results on screen, no signup. A few seconds.
42 more findings across 31 pages
Full itemised list, WCAG success-criterion mapping and a PDF you can hand to a developer.
The exposure is not hypothetical — 2025 in numbers
Published industry estimates for the 2025 calendar year, compiled from federal court filing trackers and accessibility litigation reports. Informational only — not legal advice.
What actually gets you compliant.
We find what scanners miss
An automated pass gets the obvious failures. Then we walk the site with a keyboard, trace the focus order, and run it through NVDA and VoiceOver — the tests that surface the issues plaintiffs actually cite.
- Keyboard-only walkthrough of every flow
- NVDA on Windows, VoiceOver on macOS and iOS
- Focus order traced against visual reading order
We fix the code, not the symptoms
Changes land as a pull request in your repo, or as edits in your CMS or theme. Your markup is genuinely different afterwards — which is the only version of this that holds up under scrutiny.
<div class="btn" onclick="addToCart()">Add to cart</div><img src="{{ product.image }}"><button type="button" class="btn">Add to cart</button><img src="{{ product.image }}" alt="{{ product.title }}">Fixes 3.3.2, 4.1.2 and 1.1.1 across 31 pages
You get proof, not a promise
Every finding, every fix and every re-test is dated and recorded. If a demand letter arrives, your lawyer has a document showing exactly what you did and when you did it.
It stays fixed
A theme update or a new product template can undo months of work in a single deploy. We re-scan on every deploy and alert you the moment something regresses.
An overlay is a script. A lawsuit is about your HTML.
Accessibility overlays sit on top of your site and rearrange things in the browser. They do not change the underlying HTML — so the code a court, an auditor or a screen reader actually reads is exactly as broken as it was.
A script layered over the problem
- Your HTML stays exactly as it was
- Screen reader users frequently report it makes things worse
- Nothing to hand a lawyer when a demand letter arrives
- The script is detectable, and firms search for it
- Renews every year, and the gaps renew with it
The problem itself, removed
- Violations fixed in your templates and components
- Verified by hand with NVDA, VoiceOver and keyboard only
- A dated audit trail and conformance report to hand over
- Nothing extra loads on your site at runtime
- Re-scanned on every deploy, so it does not drift back
Three steps. The first one takes a minute.
Free scan
Enter your URL and get a real report in seconds — your critical count, your conformance verdict, and the most severe violation in full, on screen. No signup needed.
Most people find something they did not know was there.
Audit
We manually test what automation cannot — keyboard paths, focus order, screen reader output, and every form and booking flow. Then we scope the work and price it.
A flat $1,500, paid up front. No scoping call to get started.
Remediation
We fix it in the source, document every change with a date, publish your accessibility statement, and keep monitoring so a future deploy does not undo it.
Twelve months of monitoring is included with remediation.
The failures that show up in demand letters.
Unlabeled form fields
Checkout, contact and booking inputs with no programmatic label and no error association. The most cited failure in ecommerce complaints.
Keyboard traps and focus order
Modals you cannot escape, menus that skip, focus that vanishes behind a sticky header, and invisible focus rings.
Colour contrast
Text and UI components brought to 4.5:1 and 3:1 without wrecking the brand palette you already paid for.
Missing alt text
Product photos, icons and infographics described properly — and decorative images correctly hidden from screen readers.
Screen reader semantics
Real buttons, real landmarks, correct roles and states — plus removal of the ARIA that is actively making things worse.
Heading structure
One h1 per page and a heading order that screen reader users can actually navigate the page by.
Video captions and media controls
Captions, transcripts and keyboard-operable player controls — including the autoplaying background video in your hero.
PDF accessibility
Intake forms, menus, price lists and patient paperwork tagged and reading-ordered — a common blind spot for practices.
Dates that are already on the calendar.
ADA Title II — larger public entities
State and local government serving 50,000+ population. Web content and mobile apps must meet WCAG 2.1 AA. Vendors get pulled in with them.
HHS Section 504 — 15+ employees
Healthcare providers receiving federal assistance — which includes most practices billing Medicare or Medicaid. Portals and intake forms are in scope.
ADA Title II — smaller entities
Public entities under 50,000 population, plus special district governments — school, water, transit and hospital districts.
HHS Section 504 — under 15 employees
Solo and small practices get an extra year. The standard they have to meet is identical when it arrives.
ADA Title III has no deadline. Private businesses — shops, restaurants, clinics, gyms, hotels — are already exposed to lawsuits today, and have been for years. There is nothing to wait for.
Selling to the EU? Different law, same failures.
Penalty ranges are set by each member state under national transposition of Directive (EU) 2019/882. Informational only — not legal advice.
A passing scan is not compliance. The EAA separately requires a published accessibility statement declaring your conformance level, listing known issues with fix dates, providing a complaints contact, and stating when it was last reviewed. We produce and maintain it.
Fixed scope, quoted before we start.
You get a number, a scope and a date before any work starts — and the number does not move.
Credited toward remediation within 90 days
Find out exactly where you stand, in a report you can act on or hand to someone else.
What's included
- Full automated scan across every template
- Manual keyboard and screen reader testing
- Prioritised report with severity and effort
- WCAG 2.1 AA and EN 301 549 conformance summary
- Delivered in 3 business days
Everything in Audit, and then we actually fix it — and stay on it for a year.
What's included
- Everything in Audit
- Source-code fixes in your repo, CMS or theme
- Re-testing and sign-off on every fix
- EAA accessibility statement, published and maintained
- 12 months of monitoring — a weekly automated audit, plus alerts on every deploy
Monitoring runs continuously, not weekly
One fix at the template level can clear the same violation across every location at once.
What's included
- Franchise groups, multi-location practices and portfolios
- Template-level fixes rolled across every site at once
- Continuous monitoring across all properties, not just weekly
- Early-warning alerts when a shared component regresses
- Scheduled re-scans with a dated conformance report each cycle
- Design system and component library review
- Procurement documentation and VPAT support
- Training for the team that maintains the sites
Final pricing depends on page count and platform. The audit fee is credited toward remediation if you proceed within 90 days.
FAQ
The questions buyers actually ask.
Still unsure? Run the free scan first — it answers most of this for your specific site.
No. An overlay is JavaScript that modifies the page in the browser after it loads; your HTML, templates and components are untouched. Courts have not accepted overlays as a defence, 1,416 businesses running one were sued anyway in 2025, and the FTC fined a major vendor $1M in April 2025 over exactly this claim.
See what a plaintiff’s attorney would see.
One URL, sixty seconds, and a straight answer about where your site stands today.
Free scan. Results on screen, no signup. A few seconds.