PixelRamp — code-level EAA remediator for small EU webshops

1. One-liner

Rewrites your Shopify theme’s actual code to pass WCAG 2.1 AA and drafts the EAA statement — no lawsuit-magnet overlay widget.

2. Trend signal — why now?

The European Accessibility Act (EAA) went enforceable 28 June 2025. Any webshop selling to EU consumers must meet WCAG 2.1 AA across the whole purchase journey. This stopped being theoretical in the last twelve months:

• Enforcement is live and biting. France’s DGCCRF sent formal notices to Auchan, Carrefour, E.Leclerc and Picard (Nov 2025); the first EAA lawsuits filed in France Nov 2025; a June 2026 court ordered Carrefour to fix its site and app within six months under daily financial penalties. Germany’s BFSG started generating private warning letters through its competition-law framework within weeks of the Aug 2025 activation.
• The incumbent category just got legally discredited. The FTC fined accessiBe $1M (Jan 2025) for claiming its overlay widget makes any site WCAG-compliant in 48 hours — “false, misleading, unsubstantiated.” A $1.2M class settlement followed. UsableNet’s tracker shows 22.6% of 2025 ADA web lawsuits targeted sites that had an overlay widget installed. The National Federation of the Blind and 700+ accessibility pros publicly oppose overlays.
• The AI unlock landed. LLMs can now reliably read and rewrite Liquid/HTML/CSS theme code — add semantic markup, alt text, ARIA labels, keyboard focus order — at the source, not as a JS band-aid. axe-core + a code-editing model turns a $10K–50K manual remediation into a mostly-automated pass.

The collision: a hard legal deadline that’s now producing daily-penalty rulings, an incumbent category that increases your lawsuit risk, and a technology that finally makes real code fixes cheap. Small merchants are stuck in the middle with no affordable, credible option.

Provenance:

• Signal 1 (demand): EAA enforceable 28 Jun 2025; France DGCCRF notices + Nov 2025 lawsuits; Carrefour June 2026 daily-penalty ruling; Germany BFSG warning letters within weeks — https://web-accessibility-checker.com/en/blog/eaa-fines/ , https://blog.usablenet.com/eaa-complaints-guide-france-germany-ireland-italy-spain — 2026-07
• Signal 2 (feasibility): LLM code-editing over Liquid/HTML themes + axe-core makes source-level WCAG remediation cheap; TestParty proves the code-remediation-not-overlay approach but sells developer/enterprise — https://testparty.ai/blog/testparty-vs-audioeye — 2026-07
• Signal 3 (economic): accessiBe $1M FTC fine + $1.2M settlement; overlays on 22.6% of 2025 ADA suits; agency audits $1.5–5K, remediation $10–50K = proven WTP with a hated supply side — https://ratedwithai.com/blog/accessibe-review-2026 , https://accessible.org/shopify-accessibility-audits-cost/ — 2026-07 Category: Regulatory arbitrage

3. The opportunity

The EAA created a compliance need for hundreds of thousands of small EU merchants overnight, and the market answered with the wrong product: overlay widgets (accessiBe, UserWay, AudioEye, and a dozen Shopify App Store clones) that inject a JavaScript layer, leave the underlying theme code non-compliant, and — per the lawsuit data — actively attract litigation while getting the vendor an FTC fine.

The credible alternative — source-code remediation — exists (TestParty) but is positioned developer-first / agency / enterprise: it assumes you have engineers and a budget. The small merchant on a $300/mo Shopify plan who just got a German warning letter has neither. Their only “affordable” options are the very overlays that make things worse, or a $1.5–5K agency audit followed by $10K+ of remediation they can’t pay for.

PixelRamp is the missing middle: self-serve, code-level, merchant-priced, EU-first. It connects to the store, fixes what’s automatable in the theme’s own code, honestly flags what needs a human, and produces the exact EAA accessibility statement the law demands — with the correct “partially compliant” language, not a fake “100% compliant” badge. The honesty is the product: the FTC just proved that overclaiming is the fastest way to get sued and fined. We win by being the one tool that doesn’t lie.

4. Target market

• Primary customer: Owner-operators and one-person marketing/dev teams of small EU-facing webshops on Shopify or WooCommerce — roughly €200K–€5M GMV, no in-house engineer, selling physical goods to EU consumers. Also EU-facing UK/US stores (the EAA binds anyone placing products on the EU market).
• Why they buy (in their words): “I got a warning letter from a German law firm about accessibility and I have no idea what they want.” “Every quote I got was $2K just to tell me what’s wrong, then thousands more to fix it.” “I installed an accessibility widget and just found out it’s actually a lawsuit magnet.” They are scared, non-technical, and on a clock with daily penalties attached.
• Rough TAM reasoning: Shopify has ~5M+ live stores; a large share touch the EU. Only microenterprises (<10 staff AND <€2M turnover) get partial exemption, so most small-but-real shops are in scope. Even 100K addressable EU-facing small merchants at €40/mo = €48M ARR ceiling — far past our $5M target. We only need a sliver.
• Why now for them: The deadline passed (Jun 2025), enforcement notices and lawsuits are landing (late 2025–2026), and the Carrefour daily-penalty precedent turned “I’ll get to it” into “I could be fined per day.” The warning-letter wave is the buying trigger.

5. Product sketch (MVP)

• One-click store connect (Shopify OAuth first; WooCommerce plugin second) — scans the live theme against WCAG 2.1 AA using axe-core plus targeted manual-rule heuristics.
• Prioritized issue report in plain language: “Your Add-to-Cart button can’t be reached by keyboard” — not “4.1.2 Name, Role, Value,” with the legal-risk framing merchants actually respond to.
• Code-level auto-fix for the automatable classes: missing alt text (AI-generated, product-aware), form labels, ARIA roles, heading structure, color-contrast tokens, focus order — applied to the theme’s own Liquid/CSS, delivered as a reviewable change set (duplicate theme → preview → publish). No overlay, no injected widget.
• Honest residual list: the WCAG items automation can’t safely fix (complex custom components, media captions, reading-order edge cases) flagged clearly, with an optional paid human-review add-on.
• EAA accessibility statement generator: produces the legally-required statement with the correct compliance level (fully / partially / non-compliant), the itemized non-compliance and disproportionate-burden sections, and a working feedback mechanism.
• Monitoring: re-scans after theme edits and app installs, alerts on regressions, keeps a timestamped remediation log (the “good-faith effort” evidence that settles demand letters cheaply).

6. AI angle — what’s load-bearing

Remove the AI and this is just axe-core (a free scanner) plus a form. The AI is doing two things no rules engine can:

1. Writing correct fixes into unfamiliar theme code. Every Shopify theme is different Liquid/HTML. Deterministically patching alt attributes is easy; adding correct ARIA roles, fixing focus order, and restructuring headings without breaking the layout requires reading the template’s intent. That’s a code-editing model’s job.
2. Generating context-accurate alt text and the statement prose. Product-aware alt text at catalog scale, and the nuanced “partially compliant / disproportionate burden” statement language that has to be defensible in front of a regulator — both are generation tasks, not lookups.

The rules engine finds problems; the AI fixes them and explains them. That’s the whole difference between us and a $10 scanner.

7. Localization angle (if any)

EU-first is the entire wedge, not a bolt-on. The statement generator must emit per-jurisdiction variants (Germany BFSG, France RGAA-flavored, Ireland’s criminal-penalty regime, Italy, Spain) with the right enforcement body, feedback-contact rules, and language. Multilingual statement output (DE/FR/IT/ES/NL) is table stakes. This is precisely what US-born overlay incumbents under-serve — they treat the EAA as an afterthought to the ADA. A tool that speaks each Member State’s specific requirement beats a generic global badge. Pricing in EUR with a €39–€99/mo band fits merchant wallets where a $199/mo AudioEye seat doesn’t.

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

• Pricing: €39/mo (single store, auto-fixes + statement + monitoring) → €99/mo (multi-store / larger catalog / priority re-scans). One-time €149 “remediation sprint” for merchants who want the fix-and-statement once without a subscription (converts a chunk to monitoring later). Human-review add-on billed at €299 per pass (thin-margin partner network of a11y auditors).
• ACV: Blended ~€600/yr (mix of €39 and €99 subs, plus one-time and add-on revenue).
• Math to $1M ARR: ~1,700 paying subscribers at ~€49/mo blended × 12 ≈ €1M. Very reachable against a six-figure addressable base with an active buying trigger.
• Math to $5M ARR: ~8,000–9,000 subscribers, or ~5,000 subs + a meaningful agency/reseller channel (a11y freelancers and Shopify Partners white-labeling the fix). Requires WooCommerce live and a second platform (BigCommerce/Wix) to widen the funnel.
• Expansion path: more stores per account, catalog-size tiers, recurring monitoring/re-scan value after each theme change, human-review marketplace take rate, and an annual “compliance renewal” as WCAG 2.2/3.0 and EAA guidance evolve.

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

• Ride the warning-letter wave. German BFSG and French notices are being sent by identifiable law/competition firms. Monitor accessibility-lawsuit trackers and merchant forums for freshly-hit stores; the merchant who just got a letter converts in days, not months.
• Shopify App Store, positioned as the anti-overlay. List with the explicit hook: “The accessibility app that fixes your code instead of hiding behind a widget that gets you sued.” The category is full of overlays with the exact liability problem we solve — differentiation is free.
• Free public scanner as top-of-funnel. A no-signup “paste your EU store URL → see your WCAG failures + your fine exposure by country” page. Ranks for “EAA Shopify compliance,” captures the panicked searcher, converts the scan into a paid fix. (accessibilitychecker.org / web-accessibility-checker already prove the traffic exists — we convert it to remediation.)
• Partner with EU Shopify agencies and a11y freelancers who get remediation requests they don’t want to hand-do: white-label the fix, revenue-share. They bring the merchant; we do the work.
• Vernacular content in DE/FR: the specific fear (“Was will diese Abmahnung?” / “que veut cette mise en demeure?”) is under-served in local languages by US incumbents.

10. Build complexity — justification

Medium. Off-the-shelf: Shopify OAuth + theme API, axe-core scanning, a code-editing LLM, statement templating. Custom work is the safe auto-fix engine — patching real theme code without breaking layouts, with a preview/rollback safety net so we never publish a broken storefront (the single biggest technical risk and where the engineering discipline goes). Multi-jurisdiction statement logic is content-heavy but not hard. A technical founder plus one engineer ships a Shopify-only v1 in ~10–14 weeks; WooCommerce and human-review marketplace follow.

11. Gating checklist

Gate	Pass?	Note
Legal in target market	✅	We help comply; must avoid overclaiming (the accessiBe trap) — honesty is baked into positioning.
Ethical — no harm / dark patterns	✅	The entire pitch is refusing the dark pattern (fake compliance badges) the incumbents sell.
Market exists (evidence above)	✅	Live enforcement, daily-penalty ruling, proven $1.5–5K WTP, saturated (wrong-shaped) competitor set.
1–5 person team can build this	✅	Technical founder + 1 eng for v1.
Launchable with <$50K / ₹40L	✅	Shopify app + inference costs; no upfront capital beyond runway.

12. Feasibility score

Axis	Weight	Score	Notes
Problem intensity	20	16/20	Legal deadline with daily penalties + warning letters = hair-on-fire for the merchant who’s been hit; latent for those who haven’t yet.
Demand evidence	15	13/15	Live enforcement, FTC fine, lawsuit trackers, proven agency pricing, saturated app category. Multiple independent hard signals.
Build feasibility	15	11/15	Scanning is easy; safe code-editing without breaking themes is the real work. Doable in ~3 months but needs discipline.
Distribution clarity	15	12/15	Free-scanner funnel + App Store + warning-letter targeting + agency channel are concrete; conversion of scan→paid still to prove.
Revenue mechanics	15	11/15	Merchant-priced subs benchmarked below incumbents; ACV modest, so needs volume, but the base is large.
Time to first revenue	10	8/10	Self-serve app + scared buyer with a deadline = fast trial-to-paid; App Store review adds a couple weeks.
Defensibility	10	6/10	TestParty (enterprise) and overlay incumbents could move down-market. Moat = EU-jurisdiction depth, merchant trust as the honest option, and remediation-log lock-in. Not a fortress.
Total	100	74/100

13. Qualitative modifiers

Founder-fit tags

technical-heavy · domain-expertise-required — you need someone who can safely edit theme code and someone who genuinely knows WCAG/EAA (or an a11y advisor), because a wrong statement is a legal liability, not a bug.

Key assumptions to validate (3–5)

1. Assumption: Auto-fixes can safely resolve enough of the common WCAG failures (alt text, labels, contrast, ARIA, focus) to be worth paying for, without breaking storefronts. How to test: Run the fix engine against 25 real Shopify themes, measure % of axe-core failures cleared and zero layout regressions on manual QA.
2. Assumption: Small merchants will pay €39–€99/mo before they personally receive a warning letter (i.e. fear-of-fine is enough). How to test: Free scanner → paywall on the fix; measure scan-to-paid conversion for non-warned vs warned segments.
3. Assumption: The “anti-overlay, honest partial-compliance” positioning converts better than “instant 100% compliant.” How to test: A/B the App Store listing and landing headline; compare install and paid conversion.
4. Assumption: Per-jurisdiction statements are seen as materially more valuable than a generic one. How to test: Interview 15 DE/FR merchants; would they pay more for a BFSG/RGAA-correct statement?

Risk flags

1. Platform dependency: Heavy reliance on Shopify’s OAuth/theme API and App Store distribution and policies. WooCommerce diversifies but adds a self-hosted support burden.
2. Liability / overclaim risk: If our statement or fix is wrong and a merchant is fined, blowback hits us. Must ship conservative claims, clear disclaimers, and a human-review escalation — the opposite of accessiBe’s mistake, deliberately.
3. Incumbent downmarket move: TestParty (code remediation, enterprise) or a well-funded overlay pivoting to real fixes could compress the window. Speed to own EU-SMB mindshare matters.
4. Market timing / enforcement pace: If EU regulators enforce softly against tiny merchants, urgency (and conversion) softens for the not-yet-warned majority.

14. Structured verdict

Score:                  74/100
Verdict:                GO
Confidence:             Medium
Best-fit builder:       Technical founder who can safely edit theme code, paired with a WCAG/EAA-literate advisor
Time to revenue:        8–12 weeks (Shopify app + free-scanner funnel)
Capital to launch:      ₹4–8 lakh / $5–10K (inference + Shopify dev + a11y advisor)
Top 3 assumptions to validate first:
  1. Auto-fix clears enough WCAG failures on real themes with zero layout breakage — test on 25 Shopify themes
  2. Merchants pay before being warned — measure scan-to-paid conversion, warned vs not-warned
  3. Anti-overlay honest positioning out-converts "100% compliant" — A/B the listing
Kill criteria:
  - Abandon if auto-fix clears <40% of axe-detected failures without human intervention, or causes layout regressions we can't reliably prevent
  - Abandon if scan-to-paid conversion is <2% after 2,000 free scans
  - Abandon if a well-funded incumbent ships credible self-serve EU-SMB code remediation at merchant price before our v1

15. Next step — 1-week validation sprint

• Day 1–2: Build the free scanner (axe-core + fine-exposure-by-country readout). Scrape 300 EU-facing Shopify stores; scan them; quantify how bad the average small store actually is (validates the “everyone’s non-compliant” premise).
• Day 3–4: Hand-run the LLM fix loop on 10 of the worst themes in a duplicate theme. Measure: % of failures cleared, layout regressions, minutes per store. This is the make-or-break — if the fixes aren’t safe, the product doesn’t exist.
• Day 5: Post the scanner in 3 EU Shopify/WooCommerce merchant communities and 2 DE/FR groups with the anti-overlay hook. Go/no-go: ≥50 scans run and ≥5 merchants ask “can you just fix it for me / what would that cost” within 48 hours. That’s a falsifiable demand signal, not a vibe.