Skip to main content
Pulxon
Menu

Web accessibility laws and standards

In the US and the EU, the rules for accessible websites point to the Web Content Accessibility Guidelines (WCAG) at level AA. Which version they point to, and who they cover, differs. This page lists the facts with their primary sources.

This section is general information, not legal advice. Laws, deadlines and court decisions change and differ from place to place. Talk to an attorney about your own situation. Pulxon is not a law firm. Checked against the sources on September 24, 2026.

At a glance

Accessibility rules, who they cover and the WCAG version they point to
RuleWho and whenPoints to
ADA Title II web rule (US)State and local governments: from April 26, 2027 for those serving 50,000 people or more, April 26, 2028 for smaller ones and special districts.WCAG 2.1 AA
Section 508 (US)US federal agencies and the technology they buy or build.WCAG 2.0 AA
EN 301 549 / European Accessibility Act (EU)EU public sector sites, and from June 28, 2025 many consumer products and services, such as online shops, under the European Accessibility Act.WCAG 2.1 AA

How the WCAG versions fit together

Each version keeps the success criteria of the one before and adds new ones, so a rule that points to WCAG 2.0 asks for fewer criteria than one that points to 2.1. WCAG 2.2 also retired one old criterion, 4.1.1 Parsing, as no longer needed. Pulxon checks against WCAG 2.2 A and AA, the latest version.

Added in WCAG 2.1 at level A and AA (12)

  • 1.3.4 Orientation (AA)
  • 1.3.5 Identify Input Purpose (AA)
  • 1.4.10 Reflow (AA)
  • 1.4.11 Non-text Contrast (AA)
  • 1.4.12 Text Spacing (AA)
  • 1.4.13 Content on Hover or Focus (AA)
  • 2.1.4 Character Key Shortcuts (A)
  • 2.5.1 Pointer Gestures (A)
  • 2.5.2 Pointer Cancellation (A)
  • 2.5.3 Label in Name (A)
  • 2.5.4 Motion Actuation (A)
  • 4.1.3 Status Messages (AA)

Added in WCAG 2.2 at level A and AA (6)

  • 2.4.11 Focus Not Obscured (Minimum) (AA)
  • 2.5.7 Dragging Movements (AA)
  • 2.5.8 Target Size (Minimum) (AA)
  • 3.2.6 Consistent Help (A)
  • 3.3.7 Redundant Entry (A)
  • 3.3.8 Accessible Authentication (Minimum) (AA)

ADA Title II web rule (US)

Who and when
State and local governments: from April 26, 2027 for those serving 50,000 people or more, April 26, 2028 for smaller ones and special districts.
Points to
WCAG 2.1, level AA
Citation
28 CFR part 35, subpart H (2024 rule; dates moved in April 2026)
Primary source
https://www.ada.gov/resources/2024-03-08-web-rule/ (opens in a new tab)
6 newer WCAG criteria that WCAG 2.1 does not include

Worth fixing for the people they affect, even where this rule does not ask for them.

  • 2.4.11 Focus Not Obscured (Minimum) (AA)
  • 2.5.7 Dragging Movements (AA)
  • 2.5.8 Target Size (Minimum) (AA)
  • 3.2.6 Consistent Help (A)
  • 3.3.7 Redundant Entry (A)
  • 3.3.8 Accessible Authentication (Minimum) (AA)

Section 508 (US)

Who and when
US federal agencies and the technology they buy or build.
Points to
WCAG 2.0, level AA
Citation
36 CFR part 1194, E205.4
Primary source
https://www.access-board.gov/ict/ (opens in a new tab)
18 newer WCAG criteria that WCAG 2.0 does not include

Worth fixing for the people they affect, even where this rule does not ask for them.

  • 1.3.4 Orientation (AA)
  • 1.3.5 Identify Input Purpose (AA)
  • 1.4.10 Reflow (AA)
  • 1.4.11 Non-text Contrast (AA)
  • 1.4.12 Text Spacing (AA)
  • 1.4.13 Content on Hover or Focus (AA)
  • 2.1.4 Character Key Shortcuts (A)
  • 2.5.1 Pointer Gestures (A)
  • 2.5.2 Pointer Cancellation (A)
  • 2.5.3 Label in Name (A)
  • 2.5.4 Motion Actuation (A)
  • 4.1.3 Status Messages (AA)
  • 2.4.11 Focus Not Obscured (Minimum) (AA)
  • 2.5.7 Dragging Movements (AA)
  • 2.5.8 Target Size (Minimum) (AA)
  • 3.2.6 Consistent Help (A)
  • 3.3.7 Redundant Entry (A)
  • 3.3.8 Accessible Authentication (Minimum) (AA)

EN 301 549 / European Accessibility Act (EU)

Who and when
EU public sector sites, and from June 28, 2025 many consumer products and services, such as online shops, under the European Accessibility Act.
Points to
WCAG 2.1, level AA
Citation
EN 301 549 V3.2.1, clause 9; Directive (EU) 2019/882
Primary source
https://eur-lex.europa.eu/eli/dir/2019/882/oj (opens in a new tab)
6 newer WCAG criteria that WCAG 2.1 does not include

Worth fixing for the people they affect, even where this rule does not ask for them.

  • 2.4.11 Focus Not Obscured (Minimum) (AA)
  • 2.5.7 Dragging Movements (AA)
  • 2.5.8 Target Size (Minimum) (AA)
  • 3.2.6 Consistent Help (A)
  • 3.3.7 Redundant Entry (A)
  • 3.3.8 Accessible Authentication (Minimum) (AA)

Court and regulator decisions

Decisions that shaped how US law treats websites and accessibility tools, oldest first.

  1. National Federation of the Blind v. Target Corp.

    N.D. Cal., filed 2006, class settlement 2008

    Blind shoppers could not use Target.com with screen readers. Target paid $6 million to a class of California shoppers, agreed to make the site accessible and had it tested by the National Federation of the Blind.

    Why it matters: The first major case about an online shop and screen reader users.

    Source for National Federation of the Blind v. Target Corp. (opens in a new tab)

  2. Robles v. Domino's Pizza, LLC

    913 F.3d 898 (9th Cir. 2019); US Supreme Court declined review, October 2019

    A blind customer could not order through Domino's website and app with a screen reader. The Ninth Circuit held that the ADA applies to them because they connect customers to Domino's restaurants.

    Why it matters: The best-known appeals decision applying the ADA to a business website and app.

    Source for Robles v. Domino's Pizza, LLC (opens in a new tab)

  3. Gil v. Winn-Dixie Stores, Inc.

    993 F.3d 1266 (11th Cir. 2021), vacated as moot, 21 F.4th 775 (11th Cir. 2021)

    The Eleventh Circuit held that a grocery website was not a place of public accommodation under ADA Title III, then vacated that decision because the dispute had become moot.

    Why it matters: US courts still disagree about websites that are not tied to a physical store.

    Source for Gil v. Winn-Dixie Stores, Inc. (opens in a new tab)

  4. FTC v. accessiBe Inc.

    Federal Trade Commission final order, April 2025

    accessiBe paid $1 million for claiming that its automated widget could make any website meet WCAG. The order bars such claims without evidence.

    Why it matters: A widget on its own does not fix the problems listed in this report; the code has to change.

    Source for FTC v. accessiBe Inc. (opens in a new tab)

What an automated check can tell you

Automated tools detect only part of accessibility barriers. Pulxon’s free check shows which WCAG 2.2 A and AA rules fail on a page, which of the rules above include each one, and how to fix it. The rest needs a person testing with a keyboard and screen readers. See how our scanner works.

Check a page for free

This section is general information, not legal advice. Laws, deadlines and court decisions change and differ from place to place. Talk to an attorney about your own situation.