ADA website compliance is the practice of making a website usable by people with disabilities so that a business or government entity meets its obligations under the Americans with Disabilities Act. For a private business the standard is the ADA's general nondiscrimination duty; for a state or local government it is now a specific technical rule.
Every rule below comes from the Justice Department's web guidance and its 2024 Title II regulation, from the April 2026 interim final rule that moved its compliance dates, and from the W3C's guidelines, current as of October 2026. Educational, not legal advice: a lawyer owns whether a particular site is covered.
| Who you are | What binds your website | Technical standard | Compliance date |
|---|---|---|---|
| A business open to the public (ADA Title III) | The ADA's general nondiscrimination and effective communication duties | None by regulation; the Department names WCAG and Section 508 | No date; the duty is ongoing |
| A state or local government serving 50,000 or more people (Title II) | The Department's 2024 web and mobile app rule | WCAG 2.1 Level AA, incorporated by reference | April 26, 2027, extended from April 24, 2026 |
| A smaller public entity, or any special district government (Title II) | The same 2024 rule | WCAG 2.1 Level AA | April 26, 2028, extended from April 26, 2027 |
| A vendor building or hosting a public entity's web content | The entity's duty reaches content provided through contractual or licensing arrangements | WCAG 2.1 Level AA, through the contract | The entity's own date above |
What the ADA requires of a business website
Title III of the ADA requires a business open to the public to give people with disabilities full and equal enjoyment of its goods and services, and the Justice Department's position is that this reaches services offered on the web. No federal regulation sets a technical standard for that site, which is a different thing from no obligation.
The Department's web guidance puts it as flexibility with a floor: businesses and state and local governments have flexibility in how they comply with the ADA's general requirements of nondiscrimination and effective communication, but they must comply with those requirements. The Department says it does not have a regulation setting out detailed web standards, and points to the Web Content Accessibility Guidelines and Section 508 standards as helpful technical references.
The guidance sets the alternative route higher than most people assume: where a site is not accessible, an accessible alternative has to give an equal degree of access in hours of operation and in the range of options and programs available.
WCAG 2.1 AA is a rule for governments and a reference for everyone else
WCAG 2.1 Level AA became a binding technical standard on April 24, 2024, when the Justice Department published its Title II rule for state and local government web content and mobile apps. That rule took effect June 24, 2024, and incorporates the guidelines by reference rather than restating them. It does not cover private businesses.
Level AA is a defined bar rather than a direction of travel. The W3C's conformance guidance states that if Level AA conformance is specified, all Level A and all Level AA success criteria have to be met, and that partial conformance at Level A does not count. That precision is why WCAG is worth using where no rule imposes it: it turns an open-ended duty into a working list.
The Title II deadline most pages still print is a year out of date
The Title II compliance dates moved in April 2026. An interim final rule effective April 20, 2026 extended the deadline for public entities serving 50,000 or more people from April 24, 2026 to April 26, 2027, and the deadline for smaller entities and special district governments from April 26, 2027 to April 26, 2028.
The technical standard is unchanged, the rule moves the dates and nothing else, and the Department was explicit that covered entities keep an ongoing obligation to make web and app services accessible whatever the compliance date. It also takes comment after publication, so the dates carry an October 2026 stamp rather than a guarantee.
The WCAG 2.1 AA checks you can run yourself in an hour
Seven Level AA criteria can be checked on a small business site without a specialist, using a browser and a contrast tool. They turn on measurable properties of the page rather than on editorial judgment, which is why a non-developer can confirm them.
| Success criterion | What it requires | How to check it |
|---|---|---|
| 1.4.3 Contrast (Minimum) | At least 4.5 to 1 for text, or 3 to 1 for large text | Run a contrast checker on body text, buttons and grey captions |
| 1.4.10 Reflow | Content works at 320 CSS pixels without two-dimensional scrolling | Narrow the window to 320 pixels; look for sideways scrolling |
| 1.4.11 Non-text Contrast | Components and graphics meet 3 to 1 against adjacent colors | Check field borders and icon buttons, not only text |
| 1.4.12 Text Spacing | Content survives adjusted line, paragraph, letter and word spacing | Apply a text-spacing bookmarklet and look for clipped text |
| 2.4.7 Focus Visible | A keyboard-operable interface has a visible focus indicator mode | Tab through the page; watch for an outline on every stop |
| 3.2.4 Consistent Identification | Components with the same function are identified consistently | Compare the booking button on every template |
| 4.1.3 Status Messages | Status messages reach assistive tech without receiving focus | Submit a form with an error; confirm it is announced, not only shown |
Two caveats from the W3C's conformance guidance belong with it: content has to rely only on accessibility-supported technologies, and some criteria, audio control and pause-stop-hide among them, apply to all content on a page rather than only the part claimed as conformant. The seven are a start on the AA set, not the set.
What the filing numbers show, and what they do not
Website accessibility cases are a large and growing share of ADA Title III litigation. Seyfarth Shaw's tracker counted 3,117 website accessibility lawsuits filed in federal court in 2025, up 27 percent on 2024 and 36 percent of the 8,667 Title III cases filed that year, against 2,452 of 8,800 cases in 2024.
The firm's analysis, published March 2026, puts monthly filings between 219 in June and 319 in July 2025, and states the limit of its own count: defense counsel handle many more demand letters that resolve privately than cases reaching a docket.
The honest reading is narrow. These are national federal filings, not Charlotte ones, and a count of claims says nothing about which sites get picked. What it supports is an order of work: the paths a keyboard and a screen reader have to complete, which are the booking form, the contact form and the navigation.
What this looks like when it runs as a built system
Accessibility holds when it is a property of the templates rather than a once-a-year pass. Mirastart builds sites where form fields carry real labels, the booking flow is keyboard operable with a visible focus state, and contrast ratios sit in the design tokens, so a new page inherits the checks instead of reopening them.
The systems this touches run in production for Charlotte businesses: the live-availability booking system on this site, the missed-call follow-up, the review request that goes to every customer at the same milestone, and the dashboard they report into. Conformance is a judgment a business makes with its counsel; a build removes the failures that are properties of the markup.
Sources
- U.S. Department of Justice, "Guidance on Web Accessibility and the ADA" - The Department's position used throughout: that the ADA's requirements reach the goods, services and privileges a public accommodation offers on the web; that businesses and state and local governments have flexibility in how they comply with the general nondiscrimination and effective communication requirements but must comply with them; that the Department does not have a regulation setting out detailed web standards, and that WCAG and the Section 508 standards are helpful technical references; and that an accessible alternative to an inaccessible site must give an equal degree of access in hours of operation and range of options and programs available. The guidance sets no technical standard, no safe harbor and no deadline for private businesses, and does not quantify litigation risk.
- ADA.gov, "Businesses That Are Open to the Public" (Title III topic page) - The Title III scope relied on here: that the ADA requires businesses open to the public, which the statute calls public accommodations, to provide full and equal enjoyment of their goods, services, facilities, privileges, advantages and accommodations to people with disabilities.
- Federal Register, "Nondiscrimination on the Basis of Disability; Accessibility of Web Information and Services of State and Local Government Entities" (DOJ final rule, 28 CFR Part 35) - The Title II rule: published April 24, 2024, effective June 24, 2024, adopting WCAG 2.1 Level AA as the technical standard for web content and mobile apps of Title II entities by incorporation rather than restatement; the original compliance dates of April 24, 2026 for entities serving 50,000 or more people and April 26, 2027 for smaller entities and special district governments; coverage of content the entity provides or makes available directly or through contractual, licensing or other arrangements; and the limited exceptions, including certain archived content and password-protected documents. This rule reaches public entities, not private businesses.
- Federal Register, "Extension of Compliance Dates for Nondiscrimination on the Basis of Disability; Accessibility of Web Information and Services of State and Local Government Entities" (DOJ interim final rule, 91 FR 20902) - The April 2026 extension, effective April 20, 2026, taking comment after publication: the date for public entities serving 50,000 or more people moves from April 24, 2026 to April 26, 2027, and the date for entities under 50,000 and special district governments from April 26, 2027 to April 26, 2028. The Department's stated grounds are its overestimate of the advancement and availability of accessibility technology and reported resource and staffing constraints, plus the litigation risk entities would face once the original dates passed. The technical standard is unchanged and covered entities retain an ongoing Title II accessibility obligation regardless of the compliance dates.
- ADA.gov, "Fact Sheet: New Rule on the Accessibility of Web Content and Mobile Apps Provided by State and Local Governments" - The Department's plain-language summary of the Title II rule, used to confirm the standard, the two tiers of covered entity and the rule's exceptions. Written against the original compliance dates, which the 2026 interim final rule above superseded.
- W3C, "Web Content Accessibility Guidelines (WCAG) 2.1" - The guidelines themselves, and the source for the seven Level AA success criteria in the table: 1.4.3 Contrast (Minimum), at least 4.5:1 for text and 3:1 for large text; 1.4.10 Reflow, content usable at 320 CSS pixels without two-dimensional scrolling; 1.4.11 Non-text Contrast, 3:1 for interface components and graphics against adjacent colors; 1.4.12 Text Spacing; 2.4.7 Focus Visible; 3.2.4 Consistent Identification; and 4.1.3 Status Messages. The how-to-check column is practical guidance, not part of the recommendation.
- W3C Web Accessibility Initiative, "Understanding Conformance" (WCAG 2.1) - The conformance rule quoted in prose: specifying Level AA conformance requires that all Level A and all Level AA success criteria be met, and conformance at any level requires all Level A criteria, so partial conformance at Level A does not count. Also the two caveats carried above: content must rely only on accessibility-supported technologies, and some criteria apply to all content on a page rather than only to the part claimed as conformant.
- Seyfarth Shaw, "Federal Court Website Accessibility Lawsuit Filings Bounce Back in 2025" (ADA Title III blog, Kristina M. Launey and Minh N. Vu) - The firm's own count, published March 2026: 3,117 website accessibility lawsuits filed in federal court in 2025, a 27 percent increase on 2024 and 36 percent of the 8,667 ADA Title III cases filed that year, against 2,452 of 8,800 in 2024; monthly filings ranging from 219 in June to 319 in July. The post also states that defense counsel handle many more demand letters that resolve privately than cases that reach court, so the count understates claim volume. These are national federal filings; the analysis reports no Charlotte or North Carolina breakdown and no data on which sites are targeted.