AxisProof — accessibility-compliance warden for EU ecommerce sellers

1. One-liner

AI catches the WCAG failures scanners miss and keeps a court-defensible EAA compliance dossier current for EU online stores.

2. Trend signal — why now?

The European Accessibility Act (EAA) became enforceable on 28 June 2025 with no grace period for existing digital services. It pulls every ecommerce service sold to EU consumers under EN 301 549 / WCAG 2.1 AA — regardless of where the seller is headquartered. By 2026 enforcement is live and physical: the Swedish Post and Telecom Agency has opened its first regulatory cases specifically against e-commerce sites, and consumer-advocacy groups are filing complaints at scale. Penalties bite by country — Germany up to €100,000 per violation, France up to €50,000 with service bans for repeat offenders, Italy public naming of offenders.

Two things just changed the math:

1. The cheap escape hatch died. The FTC fined overlay vendor accessiBe $1M (2025) for falsely claiming its widget makes any site WCAG-compliant. 1,023 sites running accessibility widgets were sued in 2024 — the widget became evidence of negligence. The National Federation of the Blind opposes all overlays; 70%+ of users say overlays make sites harder to use. The $10/mo overlay is now worse than nothing.

2. The expensive option (manual audit) just got automatable. Automated scanners catch only 30–40% of WCAG issues; the other 60% (screen-reader semantics, keyboard traps, focus order, announcement gaps) needed a human at $800–$8,000/mo. In January 2026 agentic tools (BrowserStack’s AI accessibility agent, TestSprite, TestMu) started simulating NVDA/JAWS/VoiceOver and keyboard-only flows and reasoning about semantic accuracy — manual-equivalent detection at software cost. Those tools target developers in IDEs. Nobody has packaged that detection as a compliance product for the non-technical merchant who’s actually on the hook.

Provenance:

• Signal 1 (demand): EAA enforceable June 2025, no grace period; Sweden PTS opened first ecommerce regulatory cases in 2026; fines to €100K/violation; 71% of ecommerce leaders sell into the EU — https://www.levelaccess.com/blog/penalties-for-eaa-non-compliance/ , https://www.deque.com/blog/early-signs-of-eaa-enforcement-across-europe/ — 2026-06-13
• Signal 2 (feasibility): Agentic AT-simulation (screen reader + keyboard) reasoning about semantic accuracy became real in Jan 2026 (BrowserStack AI agent, TestSprite, TestMu); automated scans still catch only 30–40% — https://testguild.com/accessibility-testing-tools-automation/ , https://qaskills.sh/blog/ai-accessibility-testing-tools-2026 — 2026-06-13
• Signal 3 (economic): FTC $1M order against accessiBe (2025) for false WCAG claims; 1,023 widget-using sites sued in 2024; Shopify-store remediation quoted $4K–$25K; one lawsuit ~$30K+ — https://accessibe.com/blog/knowledgebase/accessibility-lawsuits-impact-for-ecommerce , https://testparty.ai/blog/the-2026-guide-to-ada-website-lawsuits-what-to-do-when-you-get-sued-and-why-your — 2026-06-13 Category: Tech-unlock

3. The opportunity

The accessibility-compliance market for SMB ecommerce is split into three bad options:

• Overlay widgets ($5–500/mo): legally toxic post-FTC, actively used as evidence against you, hated by disabled users. Yet they own the Shopify app store because they’re cheap and promise one-click magic.
• Automated scanners ($10–100/mo): honest but blind — they find 30–40% of issues, miss the screen-reader and keyboard failures that real complaints and lawsuits are built on. Owner gets a green checkmark and a false sense of safety.
• Manual audit / source-code remediation ($800–$8,000/mo + $4K–$25K up front): actually works, but agency-priced and slow. Out of reach for a merchant doing €3–40M with no in-house a11y expertise.

The gap: manual-equivalent detection at scanner-tier price, delivered as a compliance posture, not a dev report. AxisProof crawls the storefront, drives it like a screen-reader/keyboard user, finds the failures that matter, tells the owner what to fix in plain language (and which ones the theme/app caused), re-checks on every site change, and continuously assembles the dated evidence file + accessibility statement an enforcer or plaintiff’s lawyer will ask for. We don’t fake compliance with a widget. We prove it and keep proving it.

4. Target market

• Primary customer: Owner / ecommerce-ops lead at an EU-selling online retailer, 10–250 staff, under €50M turnover (deliberately above the microenterprise exemption of <10 staff / €2M, so legally on the hook — and below the enterprise tier that already has a legal team and Deque). Shopify, WooCommerce, or light custom storefronts. Includes non-EU (US/UK) sellers shipping into the EU.
• Why they buy (their words): “Sued despite using a theme marketed as accessible.” “Got a demand letter out of nowhere.” “Our overlay app turned out to be the thing they pointed at in court.” They want to not get fined and not get sued, with proof they can hand a regulator.
• Rough TAM reasoning: EU ecommerce is hundreds of thousands of SMB storefronts; ~71% of ecommerce leaders sell into the EU. Even capturing the slice that is mid-sized (above the micro exemption, below enterprise) and EAA-aware is 100k+ reachable accounts. At €1.5–4K ACV, a low-single-digit-percent share is a $5M+ business.
• Why now for them: Enforcement is live in 2026 with real inspections and complaints; their existing overlay just became a liability; and a competitor in their category getting fined/named (Italy publishes offenders) is the trigger event that makes them search this week.

5. Product sketch (MVP)

• One-click connect for Shopify (and a URL-crawl mode for WooCommerce/custom) — no code, no embedded widget.
• Journey-based detection: AI drives the key flows (home → product → cart → checkout, search, account) as a screen-reader/keyboard-only user and reports the real WCAG 2.1 AA failures — focus traps, missing labels/announcements, illogical tab order, unreachable controls — not just a static scan.
• Plain-language fix list, prioritized by legal risk, with “this was caused by your theme / this app / your content” attribution so the owner knows whether to fix, swap, or escalate to a freelancer.
• Continuous re-check: every theme update, app install, or product launch triggers a re-run; owner gets an alert when a change breaks compliance.
• Court-defensible dossier: dated history of scans, issues found, remediation timestamps, and current status — the “we acted in good faith and here’s the evidence” file enforcers and plaintiffs’ lawyers ask for.
• Auto-generated, always-current EN 301 549 accessibility statement the EAA legally requires, hosted and version-tracked.
• Severity scoring framed as legal exposure (€ risk, not just a count), so a non-technical owner understands what to fix first.

6. AI angle — what’s load-bearing

Remove the AI and this collapses into a static scanner (the 30–40% tool that already failed the market). The load-bearing AI is agentic assistive-technology simulation: a vision-and-reasoning agent that operates the store the way a blind keyboard user would, judges whether an announcement is meaningful (not just present), decides whether a flow is completable, and writes a human-readable explanation + fix. That semantic judgment — “this aria-label is technically there but says ‘button button’” — is exactly what only humans could do until 2026, and exactly the 60% that scanners miss and lawsuits are built on. The AI is the product; the dossier and statement are the packaging.

7. Localization angle (if any)

This is the localization play — EU-first by regulation, not by language. The wedge is jurisdictional: EN 301 549 as the technical standard, member-state-specific penalty framing (German per-violation fines, Italian public naming, French service bans), and the legally-required accessibility statement in the local format. Multilingual screen-reader testing (the store renders in DE/FR/IT/ES) is a natural second wedge a generic US ADA tool ignores. A US-headquartered seller shipping into the EU is squarely in scope and underserved — they think “we’re not a US-ADA target” and miss the EAA entirely.

8. Business model — path to $1M–$5M ARR

• Pricing: €99/mo (single store, monthly re-check, statement + dossier) → €249/mo (continuous monitoring, change-triggered re-checks, multi-language) → €399/mo (multi-store / agency-managed). Position against the cost of one lawsuit (~€30K) and manual audit (€800–8K/mo), not against the $10 overlay.
• ACV: ~€2,000–3,000 blended.
• To $1M ARR: ~400 stores at €210/mo blended × 12 ≈ €1.0M.
• To $5M ARR: ~1,700 paying stores, or a smaller base plus an agency/reseller tier where one web agency manages 20–50 client stores under one account.
• Expansion path: per-store add-ons, multi-language testing, “managed remediation” marketplace (route the fix list to vetted freelancers, take a cut), and an agency white-label tier — the agency channel is where ACV compounds.

9. Go-to-market wedge — first 100 customers

• Mine the public lawsuit/complaint trail. Court dockets and demand-letter chatter (Shopify community threads, r/shopify, EU consumer-group complaint announcements, Italy’s public list of named offenders) surface businesses that have just been hit or named. DM/email them a free 2-minute AT-simulation video of their own store failing checkout. The freshly-stung convert fast.
• Web/Shopify agencies as the channel. Agencies building EU storefronts are now liable-by-association and being asked “are we EAA-compliant?” by every client. Offer a white-label reseller tier; one agency relationship = 20–50 stores.
• Anti-overlay positioning content + the FTC hook. Publish “your accessibility widget is now evidence against you (FTC fined accessiBe $1M)” and rank for “EAA compliance Shopify,” “is my overlay legal,” “accessibility statement EU.” This is a category where buyers are actively, fearfully searching — intent is high, not top-of-funnel.
• Partner with disability/a11y consultants who refuse to touch overlays and need an affordable detection layer to hand SMB clients they currently can’t serve profitably.

10. Build complexity — justification

Medium. Off-the-shelf: WCAG ruleset, browser automation, vision+reasoning LLMs, Shopify OAuth. Custom work is the journey-driven AT-simulation harness (driving real flows as a screen-reader/keyboard user and judging semantic meaning reliably enough to stake a legal dossier on) plus per-platform crawl quirks and the dossier/statement generator. A technical pair ships a credible v1 in 10–14 weeks; the detection-quality bar (low false positives, defensible findings) is the real engineering risk, not the plumbing.

11. Gating checklist

Gate	Pass?	Note
Legal in target market	✅	Selling compliance tooling; we detect and document, we don’t fake compliance via overlay.
Ethical — no harm / dark patterns	✅	Opposite of the overlay grift — genuinely improves access for disabled users.
Market exists (evidence above)	✅	Live enforcement, fines, lawsuits, FTC action, crowded (if bad) incumbent field.
1–5 person team can build this	✅	Technical pair, 10–14 weeks to v1.
Launchable with <$50K / ₹40L	✅	Inference + automation infra + a domain expert advisor; well under cap.

All five pass.

12. Feasibility score

Axis	Weight	Score	Notes
Problem intensity	20	17/20	Live fines (€100K+), lawsuits ($38K avg, 50/week in Denver-equivalent waves), demand letters now. Hair-on-fire for the freshly-hit.
Demand evidence	15	13/15	FTC $1M ruling, 1,023 sites sued, Shopify forum threads, 71% sell into EU, paid alternatives at scale. A skeptic nods.
Build feasibility	15	11/15	AT-simulation now exists but detection-quality bar is real engineering; pair in 10–14 weeks.
Distribution clarity	15	10/15	Named channels (lawsuit trail, agencies, intent search) but the Shopify app store is contaminated by $5–10 overlay noise; conversion uncertain.
Revenue mechanics	15	11/15	Pricing benchmarkable vs €30K lawsuit / €800–8K audit, but the app-store price floor pressures perceived value; must sell as legal insurance.
Time to first revenue	10	8/10	Self-serve trial-to-paid; revenue in 4–8 weeks off the lawsuit-trail outreach.
Defensibility	10	5/10	Execution-only — WCAG is public, AT-simulation commoditizing. Moat = detection quality, dossier lock-in, brand-as-legal-insurance.
Total	100	75/100

13. Qualitative modifiers

Founder-fit tags

technical-heavy · domain-expertise-required — needs an engineer who can build reliable agentic AT-simulation and a partner with real accessibility/legal-compliance knowledge so the dossier holds up.

Key assumptions to validate (3–5)

1. Assumption: EU SMB merchants will pay €99–399/mo for detection+dossier when the app store sells “compliance” for $10. How to test: Put a real pricing page in front of 40 EAA-aware merchants pulled from the lawsuit/complaint trail; measure willingness vs. “I’ll just keep my overlay.”
2. Assumption: AI AT-simulation catches materially more real, defensible issues than scanners, with low false positives. How to test: Run AxisProof + a leading scanner + a paid human auditor on 15 stores; compare overlap, misses, and false-positive rate.
3. Assumption: The lawsuit/complaint trail is a reliable, repeatable lead source. How to test: Source 200 freshly-hit/named merchants in 30 days; measure reply and demo-conversion on personalized failing-checkout videos.
4. Assumption: Agencies will resell/white-label rather than build their own checklist. How to test: Pitch 10 EU storefront agencies; close 2 reseller LOIs.

Risk flags

1. Distribution contamination: the Shopify app store trains buyers to expect $10 “compliance,” and overlay vendors outspend on marketing. Risk of being judged on price next to a toxic-but-cheaper product. Mitigate by selling via the lawsuit trail + agencies, not the crowded app-store search alone.
2. Platform dependency: Shopify could ship native accessibility tooling, or change its app rules. Mitigate with platform-agnostic URL-crawl mode and the EU-regulatory framing Shopify won’t own.
3. Liability of the claim itself: if our dossier says “compliant” and a customer is still sued, we get blamed. Mitigate by framing output as evidence of good-faith remediation and current status, never a guarantee — and lean on the domain expert to keep claims defensible.
4. Regulatory drift: WCAG 2.2 / EN 301 549 updates and the EAA’s 2025 simplification revision could move the goalposts. Manageable (we update the ruleset) but requires ongoing domain attention.

14. Structured verdict

Score:                  75/100
Verdict:                GO
Confidence:             Medium
Best-fit builder:       Technical founder (agentic browser automation) + accessibility/compliance domain advisor
Time to revenue:        4–8 weeks
Capital to launch:      $8–15K (inference + automation infra + advisor)
Top 3 assumptions to validate first:
  1. €99–399/mo willingness vs $10 overlay habit — pricing-page test on 40 EAA-aware, lawsuit-exposed merchants
  2. AT-simulation finds more real, defensible issues than scanners at low false-positive rate — 3-way bake-off vs scanner + human auditor on 15 stores
  3. Lawsuit/complaint trail is a repeatable lead source — 200 sourced leads in 30 days, measure demo conversion
Kill criteria:
  - Abandon if <8% of 40 lawsuit-trail merchants show paid intent at €99+/mo after a personalized failing-checkout demo
  - Abandon if AI false-positive rate is high enough that the dossier can't be trusted as legal evidence (i.e. needs human review on every finding — collapses the cost advantage)
  - Abandon if Shopify or a funded incumbent ships manual-equivalent AT-simulation as a native/bundled feature before v1 launch

15. Next step — 1-week validation sprint

• Day 1–2: Pull 150–200 EU-selling merchants from the public lawsuit/complaint trail (Shopify community threads, EU consumer-group complaint announcements, Italy’s named-offender list). Hand-build a real AT-simulation of 10 of their checkouts failing.
• Day 3–4: Send each a 90-second personalized video of their own store failing for a keyboard/screen-reader user + a one-line “this is what an enforcer sees” and a €149/mo pre-order link. Run the 3-way detection bake-off (AxisProof prototype vs a leading scanner vs one paid human auditor) on 5 stores.
• Day 5: Decide. Go if ≥8% of contacted merchants click through to the pricing/pre-order page AND the prototype surfaces ≥2 real, human-confirmed issues per store that the scanner missed. No-go if intent is below threshold or the AI can’t beat the scanner on real findings without a human checking every result.

The result is falsifiable: either freshly-stung merchants pay for manual-equivalent detection at a software price and the AI demonstrably beats scanners — or they don’t, and this is just another tool drowning in the $10 overlay swamp.