Summary. Thousands of federal lawsuits are filed every year alleging that a website or mobile app is inaccessible to people with disabilities, and most settle quickly because the legal question is unsettled while the technical question usually is not. This article explains the state of the law and, more usefully, what to actually do about it: whether and when a website is covered by Title III of the Americans with Disabilities Act, the circuit split over whether a physical place is required and the nexus test that governs in the Ninth Circuit after Robles v. Domino's Pizza, the Department of Justice's 2024 rule adopting a technical standard for state and local government websites and what it signals, and the state law overlay that supplies statutory damages where the federal statute does not. It then turns to engineering: what the Web Content Accessibility Guidelines actually require, the small number of defects that generate most complaints, why automated scanners catch only a fraction of them, and why accessibility overlay widgets have become a liability rather than a solution. It closes with a remediation program, a demand-letter response playbook, a worked example, an FAQ, and related reading.

A retailer's general counsel receives a demand letter on a Tuesday. It says the company's website violates the Americans with Disabilities Act, lists eleven specific defects, and offers to resolve for $18,000 plus a remediation commitment. The letter is professionally written. The defects are real. The lawyer has never met the plaintiff, who lives in another state and has never bought anything from the company.

The instinct is outrage. The correct response is triage, and then engineering.

Here is the thing that surprises most executives: the eleven defects in that letter are almost certainly fixable, most of them by a competent front-end developer in under a week, and several of them are also hurting the company's search rankings and conversion rates. The lawsuit is annoying. The underlying problem is a product defect that has been sitting there for years, blocking real customers.

The short answer

  • Title III of the ADA, 42 U.S.C. §§ 12181 to 12189, prohibits discrimination "on the basis of disability in the full and equal enjoyment of the goods, services, facilities, privileges, advantages, or accommodations of any place of public accommodation." § 12182(a).
  • There is no federal regulation specifying a technical standard for private websites. The Department of Justice has repeatedly stated that websites of public accommodations are covered, without issuing a rule for them.
  • The circuits are split on whether a website must have a nexus to a physical location to be covered.
  • Courts and settlements overwhelmingly use WCAG 2.1 Level AA as the de facto standard, and the DOJ adopted that standard by rule in 2024 for state and local government entities under Title II.
  • Remedies under Title III are injunctive relief plus attorney's fees. § 12188(a). No damages. That is why demand letters focus on fees and why state statutes matter.
  • State statutes supply damages. California's Unruh Civil Rights Act, Cal. Civ. Code § 51, provides a minimum of $4,000 per violation and treats an ADA violation as an Unruh violation. New York's state and city human rights laws also provide damages.

Part I: Coverage

Is a website a "place of public accommodation"?

Section 12181(7) lists twelve categories of public accommodations, all of which are physical facilities: hotels, restaurants, theaters, stores, service establishments, and so on. The list was written in 1990.

Three approaches have emerged:

1. The nexus approach (Ninth Circuit, and the most common). A website is covered if there is a sufficient connection between the website and the goods or services of a physical place of public accommodation.

Robles v. Domino's Pizza, LLC, 913 F.3d 898 (9th Cir. 2019), is the leading case. A blind customer could not order from Domino's website or app using a screen reader. The Ninth Circuit held the ADA applied because the website and app "connect customers to the goods and services of Domino's physical restaurants," and rejected the argument that applying the ADA without a DOJ technical rule violated due process. The Supreme Court denied certiorari.

2. The broad approach (First, Second, and Seventh Circuits, in varying formulations). Public accommodations are not limited to physical structures. The First Circuit's decision involving a health insurer, and the Seventh Circuit's language treating a "place of public accommodation" as including a provider of services that does not require entry to a physical facility, support coverage of internet-only businesses.

National Association of the Deaf v. Netflix, Inc., 869 F. Supp. 2d 196 (D. Mass. 2012), applied this reasoning to a streaming service with no physical locations, holding that Netflix's Watch Instantly service was covered.

3. The narrow approach. The Eleventh Circuit held in Gil v. Winn-Dixie Stores, Inc., 993 F.3d 1266 (11th Cir. 2021), that a website is not itself a place of public accommodation and that the plaintiff had not shown the website's inaccessibility denied him access to the physical store's goods and services. That opinion was vacated as moot when the panel granted rehearing and the case was dismissed, 21 F.4th 775 (11th Cir. 2021), so it is not binding precedent, but its reasoning continues to be cited by defendants.

Practical consequence: if your business has any physical location, assume coverage. If it is internet-only, coverage depends on the circuit, and you should assume coverage anyway, because the cost of compliance is lower than the cost of being the test case.

Public entities under Title II, and the 2024 rule

Title II covers state and local governments. In 2024, the DOJ issued a final rule adopting WCAG 2.1 Level AA as the technical standard for web content and mobile apps of public entities, with compliance deadlines phased by entity size (generally two or three years from publication).

That rule does not bind private businesses. But it matters for three reasons:

  1. It confirms the federal government's view that WCAG 2.1 AA is the operative standard.
  2. Private entities that contract with or serve public entities will face flow-down requirements.
  3. Courts routinely look to it as evidence of a reasonable standard.

Section 508 and federal contractors

Section 508 of the Rehabilitation Act, 29 U.S.C. § 794d, requires federal agencies to make their electronic and information technology accessible. The Revised 508 Standards incorporate WCAG 2.0 Level AA by reference.

If you sell software or services to the federal government, expect to provide a Voluntary Product Accessibility Template (VPAT), now typically in the Accessibility Conformance Report format. Producing an honest VPAT requires an actual audit; producing a dishonest one creates False Claims Act exposure.

Section 504 of the same Act reaches recipients of federal financial assistance, which sweeps in universities, hospitals, and many nonprofits.

Other federal statutes

  • Air Carrier Access Act, 49 U.S.C. § 41705, and its Department of Transportation regulations impose specific website and kiosk accessibility requirements on air carriers. Airlines are generally exempt from Title III but covered here.
  • Communications and Video Accessibility Act requirements for captioning and advanced communications services.
  • Fair Housing Act and Section 1557 of the Affordable Care Act each add requirements in their sectors.

State law: where the money is

Because Title III provides no damages, plaintiffs pair it with state claims.

  • California's Unruh Civil Rights Act, Cal. Civ. Code § 51, provides statutory damages of no less than $4,000 per violation, plus fees, and § 51(f) makes an ADA violation an Unruh violation per se. California also enacted procedural reforms aimed at high-frequency litigants, including pleading requirements and fee limits in construction-related accessibility cases, but website claims continue in volume.
  • New York State Human Rights Law and the New York City Human Rights Law permit compensatory damages, and the city law is construed liberally.
  • Other states, including Massachusetts, Colorado, and Washington, have accessibility or public accommodation statutes with varying remedies.

Between California and New York, those two states account for a very large share of all website accessibility filings.

Standing

Defendants routinely challenge standing, particularly for "testers" who visit a site to check compliance rather than to buy anything.

The Supreme Court took up tester standing in Acheson Hotels, LLC v. Laufer, 601 U.S. 1 (2023), but resolved the case as moot after the plaintiff dismissed her claims, leaving the question open. Lower courts continue to split, with most finding standing where the plaintiff alleges a concrete intent to return and actually encountered barriers.

The practical defense is narrower: many complaints fail to allege that the plaintiff encountered a specific barrier that impeded a specific transaction they intended to complete. Motions attacking that gap succeed more often than broad tester-standing arguments. See Motions to Dismiss Under Rule 12.

Part II: What accessibility actually requires

Lawyers who understand the technical substance handle these cases far better, and the substance is not difficult.

WCAG in one page

The Web Content Accessibility Guidelines, published by the W3C, organize requirements under four principles. Content must be:

  • Perceivable: users can perceive the information (text alternatives, captions, contrast, adaptable layout).
  • Operable: users can operate the interface (keyboard access, enough time, no seizure triggers, navigable structure).
  • Understandable: content and operation are comprehensible (readable, predictable, input assistance).
  • Robust: content works with current and future assistive technologies (valid markup, correct name/role/value).

Each guideline has success criteria at three conformance levels: A (minimum), AA (the operative legal standard), and AAA (aspirational).

WCAG 2.1 added criteria for mobile, low vision, and cognitive disabilities. WCAG 2.2, published in 2023, added nine more, including focus appearance, dragging alternatives, target size, consistent help, and accessible authentication. The DOJ's Title II rule adopted 2.1 AA; 2.2 AA is where new development should aim.

The defects that generate almost all complaints

Demand letters are remarkably repetitive. The recurring list:

  1. Missing or unhelpful alternative text on images. A screen reader announces "image" or a filename instead of describing the content or function.
  2. Unlabeled form fields. Inputs without associated <label> elements, so a screen reader user hears "edit text" with no idea what to enter. Checkout forms are the classic case.
  3. Keyboard traps and missing focus indicators. A user navigating by keyboard cannot escape a modal, or cannot see where focus is.
  4. Insufficient color contrast. Light gray text on white. WCAG 2.1 AA requires a 4.5:1 ratio for normal text, 3:1 for large text.
  5. Improper heading structure. Headings used for styling rather than structure, so screen reader users cannot navigate the page outline.
  6. Inaccessible custom controls. Dropdowns, carousels, sliders, and menus built from <div> elements without ARIA roles, states, and keyboard handlers.
  7. Images of text, including navigation and promotional banners with no text equivalent.
  8. Video without captions, and audio without transcripts.
  9. PDFs that are scanned images, with no text layer or tagging.
  10. Timeouts without warning or an extension mechanism.
  11. Inaccessible error messages not programmatically associated with the field, or conveyed by color alone.
  12. Skipped landmark structure, so users cannot jump to main content.

Most of these are cheap to fix in isolation and expensive to fix in a legacy codebase, which is why the cost curve rewards early attention.

Automated testing catches only part of it

Automated scanners (axe, WAVE, Lighthouse, and commercial equivalents) reliably detect roughly a third of WCAG issues: contrast failures, missing alt attributes, missing form labels, and markup errors. They cannot evaluate whether alt text is meaningful, whether the reading order makes sense, whether a custom widget is operable, or whether an error message is comprehensible.

A defensible program uses:

  • Automated scanning in CI on every build (cheap, catches regressions).
  • Manual keyboard testing of every critical flow.
  • Screen reader testing with the combinations users actually use (NVDA with Firefox, JAWS with Chrome, VoiceOver with Safari on macOS and iOS, TalkBack on Android).
  • Testing with users with disabilities, which finds problems no checklist does.

Mobile applications

Native apps present the same requirements through platform accessibility APIs: accessibility labels and traits on iOS, content descriptions and accessibility node info on Android, sufficient touch target sizes, support for dynamic type and system font scaling, and correct focus order. The WCAG2Mobile guidance and the platform vendors' own accessibility documentation are the working references.

Apps are increasingly named in demand letters alongside websites, and they are often worse, because native controls are frequently replaced with custom drawing that discards the platform's built-in accessibility.

Overlays and widgets: a warning

A category of products promises one-line-of-JavaScript compliance: an overlay widget that adds a toolbar and attempts to remediate problems at runtime.

Take this seriously as a risk factor:

  • Hundreds of accessibility professionals, including many people with disabilities, have publicly opposed these products, and disability advocacy organizations have been outspoken.
  • Overlays have themselves been the subject of lawsuits, both against the sites using them and against vendors, and plaintiffs have alleged that overlays interfere with users' own assistive technology.
  • Regulators have brought action over deceptive claims that such tools produce compliance.
  • Most importantly, they do not fix the underlying markup. A screen reader user still encounters the unlabeled form field.

A vendor promise of compliance is not a defense. Remediate the code.

Part III: Responding to a demand letter or complaint

The first week

  1. Preserve. Litigation hold covering the site's code history, deploy logs, accessibility audits, vendor communications, and analytics. See Litigation Holds, Spoliation, and Rule 37(e).
  2. Snapshot the current site. Capture the pages identified, in the state they were in when the letter arrived, including the DOM. If you remediate first and preserve nothing, you cannot later dispute what the plaintiff alleges.
  3. Verify the allegations technically. Have a qualified engineer or auditor test each claimed defect. Some letters are accurate; some are boilerplate that does not match the actual site.
  4. Assess coverage. Physical locations? Circuit? Internet-only?
  5. Assess state law exposure. California and New York change the calculus substantially.
  6. Check insurance. Some CGL, EPL, and cyber policies respond; many do not. Notice promptly regardless.
  7. Identify the population. Is this a one-off or the first of many? Serial plaintiffs file in volume, and a defensible remediation posture protects against the next twenty letters.

Evaluating settlement

Most of these matters settle, and the terms are fairly standardized:

  • A remediation commitment to a specified standard (usually WCAG 2.1 AA) within a defined period, often 12 to 24 months.
  • Third-party auditing and periodic reporting.
  • Accessibility policy adoption and staff training.
  • Attorney's fees for the plaintiff.
  • Sometimes a damages payment where state law provides for it.
  • A release, whose scope deserves attention: a release covering only the named plaintiff leaves you exposed to the next one.

The strategic point: if you are going to remediate anyway, and you probably are, the settlement's real cost is the fees. Negotiating a longer remediation period with clear milestones is usually easier than negotiating the fee number down, and it is worth more operationally.

When to fight

Litigating is sometimes right:

  • The complaint is factually inaccurate about the defects.
  • Standing is genuinely weak: no allegation of a specific barrier tied to a specific intended transaction.
  • The site was already remediated before the complaint, making the injunctive claim moot (though voluntary cessation doctrine limits this).
  • You are in a circuit and posture where coverage is genuinely doubtful and you are prepared to be the test case.
  • The plaintiff's counsel has a pattern that supports a fee reduction argument, and the economics justify the fight.

Understand the asymmetry: the plaintiff seeks injunctive relief and fees. Your fees are not recoverable except in rare frivolousness cases. Litigation almost always costs more than settlement, so fight only for a reason beyond the individual case.

Part IV: Building an accessibility program

Compliance is a product-quality discipline, not a legal one. Here is what works.

Governance

  • Name an owner with authority.
  • Adopt a written accessibility policy referencing WCAG 2.1 AA (or 2.2 AA for new work).
  • Publish an accessibility statement with a feedback channel and a real response process. This is evidence of good faith and it produces useful bug reports.

Engineering

  • Add automated accessibility checks to CI, failing the build on new violations.
  • Adopt an accessible component library and stop building custom controls from generic elements.
  • Include accessibility acceptance criteria in every user story that touches the interface.
  • Require keyboard and screen reader testing in the definition of done for critical flows.
  • Train developers and designers; most defects come from not knowing, not from not caring.

Design

  • Contrast checked at design time, not after implementation.
  • Focus states designed, not left to browser defaults.
  • Do not convey information by color alone.
  • Specify heading hierarchy in designs.

Content

  • Alt text written by whoever writes the copy, with guidance on decorative versus informative images.
  • Captions for video, transcripts for audio.
  • Accessible PDFs, or HTML alternatives, which are usually better anyway.

Procurement

  • Require accessibility conformance reports from vendors.
  • Include accessibility warranties and remediation obligations in contracts, with a right to terminate for failure.
  • Audit embedded third-party components: payment widgets, chat, booking, review, and video players are frequent sources of defects you did not write. See Indemnification and Limitation of Liability.

Verification

  • Annual third-party audit of the critical paths.
  • Remediation backlog tracked with owners and dates.
  • Retest after each major release.

Two adjacent exposures companies forget

Employment systems under Title I. Title III gets the attention, but Title I of the ADA covers employment, and an inaccessible applicant tracking system, onboarding portal, benefits enrollment tool, or internal HR platform can be a failure to provide reasonable accommodation. Claims here come from employees and applicants rather than from serial filers, and they carry compensatory and punitive damages plus the EEOC charge process. Most companies audit the marketing site and never look at Workday, the intranet, or the timekeeping kiosk. Add internal systems to the inventory, and put accessibility requirements into HR software procurement. See How to Write an Employee Handbook.

Kiosks, point-of-sale, and physical-digital hybrids. Self-checkout terminals, tablet-based ordering, restaurant table kiosks, parking payment machines, and ticketing terminals sit at the intersection of the ADA's architectural standards and its effective-communication requirements. Touchscreen-only interfaces with no tactile or audio alternative have generated both private suits and DOJ enforcement. The 2010 ADA Standards for Accessible Design address reach ranges and operable parts; the interface itself is governed by the general prohibition on discrimination and by effective-communication obligations. If you deploy hardware with a screen, include an accessible interaction path (tactile keypad, headphone jack with audio guidance, screen reader mode) in the specification, because retrofitting deployed hardware is far more expensive than specifying it.

Educational technology. Institutions receiving federal funds are covered by Section 504 and, if public, by Title II and the 2024 rule. Learning management systems, courseware, proctoring software, and library databases have all been the subject of resolution agreements with the Department of Education's Office for Civil Rights. Vendors selling into education should expect procurement diligence on accessibility, and institutions should not accept a vendor's unaudited conformance claim.

Part III-A: Procurement, contracts, and the third-party problem

Most organizations do not build most of what appears on their sites. Payment widgets, chat, booking engines, review modules, video players, maps, analytics overlays, and consent banners all inject markup you did not write, and every one of them has produced accessibility defects in the wild.

Procurement requirements that work:

  • Require a current conformance report. An Accessibility Conformance Report in the VPAT format, dated within twelve months, prepared against WCAG 2.1 Level AA. Ask who prepared it: a self-assessment by the vendor's marketing team is not the same as an independent audit.
  • Test before you buy. Put the vendor's demo instance through keyboard-only traversal and a screen reader. Fifteen minutes reveals more than the report does.
  • Contract for conformance, not for effort. "Vendor represents that the Services conform to WCAG 2.1 Level AA" is a warranty. "Vendor will use commercially reasonable efforts to improve accessibility" is not.
  • Require remediation with deadlines, and a right to terminate without penalty for material non-conformance that is not cured.
  • Indemnity for third-party accessibility claims arising from the vendor's components, with the usual attention to caps and carve-outs. See Indemnification and Limitation of Liability.
  • Change control. A vendor that ships a redesign can reintroduce defects you already paid to fix. Require notice and a right to test before major releases.

The integration problem. A component that is accessible in isolation may fail in your page: duplicated landmarks, broken heading hierarchy, focus that jumps into an iframe and cannot get out, or a modal that traps keyboard users. Conformance is a property of the delivered experience, not of the parts. Test the integrated page.

Federal and public-sector procurement. If you sell to federal agencies, Section 508 conformance is a solicitation requirement, and inaccurate conformance representations can raise False Claims Act exposure. State and local procurement increasingly imposes parallel requirements, and the Department of Justice's Title II rule has pushed public entities to demand conformance from their vendors, which flows down to anyone selling into that market.

A note for vendors. Accessibility conformance is becoming a sales gate rather than a compliance afterthought. Companies that can hand a buyer a current, honest, independently prepared conformance report close deals faster than companies that cannot, and the cost of producing one is a fraction of the deal value it unblocks.

A worked example

Fern & Field Markets (fictional) operates 31 grocery stores in California and New York plus an e-commerce site and an iOS and Android app for pickup ordering. It receives a demand letter identifying nine defects on the ordering flow.

Coverage. Thirty-one physical stores plus a site that connects customers to those stores' goods. Under Robles, coverage is clear in the Ninth Circuit, and the physical nexus makes it clear nearly everywhere. There is no serious coverage defense.

State exposure. California means Unruh, with a $4,000 statutory minimum per violation, and New York means the state and city human rights laws. This is materially more than an ADA-only case.

Technical verification. An audit confirms eight of the nine allegations and finds fourteen additional issues the letter missed, most of them in the checkout flow:

  • Product images use filenames as alt text.
  • The quantity stepper is built from <div> elements with click handlers, unreachable by keyboard.
  • The "substitutions allowed" checkbox has no label association.
  • Error messages appear in red text with no programmatic association to the field.
  • The store-selector modal traps keyboard focus.
  • Promotional banners are images of text.
  • The mobile app's cart buttons have no accessibility labels.

Triage. The checkout defects block transactions and are the highest priority both legally and commercially. Fern & Field's analytics team runs a query and finds that the cart abandonment rate on screen-reader-associated sessions is dramatically higher than baseline, which turns the accessibility project into a revenue project and unlocks budget.

Remediation plan. Three phases:

  • Phase 1 (60 days): checkout and ordering flow to WCAG 2.1 AA, verified by audit and screen reader testing.
  • Phase 2 (six months): the rest of the site plus the mobile apps.
  • Phase 3 (ongoing): CI checks, component library adoption, training, annual audit.

Settlement posture. With Phase 1 underway and documented, Fern & Field can negotiate from strength: it offers a remediation commitment matching what it is already doing, a reasonable audit and reporting obligation, and a fee number, while pushing for a release broad enough to cover the flows being remediated. It also publishes an accessibility statement with a contact channel, which both demonstrates good faith and gives future complainants a place to go other than a lawyer.

Outcome. Settlement in the low five figures plus fees, a remediation schedule Fern & Field controls, and a site that converts better. The next demand letter, when it comes, meets a documented program.

What it would have cost to prevent. Roughly two engineers for six weeks at launch, plus contrast checks in the design system. That is a fraction of what the remediation-under-deadline actually cost, which is the general rule in this area.

Checklists

Immediate risk assessment

  • Do we have physical locations? Which circuits?
  • Do we sell into California or New York?
  • Has anyone ever run an accessibility audit? When?
  • Do we have an accessibility statement and feedback channel?
  • Do we use an accessibility overlay widget? (If yes, plan to replace it with real remediation.)
  • Do our vendors provide conformance reports?
  • Do our contracts contain accessibility warranties?
  • Does any insurance policy respond?

Technical baseline

  • Automated scan of top 25 pages and all critical flows.
  • Keyboard-only traversal of registration, search, product, cart, checkout, and account management.
  • Screen reader testing on at least two combinations, desktop and mobile.
  • Color contrast audit of the design system.
  • Form label and error-handling audit.
  • Video captioning and PDF tagging inventory.
  • Mobile app label and focus-order audit.
  • Third-party embedded component inventory.

Program

  • Written policy referencing WCAG 2.1 AA (2.2 AA for new work).
  • Named owner and reporting cadence.
  • CI enforcement with build failure on new violations.
  • Accessible component library.
  • Acceptance criteria in stories; definition of done includes keyboard and screen reader checks.
  • Designer, developer, and content author training.
  • Procurement requirements and contract terms.
  • Annual third-party audit with a tracked remediation backlog.
  • Published accessibility statement with a monitored contact channel.

If you receive a demand

  • Litigation hold and site snapshot (including DOM) before remediating.
  • Independent technical verification of each allegation.
  • Coverage and standing analysis.
  • State law damages exposure quantified.
  • Insurance notice.
  • Remediation plan started before negotiating.
  • Release scope negotiated carefully.

Frequently asked questions

Is there an official legal standard for private websites? No federal regulation specifies one. WCAG 2.1 Level AA is the de facto standard used in consent decrees, settlements, and court orders, and the DOJ adopted it by rule for state and local government entities in 2024. Build to it.

Does the ADA apply to a business with no physical location? It depends on the circuit. The First, Second, and Seventh Circuits have taken broader views; the Ninth applies a nexus test; the Eleventh's narrow decision was vacated as moot. Assume coverage unless counsel advises otherwise for your specific posture.

Can I be sued for damages under the ADA? Not under Title III, which provides injunctive relief and attorney's fees only. Damages come from state statutes, most significantly California's Unruh Act at $4,000 minimum per violation.

Will an accessibility widget protect us? No. Overlays do not fix the underlying code, have been the subject of litigation and regulatory action themselves, and are opposed by many accessibility professionals and disability advocates. They are a red flag, not a shield.

How much does remediation cost? It varies enormously with codebase age and quality. A modern site built with an accessible component library may need weeks. A legacy site with custom controls and thousands of PDFs may need a year and a dedicated team. The single largest cost driver is whether accessibility was considered at design time.

We fixed everything. Is the case moot? Voluntary cessation does not automatically moot a claim; the defendant must show it is "absolutely clear" the conduct will not recur. A documented program with governance, CI enforcement, and audits makes that showing much stronger than a one-time fix.

Do we have to make old PDFs accessible? Documents that are part of the goods and services offered generally must be accessible. A practical approach is to remediate documents in current use, provide HTML alternatives going forward, and offer an accommodation channel for older documents on request.

What about third-party content on our site? You are generally responsible for what appears on your site, including embedded widgets. Require conformance reports, test the integrated experience, and put accessibility obligations in vendor contracts with a termination right.

Are serial plaintiffs abusing the statute? That is a real and long-running policy debate, and courts and legislatures have responded with procedural reforms in some states. It is also not a defense in a case where the defects are real. The practical answer for a business is to remove the defects so that the volume filers move on.

Does accessibility help our business? Consistently, yes. Accessible markup improves search indexing, keyboard efficiency benefits power users, captions increase engagement, and clear form labeling reduces error rates. Roughly a quarter of American adults report some form of disability, which is a large market to exclude by accident.

Closing thought

Website accessibility is unusual among compliance obligations because the legal uncertainty is high and the technical answer is not. Nobody knows exactly which internet-only businesses Title III reaches. Everybody knows that a form field needs a label.

That asymmetry should drive strategy. Waiting for a federal rule has been a losing bet for fifteen years and remains one. Meanwhile the defects at issue are ordinary product defects: they block real users, they are diagnosable with free tools, and they get cheaper to fix the earlier they are found.

The businesses that handle this well stop treating it as a legal question. They put contrast ratios in the design system, an accessibility check in the build pipeline, and a line in the definition of done. Then, when the demand letter arrives, they can answer it with an audit report and a schedule instead of a check.

Related articles

This article is provided for general informational purposes and does not constitute legal advice. Coverage under Title III varies by circuit and state law remedies vary substantially. Consult qualified counsel about any particular demand letter or program.