What Happens When You Type a URL and Press Enter
DNS lookups, TCP and TLS handshakes, HTTP requests, servers, and the browser's rendering pipeline. The whole journey of a web page, explained so it finally clicks.
Read →Accessibility lawsuits are rising fast and nearly 70% target e-commerce sites. Here's what WCAG compliance actually requires, why overlay widgets don't protect you, and a practical path to a defensible website.
A retail shop owner with eight employees got a demand letter last year: her website's color contrast was too low for screen reader users, and she had thirty days to fix it or face a federal ADA claim. Her site had been built by a freelancer years earlier and never touched since. This is not a rare story anymore — it's becoming the norm for how accessibility enforcement actually reaches small and mid-sized businesses.
If your website is still treating accessibility as a "nice to have," the data suggests that window is closing fast, and the businesses that get ahead of it now will avoid a costly scramble later.
More than 5,000 federal and state accessibility lawsuits were filed in the US in 2025, and federal filings are projected to surpass 6,000 in 2026. Nearly 70% of those lawsuits target e-commerce websites specifically — so if you sell anything online, this applies to you directly, not just to large companies.
There is no small-business exemption under Title III of the ADA. Research from litigation tracker UsableNet found that 64% of sued companies had annual revenue under $25 million. This isn't a Fortune 500 problem — it disproportionately hits growing small and mid-sized businesses that assumed they were too small to be a target.
Most of these cases don't start with a government audit. They start with a demand letter from a plaintiff's attorney, often settling for $5,000 to $25,000 plus a commitment to fix the site — before it ever reaches a courtroom.
The ADA itself doesn't spell out technical web standards, but courts and plaintiffs' attorneys have converged on one: the Web Content Accessibility Guidelines (WCAG), currently at version 2.2, with Level AA as the expected conformance level. WCAG 2.1 Level AA is what most settlement agreements and demand letters cite today, and it's a reasonable, achievable target for most businesses.
In plain terms, WCAG AA generally requires things like:
The WebAIM Million report — an annual scan of the top one million website home pages — found that 95.9% had at least one detectable WCAG failure, averaging 56 errors per page. Non-compliance is the norm right now, which paradoxically makes it more attractive litigation territory, not less: there's no shortage of targets.
The most common failures — low contrast, missing alt text, and unlabeled form fields — are also the fastest and cheapest to fix, which makes them a sensible starting point before commissioning a full audit.
A lot of business owners have been sold a one-line-of-code "fix": an accessibility overlay widget that promises instant compliance. This doesn't hold up. Overlay widgets don't change the underlying HTML that screen readers and assistive technology actually read, so the real barriers remain in place. In 2025 alone, 1,416 businesses that had installed an overlay were sued anyway.
The regulatory environment agrees. In early 2025, the Federal Trade Commission ordered the overlay vendor accessiBe to pay $1 million to settle charges that it deceptively claimed its AI-powered tool could make any website compliant when it couldn't reliably do so. If you've installed a widget and considered the problem solved, it's worth an honest second look.
You don't need an enterprise-level audit to make meaningful progress. A sensible sequence looks like:
If you're a government contractor or work with public entities, note that the DOJ pushed back Title II compliance deadlines by a year in 2026: larger public entities now have until April 2027, and smaller public entities until April 2028. That extension applies to state and local governments, not private businesses — a private commercial website is still exposed to Title III litigation risk today, deadline extension or not.
Courts have consistently treated commercial websites as "places of public accommodation" under Title III, and that interpretation has only solidified over time, not weakened. Combined with rising public awareness of digital inclusion and an active plaintiff's bar that has turned accessibility litigation into a repeatable business model, this pressure is not going away. If anything, as WCAG standards continue to evolve (2.2 already added new criteria beyond 2.1), the bar will keep rising, not falling.
The upside worth remembering: the same work that reduces your legal exposure also makes your site genuinely better for every visitor — faster to scan, easier to navigate, and more usable on mobile and for anyone dealing with a slow connection, a cracked screen, or a temporary injury. Accessibility work is rarely wasted effort.
DNS lookups, TCP and TLS handshakes, HTTP requests, servers, and the browser's rendering pipeline. The whole journey of a web page, explained so it finally clicks.
Read →There are dozens of HTTP status codes, but about fifteen cover nearly everything. What each one means, when to return it, and the mix-ups (401 vs 403, 301 vs 302) that confuse everyone.
Read →A, AAAA, CNAME, MX, TXT and NS records in plain English, why DNS changes seem slow, and the troubleshooting commands that tell you what is really going on.
Read →