ADA Title III and Website Accessibility: What Businesses Should Know

If your business sells to or serves the public, your website is part of how people reach you. For many people with disabilities, an inaccessible website is a closed door, and the Americans with Disabilities Act applies to that door more often than business owners expect. This article explains what Title III of the ADA covers, how it relates to the government deadline you may have seen, and a practical way to approach the work.

What Title III covers

Title III is the part of the ADA that applies to businesses open to the public, called public accommodations in the statute. The Department of Justice’s overview of businesses open to the public lists examples that include restaurants, hotels and motels, shops, movie theaters, private schools, doctors’ offices and private hospitals, day care centers, and gyms. Nonprofits that serve the public are covered too. Religious organizations and qualifying private clubs are exempt.

Title III requires covered businesses to give people with disabilities an equal opportunity to access the goods and services they offer, to communicate effectively, and to make reasonable modifications to policies and practices when needed. A private college or university is generally covered by Title III as a private school, which is a different path than a public university, covered by Title II as part of state government.

Why the government countdown is not your deadline

In 2024, the Department of Justice published a rule under Title II that sets a specific technical standard, WCAG 2.1 Level AA, for the web content and mobile apps of state and local governments, including public universities and community colleges. The DOJ fact sheet on the Title II web rule explains the compliance dates: April 26, 2027 for entities with populations of 50,000 or more, and April 26, 2028 for smaller entities and special district governments.

That rule does not apply to private businesses. There is no equivalent federal regulation that sets a compliance date or names a technical standard for business websites under Title III. This does not mean businesses have no obligation. It means the obligation arrives through the general requirements of the statute and through enforcement, not through a dedicated web rule with a countdown.

What the Justice Department has said about business websites

DOJ’s position appears in its guidance on web accessibility and the ADA: the ADA’s requirements apply to the goods, services, and activities that public accommodations offer on the web, and an inaccessible website can limit access to those offerings just as a physical barrier limits access to a building. The same guidance says businesses have flexibility in how they comply with the general requirements of nondiscrimination and effective communication, while still being required to comply.

Courts have not resolved every question in the same way. In Robles v. Domino’s Pizza, the Ninth Circuit held that the ADA applied to Domino’s website and app because they connected customers to the goods and services of its physical restaurants. Coverage is less settled for businesses that operate only online, with no physical location tied to what they sell, and the answer can differ by jurisdiction. The unsettled question is how far Title III reaches for web-only businesses, not whether the businesses it clearly covers can ignore accessibility.

Where WCAG fits

No Title III regulation currently names a technical standard for business websites. What exists is the Web Content Accessibility Guidelines from the W3C, a technical framework that describes what accessible web content looks like. WCAG 2.1 Level AA is the standard the Title II rule adopts for governments, WCAG 2.2 is the current W3C recommendation, and WCAG is the reference most often used in settlements, demand letters, and remediation plans. Working toward WCAG Level AA is the clearest available description of an accessible site, though meeting it does not by itself guarantee that a court would find a site compliant.

Barriers that tend to matter most

DOJ’s web guidance lists barriers it considers common:

• Poor color contrast. Light gray text on a white background that people with limited vision cannot read.
• Color used alone to convey meaning. Required fields marked only in red, or sale prices shown only by color.
• Missing text alternatives. Product photos, charts, and icons that a screen reader user cannot interpret because nothing describes them.
• Videos without captions. A product walkthrough or welcome video that conveys nothing to someone who is deaf.
• Inaccessible forms. Checkout, booking, or contact forms without labels, clear instructions, or error messages a screen reader can announce.
• Mouse-only navigation. Menus, carousels, and dialogs that a keyboard user cannot reach or escape.

These are rarely abstract problems. They land inside the tasks customers come to do: find a product, book an appointment, check out, read a menu, apply for a job, or ask a question. A barrier in the middle of a customer journey is the difference between a completed purchase and an abandoned one.

A manageable way to work on it

A workable approach is less dramatic than it sounds:

1. Scan the site. Automated tools find widespread, detectable issues quickly and give you a baseline.
2. Test the important journeys manually. Keyboard testing and screen reader checks on the paths customers actually take cover what scanners cannot judge.
3. Prioritize by impact. A broken checkout button outranks a missing alt attribute on a decorative image.
4. Assign each finding an owner. Accessibility work stalls when it belongs to everyone.
5. Fix and verify. Apply the change, then repeat the check that found the problem to confirm it is gone.
6. Keep the record. Note what was found, who was responsible, what changed, and how it was checked.

What Accessibility Scans Can and Cannot Tell You goes deeper on where automated and manual methods each apply, and How to Prioritize Accessibility Issues covers the ordering question.

Why checking again matters

Websites change constantly. New content gets published, templates get redesigned, and third-party components like booking widgets, chat tools, and payment flows update on their own schedules. Each change can introduce a barrier on a site that tested well last quarter. Periodic scans and a recheck of the main customer journeys after meaningful changes keep the picture current, and a repeating record shows the work is ongoing rather than a one-time project.

What records can document

Records are honest evidence of work done: what was found, who owned it, what was changed, and how the fix was verified. They support accountability inside the business and give counsel something concrete to work with if a question ever arrives. What records cannot do is prove compliance or prevent a lawsuit. A documented process does not settle whether a site meets a legal standard, and it does not stop anyone from filing a claim. It shows what the business actually did, which is a different and more defensible thing than a claim that everything was fine.

If a complaint has already arrived

If you are reading this because a demand letter or lawsuit has already reached your business, the immediate questions are different: what the document alleges, which deadlines apply, and what to preserve. What Happens After You Receive an ADA Website Demand Letter covers the first steps, and Facing a Website Accessibility Lawsuit? Here’s What to Do Next walks through the response once a case is filed.

A practical place to start

SiteRecord is built for the middle of this work: scan a site, review findings, assign them to people, verify the fixes, and keep the history in one place. A free account covers the scanning and tracking described above. Whether you use it or something else, the shape of the work is the same: find barriers, fix them, check the results, and keep a record that reflects what really happened.

This article is general educational information, not legal advice. Whether and how Title III applies to a particular business depends on the facts and the jurisdiction. Consult qualified counsel about your situation.