ADA Website Lawsuits in North Carolina: What Businesses Need to Know

North Carolina sits in the Fourth Circuit, where the courts have never decided whether a standalone website counts as a “place of public accommodation” under ADA Title III. That open question — combined with the state’s own WCAG 2.1 AA rules for government sites — makes NC a place where you can’t assume a friendly precedent will save you.

The North Carolina angle: an unsettled Fourth Circuit

Most state guides can point to a clear local rule. North Carolina can’t — and that’s exactly what businesses here need to understand.

The federal appellate court over North Carolina, the U.S. Court of Appeals for the Fourth Circuit, has issued no controlling decision on whether a website by itself is a “place of public accommodation” under Title III of the Americans with Disabilities Act. The Congressional Research Service, in its report The Americans with Disabilities Act (ADA) and Public Accommodations in Web Services (R48104), describes a long-running circuit split on exactly this question — with some circuits (such as the First and Seventh) reading “public accommodation” broadly enough to reach websites on their own, and others (such as the Ninth and the Eleventh) requiring a nexus between the site and a physical store. The Fourth Circuit sits in neither camp: it simply hasn’t answered the merits question, so North Carolina has no settled rule either way.

The closest the Fourth Circuit has come is Laufer v. Naranda Hotels, LLC, No. 20-2348 (4th Cir. 2023). There, the court held that a serial “tester” plaintiff had Article III standing to sue over an inaccessible hotel-reservation website based on an informational injury — see the Fourth Circuit’s opinion. But standing is only the courthouse door. The court did not resolve whether the website itself was a covered public accommodation. So North Carolina businesses face a double bind: a plaintiff can likely get in the door (standing is plausible here), while the merits question that might defeat the claim is genuinely up in the air. Uncertainty is not a defense — it’s a reason to be compliant rather than litigate.

This is general information, not legal advice. Circuit law on websites is unsettled; for your specific situation, talk to a qualified North Carolina attorney.

North Carolina’s own accessibility law and the WCAG 2.1 AA standard

North Carolina has a state-level disability statute and a separate digital standard for government — both worth knowing even though Title III drives most private-business cases.

The North Carolina Persons with Disabilities Protection Act (General Statutes Chapter 168A) prohibits, at § 168A-6, denying a person with a disability “the full and equal enjoyment of the goods, services, facilities, privileges, advantages, and accommodations of a place of public accommodation.” Its definition of “place of public accommodation” is framed around establishments that “[supply] goods or services on the premises” — physical-premises language that predates the web. The Act exists, and a plaintiff could invoke it, but its physical framing makes it a less common vehicle than federal Title III for pure website claims.

Where North Carolina is explicit is government digital accessibility. The State of North Carolina Digital Accessibility and Usability Standard, administered by the N.C. Department of Information Technology (NCDIT), requires state agency websites and digital services to conform to WCAG 2.1 Level AA — the same standard courts and the DOJ point to in private Title III matters. That alignment matters: whether you’re a county website or a Charlotte e-commerce shop, the technical target your developers should build to is identical.

The Title II deadlines: who they actually bind

A lot of NC organizations have heard “2026 deadline” and panicked. Here’s who it really covers — and the date that changed in 2026.

The DOJ’s 2024 Title II rule adopted WCAG 2.1 AA as the binding technical standard for state and local government web content and mobile apps. North Carolina’s larger cities and counties — those serving 50,000+ residents — were originally on the hook for April 24, 2026, with smaller governments and special districts due April 26, 2027.

Then, on April 20, 2026, the DOJ published an Interim Final Rule extending both dates by one year (citing staffing limits and the immaturity of automated remediation tools, including generative AI). The current deadlines, per the Federal Register notice:

Critically: these deadlines do not apply to private businesses. A Raleigh restaurant or a Wilmington Shopify store is governed by Title III, which carries no future compliance date — the duty to be accessible is already live. If you run a private NC business, the Title II calendar is a useful signal of where enforcement attention is heading, not a grace period you get to use.

Who is getting sued in North Carolina

North Carolina is not a top filing state — but “not New York” is not the same as “safe.”

National trackers from UsableNet recorded over 4,000 ADA digital-accessibility lawsuits in 2024, with New York, Florida, and California absorbing most of them. North Carolina’s own federal docket is genuinely quiet: Seyfarth Shaw’s count of website-accessibility filings in the three U.S. District Courts here — Eastern, Middle, and Western — found just two for all of 2024, among the lowest of any tracked state, versus 1,564 in New York (ADA Title III, 2024 filings). But that thin local number understates the real exposure for two reasons:

• Federal reach. ADA Title III is nationwide. A North Carolina website is accessible from a New York plaintiff’s screen reader, and many e-commerce and hospitality businesses get named in out-of-state federal courts where filing volume — and plaintiff-friendly experience — runs far higher than in the Eastern, Middle, or Western District of North Carolina.
• Demand letters first. A large share of activity never appears in filing counts because it arrives as a pre-suit demand letter from serial plaintiffs’ firms, often resolved quietly. NC businesses report receiving these even with no in-state lawsuit on record.

North Carolina also has an active disability-rights bar. In a high-profile state matter, the National Federation of the Blind and Disability Rights NC sued UNC Health Care, resulting in a $125,000 settlement and a 2023 injunction requiring accessible patient communications — see Disability Rights NC’s announcement. That case was about effective communication and accessible formats rather than a retail website, but it shows organized, well-resourced advocacy operates inside the state. Healthcare, ecommerce, and restaurants remain the most exposed verticals.

How a North Carolina business reduces its exposure

The Fourth Circuit’s silence is the whole problem: a NC defendant can’t move to dismiss on the theory that “a website isn’t a public accommodation” — no controlling case here adopts it — and a tester’s standing is already plausible after Laufer. So in North Carolina the realistic win is upstream: be accessible enough that a demand letter never gets written, because the cheap leverage a plaintiff’s firm relies on is a screen-reader pass that surfaces obvious failures. Aim your work at the same WCAG 2.1 Level AA target the NCDIT Digital Accessibility and Usability Standard already sets for state agencies — the technical bar is identical for a private Charlotte or Raleigh business.

1. Audit against the standard a NC plaintiff would test to. Start with a manual accessibility audit that pairs automated scanning with real keyboard-and-screen-reader testing against WCAG 2.1 AA — the exact criteria NCDIT names and the benchmark courts apply to private Title III sites. Automated scanners alone catch only a fraction of the failures that get cited: illogical reading order, unlabeled custom controls, and misleading ARIA aren’t visible to them, but they are the first things a tester hits.
2. Remediate the real code by hand — and don’t paper over it with a widget. Manual remediation fixes the underlying HTML, CSS, and JavaScript: real alt text, color contrast that clears the WCAG 1.4.3 minimum of 4.5:1 for normal-size text, full keyboard navigation, and properly labeled forms. Curbcut is explicitly anti-overlay, and that’s not dogma in a circuit with no merits defense to fall back on: UsableNet’s 2024 lawsuit report found accessibility widgets were cited as barriers in roughly a quarter of 2024 cases, so bolting one on can hand a plaintiff a fresh allegation instead of a defense. See why overlays don’t work.
3. Document the good-faith effort that matters most in an unsettled circuit. With no Fourth Circuit rule to lean on, dated proof of effort is the lever that turns a demand letter into a quick close rather than a filing in the Eastern, Middle, or Western District. Publish an accessibility statement naming your WCAG 2.1 AA target and a reporting contact, and keep dated audit and remediation records — and if the NC Persons with Disabilities Protection Act is ever invoked alongside Title III, that record answers both.
4. Monitor so a NC-reachable site doesn’t quietly regress. A new untagged PDF or third-party booking widget can reintroduce barriers overnight — and because your site is reachable from any state’s screen reader, a regression is exposure nationwide, not just in NC. Ongoing accessibility monitoring catches it before it becomes a demand letter.

For primary sources, see the W3C Web Accessibility Initiative for WCAG and ADA.gov for federal guidance.

The bottom line for North Carolina

North Carolina is a strange place to be a defendant: the Fourth Circuit hasn’t said your website is covered, but it hasn’t said it isn’t either — so the one argument that wins cases in some circuits (“no nexus, no claim”) isn’t available to you, while a tester’s standing already is after Laufer. With the merits door propped open and only two website filings reaching NC’s federal courts in 2024, the practical battleground here is the demand letter, not the courtroom — and the way to win it is to have nothing for a screen reader to flag. The state already holds its own agencies to WCAG 2.1 AA, and that is the line a private plaintiff will measure you against too. See exactly which of those criteria your site misses with a free accessibility scan, then have Curbcut fix the code by hand so there’s no open failure to anchor a claim on.