As of April 2026, ADA Title II compliance requirements are now in effect — and ADA Title III lawsuits against private businesses are accelerating. Is your site protected? →
Why Accessibility

Web accessibility isn't optional.
It's a business imperative.

1 in 4 Americans has a disability. ADA lawsuits are surging. And accessibility overlays don't actually fix the problem. Here's what you need to know — and what to do about it.

Who Is Affected

Disability is more common
than most people realize

Disabilities take many forms — visual, hearing, motor, cognitive, and neurological. Many of your current customers are affected right now.

WCAG Explained

Understanding WCAG
and the three conformance levels

WCAG (Web Content Accessibility Guidelines) is the international technical standard for web accessibility, published by the W3C. It defines what "accessible" means — and courts use it as their reference.

A

Level A

Minimum Accessibility

Level A covers the most critical barriers — issues that make a website completely unusable for certain users. Failing Level A means some users simply cannot access your content at all, regardless of their assistive technology or workarounds.

30 success criteria
Images must have alt text (or be marked decorative)
Videos must have captions
All content must be accessible via keyboard
Forms must not rely on color alone to convey errors
Pages must have a meaningful title
AA

Level AA

The Standard That Matters

Level AA is the conformance level required by the ADA Title II rule, the EU Accessibility Act, and Section 508. It's what courts reference in lawsuits, and what most accessibility regulations point to. Achieving WCAG 2.1 AA is the target for virtually every organization.

Level A + 20 additional criteria
Text must meet a 4.5:1 color contrast ratio (3:1 for large text)
Users must be able to resize text to 200% without loss of content
Form inputs must have visible, associated labels
Error messages must identify the specific field and suggest a fix
Navigation must be consistent across pages
Focus indicators must be visible on keyboard-focused elements
AAA

Level AAA

Enhanced Accessibility

Level AAA represents the highest level of accessibility conformance. It goes beyond what most regulations require and is typically not achievable for all content types. Most organizations aim for Level AA, with selective Level AAA improvements where practical.

Level AA + 28 additional criteria
Text contrast ratio of 7:1 (stricter than AA)
Sign language interpretation for all audio content
No session time limits of any kind
Reading level simplified to lower secondary education level
Pronunciation guidance for ambiguous words
Overlays Don't Work

Accessibility widgets are not
a compliance solution

The overlay myth is costing businesses money

Installing an accessibility overlay does not make your website compliant — and courts agree.

Accessibility overlays (such as AccessiBe, UserWay, AudioEye widgets, and similar products) are JavaScript snippets that attempt to patch accessibility problems visually, using automated heuristics. The pitch is compelling: install a script, check a compliance box. The reality is very different.

Courts have consistently ruled that overlays do not constitute meaningful accessibility remediation. The DOJ has stated that automated tools alone cannot ensure compliance. And the disability community — the actual users these tools are supposed to help — widely reports that overlays interfere with their assistive technologies rather than aiding them.

Most critically: over 20% of ADA web accessibility lawsuits target websites that already have an accessibility overlay installed. Having an overlay is not a defense. In some cases, it has been cited as evidence of awareness of the problem without genuine remediation.

✗ The Myth
"An overlay makes my website accessible and protects me from lawsuits."
✓ The Reality
Overlays mask visual symptoms without fixing the underlying source code. Courts have ruled them insufficient, and disabled users report they actively create new barriers.
✗ The Myth
"Automated fixes are good enough — I don't need to change my code."
✓ The Reality
Genuine accessibility requires fixing your actual HTML, CSS, and JavaScript. There's no shortcut — but the path is clear and manageable when you have the right tools.
The Path Forward

De-risk your website with
a clear, actionable plan

Start Today

Know where you stand.
Start getting protected.

Scan your first page free — no credit card, no commitment. Get a real picture of your accessibility risk and a clear path to fix it.