What Does ADA Compliance Mean for a Website?
The Americans with Disabilities Act (ADA) is a 1990 civil rights law. It does not mention websites, but the Department of Justice has long taken the position that it covers them. Title II applies to state and local governments, and Title III applies to businesses that are open to the public, known as places of public accommodation.
For Title II, the question is settled: in April 2024 the Department of Justice published a rule adopting WCAG 2.1 Level AA as the technical standard for government websites and mobile apps. For Title III businesses there is no website regulation yet, but courts and settlement agreements almost always use WCAG 2.1 AA as the measure. That is why an ADA compliance check is, in practice, a WCAG 2.1 AA check.
Most website claims start with barriers an automated scan can find: missing alternative text, unlabeled form fields, empty links and low contrast. Finding and fixing those first, then testing key journeys with a keyboard and a screen reader, is the most practical way to reduce risk.
| Law | Americans with Disabilities Act of 1990, Titles II and III |
|---|---|
| Technical benchmark | WCAG 2.1 Level AA |
| Title II rule compliance dates | April 24, 2026 (50,000+ residents), April 26, 2027 (smaller entities) |
| Title III | No web regulation; courts and settlements reference WCAG 2.1 AA |
| Enforced by | Department of Justice and private lawsuits |
Who Needs to Think About ADA Website Compliance?
- State and local government bodies, including cities, counties, public schools, public universities, courts and transit agencies (Title II).
- Businesses open to the public: retailers, restaurants, hotels, healthcare providers, banks, and service businesses with a website (Title III).
- E-commerce sites, which receive a large share of website accessibility claims because checkout and product pages involve forms and images.
- Agencies and developers who build websites for any of the above.
Barriers Most Often Cited in ADA Website Claims
Demand letters and complaints tend to describe the same problems. The first five are ones this checker finds automatically.
Images without alternative text
Product photos, icons and linked images that a screen reader cannot describe (WCAG 1.1.1).
Unlabeled form fields
Search boxes, sign-up and checkout fields that do not announce what to enter (1.3.1, 4.1.2).
Empty links and buttons
Icon-only links such as social media, cart and menu buttons with no accessible name (2.4.4, 4.1.2).
Low color contrast
Light grey text, text over images and placeholder text that is hard to read (1.4.3).
Missing page language and titles
Pages that screen readers pronounce incorrectly or cannot identify (3.1.1, 2.4.2).
Keyboard barriers
Menus, pop-ups and carousels that cannot be reached or closed without a mouse. These need a manual keyboard test.
What This ADA Compliance Checker Tests
WCAG 2.1 Level AA has 50 success criteria. This checker runs 62 automated rules, which test 19 of them. The rest need a person to judge, and they are listed here so nothing is missed. Open a principle to see every criterion.
Perceivable 9 of 20 automated
| Success criterion | Level | How it is tested |
|---|---|---|
| 1.1.1 Non-text Content | A | Automated (7 rules) |
| 1.2.1 Audio-only and Video-only (Prerecorded) | A | Manual review |
| 1.2.2 Captions (Prerecorded) | A | Automated (1 rule) |
| 1.2.3 Audio Description or Media Alternative (Prerecorded) | A | Manual review |
| 1.2.4 Captions (Live) | AA | Manual review |
| 1.2.5 Audio Description (Prerecorded) | AA | Manual review |
| 1.3.1 Info and Relationships | A | Automated (9 rules) |
| 1.3.2 Meaningful Sequence | A | Manual review |
| 1.3.3 Sensory Characteristics | A | Manual review |
| 1.3.4 Orientationnew in 2.1 | AA | Manual review |
| 1.3.5 Identify Input Purposenew in 2.1 | AA | Automated (1 rule) |
| 1.4.1 Use of Color | A | Automated (1 rule) |
| 1.4.2 Audio Control | A | Automated (1 rule) |
| 1.4.3 Contrast (Minimum) | AA | Automated (1 rule) |
| 1.4.4 Resize Text | AA | Automated (1 rule) |
| 1.4.5 Images of Text | AA | Manual review |
| 1.4.10 Reflownew in 2.1 | AA | Manual review |
| 1.4.11 Non-text Contrastnew in 2.1 | AA | Manual review |
| 1.4.12 Text Spacingnew in 2.1 | AA | Automated (1 rule) |
| 1.4.13 Content on Hover or Focusnew in 2.1 | AA | Manual review |
Operable 6 of 17 automated
| Success criterion | Level | How it is tested |
|---|---|---|
| 2.1.1 Keyboard | A | Automated (3 rules) |
| 2.1.2 No Keyboard Trap | A | Manual review |
| 2.1.4 Character Key Shortcutsnew in 2.1 | A | Manual review |
| 2.2.1 Timing Adjustable | A | Automated (1 rule) |
| 2.2.2 Pause, Stop, Hide | A | Automated (2 rules) |
| 2.3.1 Three Flashes or Below Threshold | A | Manual review |
| 2.4.1 Bypass Blocks | A | Automated (1 rule) |
| 2.4.2 Page Titled | A | Automated (1 rule) |
| 2.4.3 Focus Order | A | Manual review |
| 2.4.4 Link Purpose (In Context) | A | Automated (2 rules) |
| 2.4.5 Multiple Ways | AA | Manual review |
| 2.4.6 Headings and Labels | AA | Manual review |
| 2.4.7 Focus Visible | AA | Manual review |
| 2.5.1 Pointer Gesturesnew in 2.1 | A | Manual review |
| 2.5.2 Pointer Cancellationnew in 2.1 | A | Manual review |
| 2.5.3 Label in Namenew in 2.1 | A | Manual review |
| 2.5.4 Motion Actuationnew in 2.1 | A | Manual review |
Understandable 3 of 10 automated
| Success criterion | Level | How it is tested |
|---|---|---|
| 3.1.1 Language of Page | A | Automated (3 rules) |
| 3.1.2 Language of Parts | AA | Automated (1 rule) |
| 3.2.1 On Focus | A | Manual review |
| 3.2.2 On Input | A | Manual review |
| 3.2.3 Consistent Navigation | AA | Manual review |
| 3.2.4 Consistent Identification | AA | Manual review |
| 3.3.1 Error Identification | A | Manual review |
| 3.3.2 Labels or Instructions | A | Automated (1 rule) |
| 3.3.3 Error Suggestion | AA | Manual review |
| 3.3.4 Error Prevention (Legal, Financial, Data) | AA | Manual review |
Robust 1 of 3 automated
| Success criterion | Level | How it is tested |
|---|---|---|
| 4.1.1 Parsing (obsolete in WCAG 2.2) | A | Manual review |
| 4.1.2 Name, Role, Value | A | Automated (28 rules) |
| 4.1.3 Status Messagesnew in 2.1 | AA | Manual review |
What to Check by Hand
Automated rules find the code-level failures. Add these checks to cover what they cannot judge.
- Complete your most important task, such as checkout, booking or a contact form, using only a keyboard.
- Listen to the same task with a screen reader such as NVDA or VoiceOver.
- Check that pop-ups, cookie banners and chat widgets can be closed with the keyboard.
- Confirm that error messages explain what went wrong and how to fix it.
- Check PDFs and documents linked from key pages, which are also covered.
- Publish an accessibility statement with a way to report barriers.
For a step-by-step routine, see Plan manual testing in our Help Center.
How to Use Your Results
- Fix critical and serious issues first, especially on forms, navigation and checkout. Each issue shows the failing code and how to fix it.
- Filter by criterion to hand one type of issue to the right person, for example contrast to design and labels to development.
- Rescan after each fix to confirm it, then run the manual checks above.
- Monitor the whole site. A free scan checks one page. AccessBell Pro monitors up to 500 URLs per domain against WCAG 2.1 Level AA every day and alerts you to new issues.
Related Guides
ADA Compliance Checker Questions
Does the ADA apply to websites?
The Department of Justice says it does. For state and local governments, a 2024 rule sets WCAG 2.1 AA as the standard. For businesses open to the public, there is no specific regulation, but courts have applied the ADA to websites and settlements consistently require WCAG 2.1 AA.
Can a checker make my website ADA compliant?
No tool can on its own. An automated checker finds many of the code-level barriers that appear in claims, quickly and at scale. You still need to fix them, test key journeys manually and keep monitoring as your site changes.
Do accessibility overlays make a site ADA compliant?
Overlay widgets change how a page looks after it loads but do not fix the underlying code, and sites using them have still been sued. Fixing issues at the source is the reliable approach.
What happens if my website is not accessible?
Businesses can receive demand letters or lawsuits. Under federal Title III, plaintiffs can seek an order to fix the site plus attorney fees; some state laws, such as California's Unruh Act, also allow damages. Government bodies can face Department of Justice enforcement.
Sources
- ADA.gov: Guidance on web accessibility and the ADA (opens in a new tab)
- ADA.gov: Fact sheet on the ADA Title II web and mobile rule (opens in a new tab)
- W3C: Web Content Accessibility Guidelines (WCAG) 2.1 (opens in a new tab)
This page explains technical standards and is not legal advice. See our disclaimer.