In Ohio, your ADA website risk is shaped by one distinctive fact: the Sixth Circuit follows the “nexus” approach, generally requiring a connection between your website and a physical place of public accommodation. That gives Ohio defendants — especially online-only ones — leverage you won’t find in every state. It does not make you immune.

Ohio’s distinct angle: the Sixth Circuit nexus rule

Most ADA website lawsuits ride on a single legal question: is a website itself a “place of public accommodation” under Title III of the Americans with Disabilities Act? The federal appeals courts disagree, and Ohio sits in a part of that map that favors defendants.

Ohio is in the Sixth Circuit, which — alongside the Third and Ninth Circuits — applies the nexus theory: a website is covered when there is a sufficient connection between it and a physical location, such as a store, clinic, or restaurant. By contrast, the First and Seventh Circuits have held that a website can be a public accommodation on its own, with no physical place required. The Second Circuit is split. This circuit divide is summarized by the American Bar Association and detailed in the Federalist Society’s review of website Title III litigation.

The leading Sixth Circuit decision is Brintley v. Aeroquip Credit Union (2019), where a blind plaintiff sued two credit unions over inaccessible websites. The court dismissed the case on standing grounds — the plaintiff was not eligible to join the credit unions and showed no intent to become eligible, so she had no concrete injury. Brintley didn’t resolve every nexus question, but it set a defendant-friendly tone in this circuit: standing and a real connection to a covered place both matter.

This is general information, not legal advice. Circuit law evolves, district courts apply it unevenly, and your facts control. Consult a qualified Ohio attorney before relying on any defense.

What the nexus rule means for an Ohio business

Read this carefully, because the nexus rule cuts two ways:

  • If you’re online-only in Ohio — a SaaS product, a digital service, an e-commerce brand with no storefront — the Sixth Circuit gives you a genuine argument that Title III may not reach your site at all. That is a meaningfully stronger position than a defendant in the First Circuit or a California business facing both the Ninth Circuit and the Unruh Act.
  • If you have a physical location — and most Ohio businesses do — your website is tied to that place. The nexus exists. The defense that helps online-only companies does little for a Columbus restaurant, a Cincinnati dental practice, or a Cleveland retailer whose site lets customers find hours, book appointments, or shop the same goods sold in store.

So the practical takeaway for the typical Ohio business is sobering: the circuit’s rule narrows the field of who can be sued, but it doesn’t shrink the target on a normal store-plus-website operation.

Ohio’s own law: R.C. 4112 and a private right to sue

Federal Title III isn’t the only exposure. Ohio’s civil rights statute, R.C. 4112.02(G), makes it unlawful for any place of public accommodation to deny a person with a disability the full enjoyment of its accommodations, advantages, facilities, or privileges. Ohio law allows a private civil action for damages, injunctive relief, and other appropriate relief, and prevailing plaintiffs can recover attorney’s fees.

Ohio also carves out special damages for “accessibility law” claims under R.C. 4112.16, defined to include R.C. 4112.02(G) as applied to people with disabilities. The state statute mirrors the ADA’s public-accommodation concept rather than imposing a separate WCAG number on private companies — but it means a plaintiff has both a federal and a state path, and Ohio’s fee-shifting makes even modest cases worth a lawyer’s time. (Again: general information, not legal advice.)

The IT-09 deadline: WCAG 2.1 AA is now Ohio’s baseline

Here’s the development reshaping the standard everyone is measured against. Ohio updated Administrative Policy IT-09, Digital Accessibility, in January 2025. It requires state agencies, boards, and commissions to make their web content and mobile applications conform to WCAG 2.1 Level AA, in line with ADA Title II and the DOJ’s web rule, as published by the Ohio Department of Administrative Services.

Key points of IT-09:

IT-09 doesn’t directly regulate a private Ohio business. But it does something quieter and more important: it cements WCAG 2.1 AA as the recognized benchmark across Ohio’s public and procurement ecosystem. When a plaintiff’s expert, a judge, or your own enterprise customer asks “what should this site meet?”, the answer in Ohio is now unambiguous. Learn what that target involves in our WCAG 2.1 AA explainer.

Who’s getting sued — and where Ohio fits

Nationally, website accessibility litigation rebounded in 2025: about 3,117 website cases were filed in federal court, roughly 36% of all ADA Title III filings, per Seyfarth’s ADA Title III tracker. The volume concentrates in plaintiff-friendly venues: the same Seyfarth count puts New York federal courts at 1,021 website filings — far ahead of Florida — with Illinois, Minnesota, and Pennsylvania rounding out the active districts. Ohio is not a top filing state, and the Sixth Circuit’s nexus and standing posture — set by Brintley — is a big reason serial filers route cases to New York and Florida courts instead.

That said, “fewer filings” is not “no filings.” Ohio businesses still receive these claims as federal suits in the Northern District of Ohio (Cleveland, Toledo, Akron) or Southern District of Ohio (Columbus, Cincinnati, Dayton), and as pre-suit demand letters that never hit a docket. The sectors drawing attention mirror the national pattern — e-commerce, restaurants, healthcare and clinics, and any site with online ordering or booking. The barriers cited are the usual ones: missing alt text, unlabeled forms, weak color contrast, and content you can’t reach by keyboard.

If a letter has already arrived, read what to do after an ADA demand letter and how serial plaintiffs operate before you respond.

How an Ohio business reduces exposure

In Ohio the nexus rule is a defense you raise after you’re sued, not a plan that keeps the suit away — and it does nothing for the store-plus-website operations that make up most of the state’s defendants. What actually lowers risk on both the federal Title III track and the R.C. 4112 state track is the same thing: a site that survives a real assistive-technology test. Three steps, each tied to how an Ohio claim actually plays out.

  1. Audit against WCAG 2.1 AA. Start with a manual accessibility audit that pairs automated scanning with keyboard and screen-reader testing (NVDA, JAWS, VoiceOver). Automated tools alone catch only a fraction of failures — and the ones they miss, like illogical reading order, unlabeled custom controls, and misleading ARIA, are precisely the barriers a plaintiff’s expert documents to manufacture the “concrete injury” that Brintley says an Ohio plaintiff must show. See what WCAG 2.1 AA requires.
  2. Remediate the real code. This is the step overlay widgets skip. Manual remediation rewrites the underlying HTML, ARIA, and JavaScript file by file — real alt text on informative images, color contrast that meets the 4.5:1 threshold, full keyboard navigation with a visible focus ring, and accessible forms with associated labels and error messaging. Because R.C. 4112.16 layers special damages and fee-shifting on top of any federal claim, the cheapest move in Ohio is to delete the barriers before a demand letter turns them into billable hours — not paint over them at runtime. Curbcut is deliberately anti-overlay; see why overlays don’t deliver compliance and overlay vs. manual remediation.
  3. Document the conformance. Keep the audit reports and remediation log, and publish an accessibility statement naming WCAG 2.1 AA and a way to report barriers. In Ohio that paper trail does double duty: it supports a good-faith, standing-style defense if a serial filer brings a Brintley-style claim, and it is the exact WCAG 2.1 AA certification a State-of-Ohio procurement officer demands under IT-09 if you ever sell into the public sector.

For a small Ohio business, that program costs less than one round of N.D. or S.D. Ohio litigation — and unlike a one-line widget, it actually closes the R.C. 4112.16 fee exposure. Find out where your site stands with a free accessibility scan, then let [EXPERT_NAME] and the [AGENCY_NAME] team remediate the issues by hand.

Authoritative resources for Ohio

The sources that actually govern an Ohio claim, in the order you’d reach for them:

The bottom line for Ohio

Ohio’s profile is specific, and the specifics cut in different directions. Brintley and the Sixth Circuit’s nexus-plus-standing posture give online-only Ohio operations a defense few other circuits offer — and they’re the reason serial filers route their volume to New York’s 1,021-case docket instead of the N.D. or S.D. Ohio. But the same posture does nothing for the Columbus restaurant or Cleveland clinic whose website is plainly tied to its premises, and R.C. 4112.16 hands those defendants a second front: state-court special damages and fee-shifting that a federal-only state never imposes. IT-09 then settles any argument about which standard applies — it’s WCAG 2.1 AA, the same target a procurement officer makes vendors certify. The one variable you control is whether the site actually meets it. That’s fixable, and it’s what Curbcut remediates by hand — file by file, not behind a widget.