In Virginia, your ADA website risk turns on an unsettled question: the Fourth Circuit has issued no controlling rule on whether a standalone website is a “place of public accommodation.” That ambiguity cuts both ways — there’s no easy dismissal, but a Western District judge already read the ADA broadly in Mejico. The settled piece is the state accessibility standard.

Virginia’s distinct angle: an open Fourth Circuit

Almost every ADA website case turns on one legal question: is a website itself a “place of public accommodation” under Title III of the Americans with Disabilities Act? The federal appeals courts have split — some require a “nexus” to a physical store, a couple treat a website as a public accommodation on its own. Virginia sits in the most unsettled position: the Fourth Circuit, whose precedent binds Virginia’s federal courts, has issued no controlling decision either way.

That blank space matters. Practitioner surveys of the circuit split place the Fourth among the circuits with no binding appellate rule on standalone websites (American Bar Association overview; Federalist Society review of website Title III litigation). Unlike a Seventh Circuit defendant in Illinois, who faces precedent that a website is covered in its own “electronic space,” a Virginia defendant operates in a vacuum — no appellate holding to lean on, none to fear — so outcomes turn on which judge draws the case.

This page is general information, not legal advice. Fourth Circuit law on websites is genuinely unsettled and district courts apply it inconsistently — consult a qualified Virginia attorney about your situation.

What a Virginia court did when the question landed: Mejico

The most important Virginia data point is Mejico v. Alba Web Designs, LLC, 515 F. Supp. 3d 424 (W.D. Va. 2021). A blind plaintiff sued over an inaccessible commercial website; the defendant moved to dismiss on the classic nexus theory — no physical store, no “place,” no claim. The Western District of Virginia rejected that, holding that places of public accommodation under the ADA “are not limited to physical, brick-and-mortar establishments” and instead include commercial websites that offer goods and services to the public, because excluding online retailers “would contravene the broad remedial purpose of the ADA” (FindLaw — Mejico v. Alba Web Designs). Both motions were denied.

Keep Mejico in perspective: it is a single district-court decision, not binding Fourth Circuit precedent, and an Eastern District judge could reason differently. But you cannot count on a “websites aren’t places” dismissal in Virginia — a judge here has already refused one.

Where Virginia’s standard is actually settled: the IT Access Act

If federal coverage is uncertain in Virginia, the standard a site should meet is not. The Virginia Information Technology Access Act (Va. Code Title 2.2, Chapter 35) requires state agencies and public higher education to make their technology accessible under the Rehabilitation Act (Code of Virginia, Title 2.2, Ch. 35), and the operational rule — the Virginia Information Technologies Agency (VITA) ITRM Standard GOV103-00 — is built on WCAG 2.0 Level AA (Section508.gov state-law summary). That binds government, not your storefront — but it tells a judge and a plaintiff’s expert what the Commonwealth treats as the floor. Because the DOJ’s 2024 Title II web rule references the newer WCAG 2.1 Level AA, a private business is safer targeting WCAG 2.1 AA than the older 2.0 the state baseline still names; the WCAG success criteria spell out what that involves.

HB 2541 raised the bar in 2025

Virginia did not leave the Act frozen in 2004. HB 2541, enacted in 2025, modernized it — expanding scope to all disabilities and embedding accessibility into how public bodies buy technology (Allyant on HB 2541; Virginia LIS bill record). Under the amended Va. Code § 2.2-3503, vendors selling ICT to a covered Virginia entity must certify accessibility conformance or supply a vendor-paid Accessibility Conformance Report with a remediation roadmap (Va. Code § 2.2-3503). The duties phase in by population — entities of 50,000 or more and higher education start April 24, 2026, smaller entities April 26, 2027 — so public-sector vendors should expect that clause in their contracts.

Who’s getting sued — and where Virginia fits

Nationally, website accessibility litigation rebounded in 2025: roughly 3,117 website cases were filed in federal court, about a 27% increase over 2024 and around 36% of all ADA Title III filings, per Seyfarth’s ADA Title III tracker. That volume concentrates in a few plaintiff-friendly venues — New York led with about 1,021 filings and Florida with roughly 961 — while Virginia is not a top filing state: the lack of clear pro-plaintiff Fourth Circuit precedent gives serial filers reason to route their volume elsewhere.

But “fewer filings” is not “no filings.” Virginia businesses still face these claims as suits in the Eastern District of Virginia (Alexandria, Richmond, Norfolk, Newport News) or the Western District (Roanoke, Charlottesville, Abingdon) — Mejico’s home — and as pre-suit demand letters that never hit a docket. Targeted sectors mirror the national pattern: e-commerce, restaurants, hospitality, and any site with online ordering or booking. The cited barriers are the usual ones — missing alt text, unlabeled forms, weak color contrast, content unreachable by keyboard — the failures the DOJ flags in its web accessibility guidance. If a letter arrives, see what to do after a demand letter and how serial plaintiffs operate.

How a Virginia business reduces exposure

The open circuit cuts both ways: no settled precedent to fear, but Mejico shows you can’t dismiss your way out of a Title III claim. The reliable move is a site that survives a real assistive-technology test:

  1. Audit against WCAG 2.1 AA. Start with a manual accessibility audit that pairs automated scanning with keyboard and screen-reader testing. The failures automated tools miss — illogical reading order, unlabeled controls, misleading ARIA — are the barriers a plaintiff’s expert documents to establish the personally-encountered injury that survived Mejico’s standing challenge.
  2. Remediate the real code. This is the step overlay widgets skip. Curbcut’s manual remediation rewrites the HTML, ARIA, and JavaScript by hand — real alt text, contrast meeting 4.5:1, full keyboard operability, and accessible forms with labels and error messaging. Because an overlay can itself become a target and often makes screen-reader use worse, Curbcut is deliberately anti-overlay; see whether accessibility overlays actually work before trusting one.
  3. Document the conformance. Keep the audit and remediation logs and publish an accessibility statement naming WCAG 2.1 AA. That paper trail supports a good-faith record against a Mejico-style claim — and, if you sell to the public sector, grounds the vendor certification HB 2541 requires under § 2.2-3503.

That program costs less than one round of E.D. or W.D. Va. litigation. Find where your site stands with a free accessibility scan, then let [EXPERT_NAME] and the [AGENCY_NAME] team remediate by hand — and see how to avoid an ADA lawsuit for the broader playbook.

Authoritative resources for Virginia

The sources that govern a Virginia claim: the case — Mejico v. Alba Web Designs, LLC (W.D. Va. 2021); the statute — the Information Technology Access Act, Va. Code Title 2.2, Ch. 35, as amended by HB 2541 (2025); the standard — VITA’s ITRM Standard GOV103-00; and the federal baselines — ADA.gov web guidance and the W3C Web Accessibility Initiative.

The bottom line for Virginia

Virginia’s profile is uncertainty at the federal level and clarity at the state level. The Fourth Circuit has set no controlling rule on whether a website is a public accommodation — but Mejico proves a Virginia judge will read Title III broadly when squarely presented, so the “it’s not a place” defense is no safe harbor. Meanwhile the Information Technology Access Act, sharpened by HB 2541, settles which standard the Commonwealth recognizes. The one variable you control is whether your site meets it — and that’s what Curbcut remediates by hand, file by file.