// THE NUMBERS

The claims are up 27% from last year and they target small businesses

Start with the count. 3,117 website accessibility lawsuits were filed in federal court in 2025, up 27% from the year before. Add state-court cases and the total passes 5,000. Thousands more demand letters go out every year and never become public filings, which means the lawsuit counts are the visible part of a bigger iceberg.

These are not suits against Fortune 500 brands. Industry reports consistently find that most defendants are small and mid-size businesses, because they are the ones least likely to have fixed anything. And filing has gotten dramatically cheaper for the other side: roughly 40% of 2025’s federal filings were filed without an attorney, with plaintiffs increasingly using AI tools to find violations and draft complaints. A scanner finds the errors, a template turns them into a claim, and the plaintiff never has to visit your business. Your website is the storefront they inspect.

// CALIFORNIA

The quiet federal numbers here are misleading

California showed only a handful of federal filings in 2025, and it would be easy to read that as low risk. What actually happened is that the activity moved to state court. California’s Unruh Civil Rights Act carries minimum statutory damages of $4,000 per violation plus attorney’s fees, which makes state-court claims and pre-suit demand letters the preferred play here, especially against businesses with physical locations. If you run a California business with a public website, the exposure did not go away. It changed venue.

// THE PRICE TAG

What it actually costs

Public court records and legal industry reports put the typical resolution costs in these ranges:

How it resolves	Typical range	Typical outcome
Demand letter settlement	$1,000 – $25,000	~$5,000 average
Out-of-court settlement	$5,000 – $150,000	~$30,000 average
Defending a suit, even winning	$5,000 – $125,000	legal fees, no damages
Court judgment	$10,000 – $500,000	~$85,000 average

Two things make those numbers worse than they look. First, settling does not fix your website. You pay the settlement and then pay for the remediation anyway, sometimes on a court-supervised deadline instead of your own schedule. Second, businesses that settle without fixing the site are documented repeat targets: nearly half of 2025’s federal filings named companies that had been sued before.

// THE WIDGET TRAP

Why an accessibility widget won’t save you

The one-line “accessibility overlay” widgets that promise instant compliance have become a liability of their own. Sites running overlays keep getting sued, and in January 2025 the FTC reached a $1 million settlement with a prominent overlay provider for misleading businesses about what the widget could actually do for compliance. Real protection is fixing the code, not layering a script over it. That is the position I take with every client site I touch: no overlays, fixes at the source, changes that hold up if anyone ever looks.

// ACTING EARLY

What acting early looks like

Compare the table above to the cost of getting ahead of it:

• Free: an automated check of your homepage, which finds the same machine-detectable errors a plaintiff’s scanner finds. Instant results on screen, full findings by email.
• $500 flat: a full-site Website Accessibility Review. Every page scanned, human review, a plain-English risk summary, and a prioritized fix list your developer can act on. If you move ahead with fixes through me, the $500 is credited toward the remediation work.
• From $250/month: ongoing monitoring and remediation, so the site stays clean instead of drifting back into risk.

The entire ladder, end to end, costs less than the average demand-letter settlement. And unlike a settlement, it leaves you with a website that works for everyone, which was the point of the law in the first place.

Run the free check to see where you stand in about 30 seconds, or book 15 minutes and I’ll walk you through it.

Sources: Seyfarth Shaw’s ADA Title III litigation tracking (2025 federal filing counts, state data, pro se share); the Accessibility.build lawsuit tracker (settlement and defense cost ranges, FTC overlay settlement); UsableNet annual reports (combined federal and state totals). California Unruh Act statutory damages: Cal. Civ. Code § 52. This article is general information, not legal advice, and does not guarantee prevention of claims. Consult qualified legal counsel regarding ADA, website accessibility, and California disability-access obligations.

// THE BURIED STAT

What the headline misses

IBM surveyed 2,000 CEOs at companies pulling roughly $5.8B in revenue. Three quarters of them are hiring a Chief AI Officer this year. Two years ago, only one in four had even thought about it. The headlines wrote themselves. Every consultant within a thousand miles of LinkedIn is updating their bio to include “AI strategist” by the end of the week.

That’s not the interesting number in the report.

The interesting number is buried two pages in. Inside those same companies, 86% of employees have the skills to use AI today, or could pick them up with a little training. Only 25% actually use it in their daily work. Sixty-one points of gap between “could” and “do.” That gap isn’t a skills problem. It’s an operations problem. Nobody is walking around the building connecting the people who can use AI to the workflows that actually need it.

If you run a small organization in California, here’s what I want you to take from that report: the gap is bigger at your size, not smaller. You don’t have a $250,000 Chief AI Officer line item in your budget. You probably don’t have a director of anything. What you have is a handful of people doing the work, a handful of recurring workflows that eat hours every week, and a vague pressure to “do something with AI” before the board asks again.

Hiring a CAIO is not the answer. The job doesn’t fit your shape. But the work of a CAIO absolutely does, and it’s the work nobody on your team is going to spontaneously volunteer for.

// THE WORK

What that work actually looks like

Walk the floor for a week. Find the three workflows that bleed the most hours. Pick the one with the cleanest inputs and outputs. Build a working automation in two weeks, not six months. Hand it to the person whose job it touches and watch what they do with it. If it sticks, train one internal champion to run it. If it doesn’t, kill it without ceremony and pick the next one.

That’s the job. It’s unglamorous, it’s iterative, and it’s the only thing that closes the 61-point gap. The strategy decks come later, after the team has watched something actually work.

Most small orgs don’t do this because the person who would do it doesn’t exist on the org chart. Your operations lead is buried in operations. Your marketing lead is buried in marketing. The CEO doesn’t have the technical fluency, and the IT vendor doesn’t have the operational context. So the workflows stay manual, the pressure stays, and AI stays a slide in a board deck.

// THE LEVERAGE

What I do here

I spent the last ten years building and running brand systems for small California organizations. The last two years I’ve been quietly running a different stack underneath all of it: n8n, Claude, and a tight loop of automations that handle the unglamorous parts of every retainer I ship. That’s what makes hosting and maintenance work at a small-org price point. Me at the front, Claude in the back, both of us pointed at the same workflow.

I do that work for myself every day. I also do it for clients. A pizza chain with hundreds of locations runs an inbound-feedback pipeline I built that triages thousands of emails a day with a human in the loop. An association runs a member-intelligence dashboard that flags renewal risk before it shows up in the renewal report. A real-estate brokerage runs an inbound-lead engine that captures voicemails, faxes, and form fills into a single queue.

None of those clients hired a Chief AI Officer. They hired the work of one, embedded into a monthly relationship, with a defined cadence and a working session they can put on the calendar.

// THE OFFER

AI Operator-in-Residence

This is what I’m calling that offer now. It’s a monthly add-on that layers on top of an existing maintenance retainer. You get a named operator (me) plus monitoring of the automations already running in your stack, a recurring working session with your team and your designated AI champion, and new automations shipped on a defined cadence. Standard is $500/month. Plus is $1,250/month and includes a build credit for up to one new automation per quarter. Enterprise is custom for regulated industries or multi-team scope.

The shape is deliberate. It’s not a 90-day sprint, because the work doesn’t end at day 90. It’s not pure advisory, because slide decks don’t close the 61-point gap. It’s a recurring operator presence, priced so a 20-person organization can actually afford it, anchored to the same maintenance-retainer relationship that keeps your site alive.

Full details, included scope per tier, and what’s not included on the AI Operator-in-Residence page.

If this sounds like the shape of the problem at your organization, the contact page is one click. The bigger point stands either way: the CAIO headline is real, but for an org your size, the real answer is an operator, not a title.

// THE TABLE ERA (2001-2005)

The Table Era

2001. HTML hand-coded in a Notepad window. Classic ASP for anything dynamic. MySQL when data needs to persist. IE6 ships and refuses to die for the next decade. Tables nested inside tables for layout. XHTML 1.0 ratified.

2002. Mozilla 1.0. Movable Type blogs. Macromedia Flash is how you make a site feel “interactive.” ASP still dominant for server-side.

2003. CSS Zen Garden launches and proves you can build the same page two hundred ways with stylesheets alone. WordPress 0.7 ships and enters the toolkit as a blog install. Safari 1.0.

2004. Firefox 1.0. Gmail launches and makes Ajax mainstream. “Web 2.0” gets coined. PHP overtakes ASP for client work. LAMP becomes the default stack.

2005. YouTube. Google Maps drags the rest of the web into Ajax. Rails 1.0 starts the convention-over-configuration era. WordPress becomes the go-to CMS for content sites. Custom PHP and MySQL for anything bespoke.

// THE AJAX-AND-JQUERY ERA (2006-2010)

The Ajax-and-jQuery Era

2006. jQuery 1.0. Twitter. Facebook opens to the public. The DOM gets ergonomic for the first time. WordPress plus jQuery becomes the working setup.

2007. iPhone. WebKit goes mobile. Everything changes, but most sites don’t notice yet. WordPress is now the default for client builds. Classic ASP retires.

2008. Chrome 1.0 ships with V8 and the JavaScript engine arms race begins. Android launches.

2009. Node.js. HTML5 video. Server-side JavaScript stops being a joke.

2010. Ethan Marcotte publishes “Responsive Web Design” in A List Apart. iPad launches. CSS3 transitions and animations ship. Client themes get rebuilt responsive from the ground up.

// THE FRAMEWORK ERA (2011-2015)

The Framework Era

2011. Bootstrap 1.0. Sass goes mainstream. Every site starts looking the same on purpose. WordPress themes pick up a Bootstrap underlay.

2012. Retina displays. Flexbox enters the spec. Skeuomorphism peaks before falling off a cliff.

2013. iOS 7 ships flat design. React released. AngularJS rising. Component-driven UI becomes the conversation. WordPress page builders (Divi, Visual Composer) take off and enter the toolkit for faster client turnarounds.

2014. Google Material Design. ES6 specced. Web Components edge in.

2015. Vue.js. CSS Grid enters the spec. HTTP/2. The frameworks split into camps. WordPress powers roughly 25% of the web.

// THE JAMSTACK ERA (2016-2020)

The Jamstack Era

2016. “Jamstack” gets coined. Netlify rising. React wins. PWAs get pitched as “the future of the mobile web.” Jamstack gets tested on a few projects; WordPress wins out for client work, because content editors don’t want a git workflow.

2017. Headless CMS goes mainstream (Contentful, Sanity, Strapi). CSS Grid ships in browsers. Service workers everywhere.

2018. GraphQL adoption climbs. Gatsby, Hugo, Eleventy split the SSG market. Webpack pain peaks. WordPress Gutenberg block editor ships.

2019. Headless WordPress. Next.js gains share. The industry collectively names “JavaScript fatigue.”

2020. Pandemic forces every business online. Tailwind CSS hits mainstream. Vercel and Netlify own deploy. The client stack consolidates around WordPress on WP Engine, custom themes, and utility CSS.

// THE AI ERA (2021-2026)

The AI Era

2021. Web3 hype peaks and breaks. Astro launches. View Transitions API drafts.

2022. ChatGPT ships November 30 and the conversation pivots overnight. Tailwind owns CSS. LLMs enter dev workflows. n8n joins the stack for client automations.

2023. Copilot mainstream. Midjourney and DALL-E enter design briefs. Bun. React Server Components.

2024. Claude Code. Cursor. AI agents start writing production markup. CSS container queries finally ship. Claude joins the stack as a daily collaborator.

2025. Agent-driven workflows go from demo to production. n8n plus LLMs become a standard operations layer. Lovable and v0 let non-developers ship full apps.

2026. Where we are. WordPress is still the CMS under most client work. The orchestration around it (n8n, Claude, automation pipelines) is what’s new.

// THE PATTERN

What compounds

A new paradigm every 2.5 years on average. None of them killed the previous one. They stacked. The stack proves it: HTML from 2001 is still in everything. WordPress from 2003 still runs most of what ships. ASP got retired. PHP, MySQL, WordPress, jQuery, Bootstrap all live on, just covered over by newer layers.

The thing that compounds across all of it is operating discipline. Year 10 of running Sonnenberg Design is built on year 25 of building sites. Tools change every couple years. The studio compounds.