United States Web Accessibility Laws

What web accessibility means

The term accessibility refers to the ability to perceive, operate, understand, and use something — in this case, the web. Web accessibility ensures that users with disabilities (permanent, temporary, or situational) can access the same information, complete the same tasks, and participate in the same online services as anyone else. It benefits users with vision, hearing, motor, cognitive, and neurological impairments, users with age-related limitations, users on slow connections or mobile devices, and users whose context (loud environment, bright sunlight, one-handed operation) prevents normal interaction with a site.

The international standard referenced by essentially every US accessibility law is the Web Content Accessibility Guidelines (WCAG), published by the World Wide Web Consortium (W3C). Released versions:

• WCAG 2.0 — published December 2008. Still the standard referenced by Section 508 (2017 refresh) and many older contracts.
• WCAG 2.1 — published June 2018. Adds 17 new success criteria focused on mobile, low vision, and cognitive disabilities. Referenced by the DOJ’s April 2024 ADA Title II Final Rule.
• WCAG 2.2 — published October 5, 2023. Adds 9 new success criteria including Focus Not Obscured, Target Size (Minimum), Consistent Help, Accessible Authentication, and Redundant Entry. Current version.

WCAG’s four principles are POUR: Perceivable, Operable, Understandable, Robust. Each guideline has success criteria at three levels — A (minimum), AA (standard target for most legal requirements), and AAA (advanced, often aspirational). Most US regulations require Level AA.

Types of disability to consider

The CDC reports that roughly 1 in 4 US adults (~27%) lives with some form of disability — a figure that has grown over the past decade as diagnostic awareness has improved. Disabilities fall into three broad modes:

1. Permanent — long-term or lifelong conditions: blindness, deafness, motor impairment, cognitive disability.
2. Temporary — short-term conditions: broken arm, eye surgery, concussion, ear infection affecting hearing.
3. Situational — context-driven: bright sunlight on a screen, loud environment where audio can’t be heard, holding a baby with one arm, slow network.

Accessibility that addresses permanent disabilities usually helps all three groups. A user with a broken wrist benefits from the same keyboard-only navigation that a permanent motor-impaired user relies on.

Why US businesses need to care

1. Avoid legal complications and lawsuits

ADA Title III lawsuits over inaccessible websites have climbed significantly — from roughly 2,700 in 2016 to over 11,000 per year by 2020–2022, stabilizing around 8,000–10,000 annually through 2024. Well-known companies sued for inaccessible websites include Domino’s Pizza (which went to the Supreme Court; certiorari denied 2019, letting the Ninth Circuit ruling stand), Target (2006–2008 NFB class action, settled $6 million plus fees), Netflix (2012, captioning), and dozens more across retail, healthcare, education, and hospitality.

2. Improve search engine rankings

Many accessibility best practices align with on-page SEO — descriptive alt text, proper heading hierarchy, clear link anchor text, server-rendered content, and fast load times all help both screen readers and search-engine crawlers. Google has confirmed that Core Web Vitals (LCP, INP, CLS) are formal ranking signals, and pages that meet accessibility thresholds tend to pass those metrics naturally.

3. Boost brand reputation and reach

Social media makes a bad accessibility experience visible quickly, and customer communities increasingly call out inaccessible sites by name. An accessible site reaches roughly 25% more potential users on the same marketing spend — a meaningful reach increase in any competitive category.

4. Improve usability for everyone

Most accessibility improvements — larger tap targets, clearer focus indicators, better contrast, real form labels, captioned video — improve usability for every user, not just those with disabilities. Conversion rates, task completion, and time-on-site all improve when a site is easier to use overall.

The major US web accessibility laws

The Rehabilitation Act of 1973 (Sections 504 and 508)

Signed into law by President Nixon on September 26, 1973, the Rehabilitation Act was the first US federal civil rights legislation protecting people with disabilities. It has been amended multiple times since — most significantly via the Workforce Investment Act of 1998, which substantially revised Section 508. Two provisions directly affect web accessibility:

Section 504

Prohibits disability-based discrimination by any employer or organization receiving federal financial assistance. Covered organizations include:

• Postsecondary institutions (universities, colleges)
• K–12 public schools
• Federally-funded projects and programs
• Federal agencies
• Organizations receiving federal grants or contracts

Section 504 predates and overlaps with the ADA; nothing in the ADA supersedes Section 504, and entities subject to both must comply with the stricter requirements between them.

Section 508

Added to the Rehabilitation Act by amendment in 1986 and substantially revised in the 1998 Workforce Investment Act, Section 508 requires that electronic and information technology (ICT) procured, developed, or used by federal agencies be accessible to people with disabilities. Section 508 applies to:

• Federal agency websites, software, documents, and apps
• Third-party vendors selling ICT to federal agencies
• Many state agencies (states receiving federal funds often adopt 508 via state law)

The 2017 Section 508 refresh

On January 18, 2017, the US Access Board published the Section 508 refresh — a comprehensive update that harmonized Section 508 with international accessibility standards by incorporating WCAG 2.0 Level AA by reference. The refresh became effective March 20, 2017, with mandatory compliance required from January 18, 2018. The refresh also updated Section 255 of the Telecommunications Act simultaneously.

Because Section 508 now references WCAG 2.0 AA directly, federal agency sites that conform to WCAG 2.0 AA automatically satisfy Section 508’s web content requirements. Many agencies are now voluntarily targeting WCAG 2.1 AA or 2.2 AA as forward-looking practice.

The Americans with Disabilities Act (ADA) of 1990

Signed into law by President George H.W. Bush on July 26, 1990, and amended by the ADA Amendments Act of 2008, the ADA is the most sweeping US disability rights legislation. Five titles cover different domains; two affect the web:

• Title II — state and local government services. Covers state and local public entities, including their websites and mobile apps.
• Title III — public accommodations and commercial facilities. Covers private-sector businesses open to the public: retailers, restaurants, hotels, healthcare providers, banks, hospitals, and so on.

The ADA text doesn’t mention websites explicitly — the law predates the mainstream web by several years. US courts have largely interpreted Title III to apply to business websites that are either extensions of physical locations (Target, Domino’s) or standalone places of public accommodation (Netflix). The legal interpretation varies by federal circuit but trends toward coverage.

DOJ’s April 2024 Final Rule under ADA Title II

This is the most significant US web-accessibility regulatory development in more than a decade. On April 24, 2024, the US Department of Justice published a Final Rule requiring that state and local government websites and mobile apps be accessible under WCAG 2.1 Level AA. Covered entities and deadlines:

• Entities serving populations of 50,000 or more: compliance required by April 26, 2027.
• Entities serving populations under 50,000, and all special district governments: compliance required by April 26, 2028.

These deadlines reflect the DOJ’s Interim Final Rule published April 20, 2026 (Federal Register 2026-07663), which extended both original deadlines (April 24, 2026 and April 26, 2027) by twelve months. DOJ stated it “overestimated the capabilities (whether staffing or technology) of covered entities to comply with the rule in the time frames provided.” The WCAG 2.1 AA requirement itself was not changed, and HHS’s separate May 2026 Section 1557 deadline for health programs was not extended.

The rule covers state and local government websites, web content, mobile apps, digital documents (PDFs, Word files, etc.), and online content associated with courses and services. There are limited exceptions for certain archived materials, pre-existing social-media posts, password-protected course content outside a K–12 context, and some classes of third-party content — but the exceptions are narrow, and most content an entity produces or controls is covered.

State and local governments that have not begun a systematic accessibility program are running short on time: the 2026 deadline is less than a year away for the largest entities, and full compliance requires audit, remediation, training, procurement changes, and ongoing maintenance workflows that take many months to implement.

The 21st Century Communications and Video Accessibility Act (CVAA) of 2010

Signed by President Obama on October 8, 2010, the CVAA extends existing communications accessibility laws into the internet age. The CVAA has two titles:

• Title I (Communications Access) — requires accessibility of advanced communications services (ACS), including email, text messaging, video conferencing, and instant messaging. Equipment and software used for these services (smartphones, apps, web browsers with ACS features) must be accessible to people with disabilities.
• Title II (Video Programming) — requires closed captioning of video programming distributed on the internet when the same programming was captioned on television. Also requires video description for major-network prime-time and children’s programming, and accessibility of video programming devices and user interfaces.

CVAA is enforced by the FCC. It has been particularly impactful on video streaming services (Netflix, Hulu, YouTube, Amazon Prime) and online video publishers, which must caption re-aired TV content and support accessible video players.

The Telecommunications Act of 1996

The Telecommunications Act opened telecom markets to competition but also included significant accessibility provisions:

• Section 255 — requires that telecommunications equipment and services be accessible to people with disabilities, “if readily achievable.” First product-design law specifically addressing disability accessibility. Updated by the 2017 Section 508/255 refresh to incorporate WCAG 2.0 AA by reference.
• Section 713 — requires closed captioning of video programming, with the FCC setting timetables and exemptions for economic hardship.
• Section 706 — directs the FCC to encourage deployment of advanced telecommunications, with particular attention to underserved populations and educational settings.
• Section 254 — universal service; requires affordable telecommunications access for libraries, schools, and healthcare organizations.
• Section 251(a)(2) — prohibits carriers from installing equipment that doesn’t comply with Sections 255 and 256 accessibility requirements.

The Telecom Act’s accessibility provisions are enforced by the FCC through its notice-and-comment rulemaking process. Members of the public can submit comments during rulemaking periods, which are published on the FCC website.

The Individuals with Disabilities Education Act (IDEA)

Originally enacted as the Education for All Handicapped Children Act of 1975, reauthorized and renamed Individuals with Disabilities Education Act (IDEA) in 1990, and subsequently reauthorized in 1997 and again in 2004 as the Individuals with Disabilities Education Improvement Act (IDEIA). IDEA guarantees a free appropriate public education (FAPE) to eligible children with disabilities, implemented via Individualized Education Programs (IEPs).

Eligibility requires a documented disability in one of 13 categories: autism, deaf-blindness, deafness, developmental delay (ages 3–9 in most states), emotional disturbance, hearing impairment, intellectual disability, multiple disabilities, orthopedic impairment, other health impairment (including ADHD), specific learning disability (including dyslexia), speech or language impairment, traumatic brain injury, and visual impairment. The disability must also adversely affect educational performance.

Because the internet is deeply embedded in K–12 education — for research, assignments, assessment, and increasingly instruction itself — IDEA creates implicit requirements that educational technology be accessible. Districts and schools must ensure that online curriculum, learning management systems, and assessment platforms work for students with IEPs. Section 504 and the ADA overlay additional requirements for schools that receive federal funding.

State-level accessibility laws

Several US states have enacted their own web accessibility requirements, often stricter than federal baselines:

• California — The Unruh Civil Rights Act allows ADA Title III claims to be pursued as state civil rights claims with statutory damages. California Government Code §11546.7 (AB 434, signed 2017) requires state agency websites to conform to WCAG 2.0 AA.
• New York — NY Human Rights Law has been interpreted by state courts to cover website accessibility. NY State Technology Law §103 requires state agency websites and digital services to meet accessibility standards.
• Colorado — HB21-1110 (signed 2021) requires state government and local government websites to meet accessibility standards, with phased compliance deadlines.
• Texas, Illinois, Minnesota, Virginia — have varying state-agency accessibility requirements.

Businesses serving customers in multiple states need to be aware that state-level laws can apply even when federal coverage is ambiguous — and California in particular drives significant accessibility litigation volume.

How ADA compliance ties into SEO

Google’s ranking systems reward the same things that accessibility requires. Specifically:

• Descriptive alt text — critical for screen readers; also a signal Google uses to understand image content.
• Proper heading hierarchy (one H1, structured H2/H3) — screen reader users navigate by heading; Google uses headings to understand page structure.
• Meaningful link text — “Read our crawl budget guide” beats “Click here” for both a screen reader user and Google’s algorithm.
• Semantic HTML (<nav>, <main>, <button>, real form elements) — improves both assistive-tech support and crawler parsing.
• Fast, stable page loading — Core Web Vitals directly; users with cognitive and motor disabilities particularly benefit from predictable, performant pages.
• Video transcripts and captions — CVAA requirement; also makes video content discoverable through text search.

Sites investing seriously in accessibility routinely see SEO improvements as a side effect — the work is legitimately dual-purpose.

What happens if your site isn’t compliant

Three main risk categories:

1. ADA Title III lawsuits — filed in federal court; remedies include injunctive relief (fix the site) plus attorneys’ fees (which drive most settlements). California plaintiffs can also pursue Unruh Act claims with statutory damages of $4,000+ per violation. Firms such as Seyfarth Shaw track annual ADA Title III federal filings, which hit peaks of 11,000+ per year in 2021–2022 and remain substantial through 2024–2025.
2. DOJ enforcement (Title II) — state and local governments missing the 2026/2027 deadlines face DOJ enforcement action. The Final Rule includes the full range of Title II remedies, including compliance reviews and federal litigation.
3. State law enforcement — varies by jurisdiction; California’s Unruh Act drives the highest volume, but other states (New York, Colorado) have increasingly active enforcement programs.

Some commonly-sued entities since 2015 include Target Corp, Netflix, Domino’s Pizza, Winn-Dixie, H&R Block, Harvard University, MIT, Kylie Cosmetics, and dozens of mid-size retailers. Most cases settle with agreed remediation plans; a smaller share proceed to litigation, where courts have increasingly ruled that ADA Title III applies to standalone commercial websites.

How to maintain compliance

Compliance is an ongoing process, not a one-time audit. A sensible program:

1. Keyboard-accessible navigation

Every interactive element reachable and operable via keyboard alone (Tab, Shift+Tab, Enter, Space, Arrow keys, Esc). No keyboard traps. Visible focus indicator at all times. See our manual accessibility testing guide for a fast check.

2. Accessible image content

Every image has appropriate alt text — descriptive for content images, empty (alt="") for purely decorative. Avoid images-of-text except for logos. Provide long-form descriptions for complex images (charts, infographics) either adjacent or via longdesc/link.

3. Properly labeled forms

Every form field has a programmatic label. Required fields are announced as required. Errors are announced with clear corrective guidance. Form completion doesn’t time out without warning. WCAG 2.2’s new 3.3.7 (Redundant Entry) and 3.3.8 (Accessible Authentication) add requirements for authentication flows specifically.

4. Avoid automatic navigation or media

Don’t auto-play video or audio. Don’t trigger automatic navigation or content changes based on focus alone (WCAG 3.2.1 On Focus). Any moving, blinking, or scrolling content that lasts more than 5 seconds should have pause/stop/hide controls (WCAG 2.2.2).

5. Captions and transcripts for media

All pre-recorded video has synchronized captions. Live video (where required) has real-time captions. Audio-only content has text transcripts. Video descriptions for major-network and regulated online content per CVAA.

6. Sufficient color contrast

Normal text must meet 4.5:1 contrast ratio against its background; large text (18pt, or 14pt bold) must meet 3:1. UI components and graphical objects have a 3:1 requirement (WCAG 1.4.11). Don’t rely on color alone to convey information — pair with icons, labels, or patterns.

7. Continuous testing

Combine automated tools (axe, WAVE, Pa11y, Lighthouse) with manual testing (keyboard, screen reader, zoom, forced-colors mode). Automated tools catch 30–50% of issues; manual testing catches the rest. Run automated checks in CI on every deploy; schedule quarterly manual audits on critical paths.

Frequently asked questions

Does the ADA apply to my commercial website?

Most likely yes, especially if your business has a physical location open to the public or if your website is a standalone commercial service. US courts have largely interpreted ADA Title III to cover business websites, though legal interpretation varies by federal circuit. Even where interpretation is ambiguous, the risk of litigation is high enough that most law firms advise compliance regardless.

What WCAG level do I need to meet?

Level AA is the standard target for virtually every US legal requirement. Section 508 (federal agencies) references WCAG 2.0 AA; DOJ’s April 2024 Rule (state/local government) references WCAG 2.1 AA. WCAG 2.2 AA is a reasonable forward-looking target that also satisfies 2.1 AA (the new 2.2 criteria are additions, not changes).

What’s the deadline for state and local government sites?

Under the DOJ April 2024 Final Rule, as amended by the April 20, 2026 Interim Final Rule: April 26, 2027 for entities serving populations of 50,000 or more, and April 26, 2028 for entities serving populations under 50,000 and all special district governments. The IFR extended both original deadlines (April 2026 / April 2027) by twelve months.

Does accessibility actually help SEO?

Yes. Alt text, heading hierarchy, descriptive link anchors, semantic HTML, and fast loading all help both assistive tech and search engines. Google’s Core Web Vitals (LCP, INP, CLS) overlap heavily with accessibility principles around predictable, fast, stable pages. Sites investing in accessibility routinely see SEO improvements as a side effect.

Can I get sued for my small business website?

Yes — ADA Title III has no minimum size exemption. Small businesses have been sued over inaccessible sites, especially in California where Unruh Act statutory damages apply per violation. The silver lining: most small-business sites can reach WCAG AA with modest investment if they start before litigation arrives, and most automated accessibility issues are cheap to fix when caught early.

What’s the single most valuable compliance step?

A baseline automated scan (axe, WAVE, or Lighthouse) plus one round of keyboard-only navigation testing on critical paths (homepage, signup, checkout, contact). Together these surface the majority of issues, at which point remediation can be prioritized by severity. Ongoing monitoring — not a one-time audit — is what separates sites that stay compliant from sites that drift.

Bottom line

US web accessibility law is a patchwork — Rehabilitation Act, ADA, CVAA, Telecommunications Act, IDEA, and a growing set of state laws — but the practical compliance target is consistent: WCAG 2.1 or 2.2 Level AA. The DOJ’s April 2024 Title II Final Rule is the biggest single regulatory change in over a decade, and it puts thousands of state and local government entities on the clock for 2026 and 2027 compliance. For private-sector sites, the exposure is ADA Title III litigation, which remains active and expensive. The accessibility work itself overlaps heavily with SEO, usability, and mobile-first design — meaning the compliance investment tends to return more than it costs, in both risk mitigation and in better performance for every user who visits your site.