ADA & WCAG Web Accessibility

The Americans with Disabilities Act (ADA) was signed into law in 1990, long before the modern web existed. Titles II and III — which cover government entities and places of public accommodation, respectively — have been interpreted by courts and the DOJ to include websites, mobile apps, and digital services.

Title II covers state and local governments: city websites, public school districts, county offices, utility districts, public parks. These entities must ensure their digital services are accessible to people with disabilities.

Title III covers businesses open to the public — trades companies, service businesses, retailers, restaurants. Courts have consistently held that a company's website is a "place of public accommodation" subject to Title III.

The legal standard the DOJ and courts reference is WCAG (Web Content Accessibility Guidelines), developed by the W3C. The current applicable level is WCAG 2.1 and 2.2, Level AA.

WCAG is organized around four principles — content must be Perceivable, Operable, Understandable, and Robust (POUR). At Level AA, the practical requirements include:

Perceivable

• Alt text on all meaningful images — screen readers need text descriptions for photos, logos, charts, and icons.
• Captions on all videos — both pre-recorded and live video must be captioned.
• Color contrast ratio of 4.5:1 for normal text, 3:1 for large text — low-contrast text fails users with low vision.
• Text can be resized to 200% without losing content or functionality.

Operable

• Full keyboard navigability — every action possible with a mouse must be possible with a keyboard alone.
• No keyboard traps — users must be able to navigate away from any component.
• Skip navigation links — allow keyboard users to jump past repetitive header/nav content.
• No content that flashes more than 3 times per second — seizure risk for photosensitive users.

Understandable

• Page language declared — the HTML lang attribute must be set so screen readers pronounce content correctly.
• Error messages are descriptive — form errors must explain what went wrong and how to fix it.
• Labels on all form inputs — every field must have a visible or programmatic label.

Robust

• Valid, semantic HTML — proper use of HTML elements (headings, lists, buttons, forms) so assistive technologies can interpret them.
• ARIA attributes where needed — ARIA labels, roles, and states for interactive components that HTML alone can't describe.
• Status messages programmatically determined — dynamic content changes (e.g., "Form submitted") must be announced to screen readers.

WCAG 2.2 (published October 2023) added new criteria including focus not obscured, target size minimum (24x24 CSS pixels for interactive elements), and dragging movements having keyboard alternatives.

In April 2024, the DOJ published its final rule for Title II, establishing WCAG 2.1 Level AA as the formal accessibility standard for state and local government websites and mobile apps.

Compliance deadlines:

• Larger entities (populations over 50,000): must comply by April 24, 2026
• Smaller entities (populations under 50,000): must comply by April 26, 2027

This covers every county, city, public school district, public library, transit authority, and municipality. There is no "best efforts" defense — the standard is technical compliance with WCAG 2.1 AA.

For private businesses (Title III), no equivalent final rule has been published yet — but courts continue to apply WCAG 2.1 AA as the de facto standard, and the DOJ has filed briefs supporting this position in major cases.

Read the full enforcement story in DOJ ADA Enforcement & Settlements.

AI has introduced new compliance dimensions that the original WCAG guidelines didn't anticipate:

• AI-generated content needs manual alt text. Image generation tools (Dall-E, Midjourney, Stable Diffusion) produce images without alt text. If you use AI imagery on your site, you must add descriptive alt text — the AI doesn't do this automatically.
• AI chatbots must be keyboard accessible. If you add an AI chatbot to your site, its interface must meet WCAG — keyboard navigable, screen-reader compatible, with proper ARIA attributes. Many off-the-shelf AI chat widgets fail these tests.
• AI-generated videos require captions. AI video tools (Synthesia, HeyGen, Runway) generate video content without captions. Any video published to your site must be captioned.
• Dynamic AI content needs status announcements. If AI components update content dynamically (streaming text, loading states), ARIA live regions must announce those changes to screen readers.

See the full picture: AI & the New Compliance Landscape.

Trades businesses (HVAC, plumbing, electrical, roofing)

If your business has a public-facing website (virtually all do), you are a "place of public accommodation" under Title III. Courts have found HVAC companies, plumbing businesses, and other service contractors liable for inaccessible websites. The most common failure points: missing alt text on project photos, low-contrast text, inaccessible contact forms, and no keyboard navigation on mobile menus.

Plaintiff's attorneys use automated scanning tools that identify these failures in minutes. The lawsuit process is often demand-letter first — you'll receive a letter demanding remediation and legal fees before any court filing. The cost of early settlement is typically $5,000–$25,000. The cost of defense is significantly higher.

K–12 schools and school districts

Public schools are covered under both Title II (as government entities) and Section 504 of the Rehabilitation Act (as recipients of federal funding). Every page — the main website, parent portals, learning management systems, food service pages, and enrollment forms — must meet WCAG 2.1 AA under the 2024 final rule.

The Office for Civil Rights (OCR) at the Department of Education enforces Section 504 and regularly investigates complaints about inaccessible school websites, inaccessible PDFs (class schedules, enrollment forms, lunch menus), and inaccessible online learning platforms.

Municipalities and government entities

Cities, counties, utility districts, transit authorities, and other government bodies are directly covered by the 2024 DOJ Title II final rule. Compliance is not optional — it is legally mandated, with the deadline tied to population size (see above). This covers utility payment portals, permit applications, public meeting agendas, zoning information, and any other digital service provided to the public.

For full industry breakdowns, see Compliance by Industry.

Does an accessibility widget/overlay make me compliant?

No. Overlays (like UserWay, AudioEye, or AccessiBe) do not make a non-compliant site compliant. Multiple courts and the DOJ have made clear that overlays do not satisfy ADA requirements. They mask underlying failures without fixing them. Genuine compliance requires fixing the source code.

Do I need an accessibility statement?

It is strongly recommended. An accessibility statement demonstrates good-faith effort, provides a feedback mechanism for users who encounter barriers, and signals to plaintiffs' attorneys that you are actively working on compliance. It doesn't eliminate liability but is considered a mitigating factor.

What is the difference between ADA and Section 508?

Section 508 of the Rehabilitation Act applies specifically to federal agencies and companies that contract with the federal government. It also references WCAG 2.1 AA as its technical standard. ADA applies more broadly to all businesses and state/local governments. Many organizations must meet both.