Georgia is one of the few states where the core legal question — whether the ADA even covers websites — has no settled answer. The federal Eleventh Circuit, which governs Georgia, vacated its only major ruling on the issue, and a new state law, HB 1470, now cuts against abusive filings. That makes Georgia’s risk picture genuinely distinct.

Why Georgia is legally unsettled: the Winn-Dixie vacatur

Most state guides can point to circuit precedent. Georgia can’t — and that’s the whole story here.

Georgia falls under the U.S. Court of Appeals for the Eleventh Circuit (which also covers Florida and Alabama). In Gil v. Winn-Dixie Stores, a legally blind plaintiff sued the grocery chain because its website didn’t work with screen readers. A Florida district court ruled against Winn-Dixie in 2017. On April 7, 2021, a split Eleventh Circuit panel reversed, holding that “public accommodations are limited to actual, physical places” and that websites are not themselves public accommodations — and pointedly rejecting the “nexus” theory other circuits use to tie websites to physical stores (Holland & Knight analysis).

That pro-business ruling did not last. On December 28, 2021, the Eleventh Circuit vacated its own opinion as moot, because the underlying injunction had already expired in 2020, leaving no live dispute (Perkins Coie). A vacated opinion carries no precedential weight. The practical result: Georgia businesses cannot rely on Winn-Dixie as a shield, and plaintiffs cannot cite it either. Georgia district courts are left to decide coverage case by case — a vacuum that invites litigation rather than ending it.

This page is general information, not legal advice. Georgia is a moving target right now — the Eleventh Circuit left no binding answer after Winn-Dixie, and HB 1470 only takes effect July 1, 2026 — so the right call for your situation depends on timing and facts. Consult a qualified Georgia attorney before acting.

Georgia’s state law: no Unruh Act, but a new HB 1470 twist

Unlike California, Georgia has no state disability-access statute that adds damages for website inaccessibility. There is no Georgia equivalent of California’s Unruh Civil Rights Act. So a private plaintiff in Georgia generally proceeds under federal ADA Title III, where the only remedy is injunctive relief plus attorney’s fees — the plaintiff personally recovers no damages (Congressional Research Service on ADA tester suits). Attorney’s fees are what drive the volume.

Then Georgia did something most states haven’t: it pushed back legislatively. HB 1470 — passed the House 144–22 and the Senate 50–0, signed as Act 458, and effective July 1, 2026 (Georgia General Assembly bill page; full text and vote history on LegiScan) — amends Georgia’s abusive-litigation statute (O.C.G.A. Title 51, Chapter 7) to create a dedicated cause of action for abusive website-access litigation. When a defendant prevails — on the merits, by involuntary dismissal, or on a standing challenge — the statute lets the defendant recover actual damages or $10,000 in statutory damages, whichever is greater, plus reasonable defense attorney’s fees, and triple damages if the plaintiff was given written notice of the law’s provisions and still refused to voluntarily dismiss; it also builds in a rebuttable presumption that a claim is not abusive when the business takes corrective action after notice, and authorizes the Georgia Attorney General to intervene (Georgia General Assembly bill summary; analysis at Understanding the ADA). That fee-shifting flips the usual economics of serial filings — but it does nothing to remove your underlying federal duty to be accessible. A genuinely inaccessible site can still lose under federal law.

Who is actually getting sued in Georgia

Georgia is not New York-level volume, but it is far from quiet — and it splits into two distinct tracks.

Private businesses. Nationally, federal website-accessibility filings climbed to roughly 3,117 in 2025, up about 27% over 2024, with New York, Florida, and Illinois leading the count (Seyfarth’s ADA Title III blog). Georgia is not in that top tier, but it is a real filing state: Seyfarth counted 107 federal ADA Title III suits filed in Georgia in 2024, enough to land it in the national top ten (Seyfarth 2024 ADA Title III filings). Because Georgia sits in the Eleventh Circuit alongside Florida, the same high-volume plaintiff firms that drive Florida’s docket can — and do — name Georgia defendants. E-commerce, restaurants, and professional-service sites are the usual targets, hit on the same recurring barriers seen nationwide; a meaningful share never reaches a docket because it arrives first as a pre-suit demand letter.

Government entities. This is Georgia’s standout exposure. Public bodies face both private suits and DOJ enforcement under ADA Title II, and Georgia’s government sector is unusually large — 159 counties plus hundreds of cities and school districts, every one of them now on a fixed WCAG 2.1 AA deadline (below). The clearest documented example is Lumpkin County, whose ADA settlement agreement covering web and program access is archived on ADA.gov’s Project Civic Access. Reporting on the Georgia public sector also points to website-accessibility settlements by metro-Atlanta entities such as Fulton County and Atlanta Public Schools, and to a 2023–2024 cluster of demand letters and suits around Gainesville (adaquickscan Georgia government guide); those secondary accounts are useful as signals of where enforcement is concentrated, but the underlying figures are not confirmed in a primary court or DOJ record, so treat them as directional rather than precise.

The Title II deadlines Georgia governments can’t ignore

The DOJ’s Title II rule sets WCAG 2.1 Level AA as the required standard for state and local government web content and mobile apps. In its April 2026 interim final rule, the DOJ extended the deadlines: entities with 50,000 or more residents must comply by April 26, 2027, and smaller entities and special districts by April 26, 2028 (Federal Register). Georgia’s own ADA Coordinator’s Office confirms an April 26, 2027 deadline for state agencies. For Georgia cities, counties, and school districts, this is a hard line — not a litigation gamble.

How a Georgia business or agency reduces exposure

Whether you’re a private Georgia business worried about a demand letter or a public entity racing the Title II clock, the path is the same — and in Georgia it does double duty. Because the Eleventh Circuit gives you no coverage defense to hide behind after Winn-Dixie, genuine accessibility is your only durable shield against a federal claim. And because HB 1470 rewards businesses that take corrective action after notice, the same work also builds the documented good-faith record the state statute hinges on.

  1. Audit against WCAG 2.1 AA — the standard both fronts cite. Start with a manual accessibility audit. It’s not academic in Georgia: WCAG 2.1 AA is both the benchmark a Title III plaintiff measures you against and the literal legal requirement the DOJ’s Title II rule imposes on Georgia’s counties, cities, and school districts. Automated scanners catch only a fraction of real failures; a human testing with a keyboard and screen readers (NVDA, JAWS, VoiceOver) finds the unlabeled forms, broken focus order, and bad ARIA that plaintiffs actually cite. See what WCAG 2.1 AA requires.
  2. Remediate the real code. Manual remediation means fixing the HTML, CSS, and JavaScript itself — adding meaningful alt text, correcting color contrast, and making everything reachable by keyboard. In Georgia this is what actually triggers HB 1470’s rebuttable presumption: the statute protects businesses that correct after notice, not businesses that merely claim to have a fix.
  3. Document everything — Georgia makes it pay off. Publish an honest accessibility statement, keep your audit reports and remediation logs, and date-stamp the corrective work you did after any demand letter. Because HB 1470 (Act 458) sits inside O.C.G.A. Title 51, Chapter 7’s notice-and-cure structure, that timeline is the difference between a clean rebuttable presumption — and, if a warned plaintiff presses on anyway, a defense fee award and treble damages — versus having nothing to show. For a Title II public entity, the same records evidence conformance ahead of the April 2027/2028 deadlines.

A word on overlays: the one-line JavaScript widgets that promise instant compliance don’t fix your code, and overlay vendors have themselves been named in lawsuits. For a Georgia defendant they’re doubly useless — an overlay doesn’t make the site genuinely usable (so it doesn’t defeat the federal claim), and it isn’t the “corrective action” HB 1470 rewards (so it earns you no rebuttable presumption). They create a false sense of security while the barriers — and your exposure — remain. Read why overlays don’t work and the case for manual remediation over overlays.

Already received a Georgia demand letter?

In Georgia, a demand letter is not just a settlement demand — after July 1, 2026 it sits at the intersection of two opposing statutes, and how you respond changes your position under both.

The federal half still controls liability. A Georgia demand letter almost always threatens an ADA Title III claim, where the remedy is injunctive relief plus the plaintiff’s attorney’s fees. Because the Eleventh Circuit left no binding answer after the Winn-Dixie vacatur, a Georgia plaintiff can’t be brushed off on coverage alone — the safest read is that your site needs to actually work. So the moment a letter arrives, start a manual accessibility audit against WCAG 2.1 AA and begin fixing real code. Remediation is both the legal answer and your strongest negotiating leverage, because a demand built on barriers you’ve already removed loses most of its force.

The Georgia half changes the leverage — but only if you document it. HB 1470 (Act 458) folds website-access claims into Georgia’s existing abusive-litigation framework under O.C.G.A. Title 51, Chapter 7, which already runs on a written-notice-then-cure structure: a defendant who voluntarily dismisses (or, here, a business that takes corrective action after notice) gets protection that a stubborn plaintiff can’t ignore. Practically, that means three things for a Georgia demand letter:

  • Preserve the letter and date-stamp your response. Documented corrective action taken after the notice is exactly what triggers HB 1470’s rebuttable presumption that the claim is not abusive — and, conversely, what supports a defense fee award and treble damages if the plaintiff was warned and pressed on anyway.
  • Don’t quietly pay to make it disappear without fixing the site. A pure nuisance settlement leaves the barriers — and your federal exposure — in place, and forfeits the HB 1470 record you’d want if the same plaintiff or another returns.
  • Loop in Georgia counsel on the O.C.G.A. § 51-7-84 mechanics. The interplay between the federal claim and the state counter-claim (written notice, the 30-day voluntary-dismissal window, and Attorney General intervention authority) is specific to Georgia’s statute and worth a lawyer’s read (O.C.G.A. § 51-7-84).

Our guides on responding to an ADA demand letter and serial ADA plaintiffs walk through how these cases unfold; in Georgia, layer the HB 1470 documentation discipline on top.

The bottom line for Georgia

Georgia’s law is in flux: the Eleventh Circuit left no binding answer after Winn-Dixie, HB 1470 now arms defendants against abusive filings, and government entities face hard WCAG 2.1 AA deadlines. None of that changes the one thing within your control — whether your site is genuinely usable. Find out where you stand with a free accessibility scan, then let Curbcut audit and remediate by hand so your Georgia site is defensible, not just decorated.

For primary sources specific to Georgia: the text and status of HB 1470 (Act 458) at the Georgia General Assembly and the underlying abusive-litigation statute, O.C.G.A. § 51-7-84; the State of Georgia ADA Coordinator’s Office and its notice on the extended Title II deadlines for state and local entities; and the DOJ Title II web rule in the Federal Register. For the federal baseline that still governs liability, see ADA.gov and the W3C Web Accessibility Initiative for WCAG itself.