Is My Website ADA Compliant? A 2026 Checklist and Free Check

A demand letter arrives. Or a customer emails to say they cannot use your checkout. Or you simply want to know your legal exposure before it becomes a problem. Whatever brought you here, the question is the same: is my website actually ADA compliant? The honest answer is that most websites are not — and most owners have no idea. This guide explains what the ADA requires, what WCAG 2.1 AA looks like in practice, and how to run a real check rather than hoping an overlay widget is keeping you safe.

Does the ADA Apply to Websites?

Yes, with very high confidence. Title III of the Americans with Disabilities Act prohibits discrimination in places of public accommodation. Courts have consistently extended that to business websites, and in 2022 the Department of Justice issued formal guidance confirming that web accessibility is required under the ADA for businesses covered by Title III — restaurants, retailers, hotels, healthcare providers, financial services, and many others.

Over 4,000 federal ADA web-accessibility lawsuits were filed in 2023 alone. The typical target is a small or mid-size business whose site has never been tested. If you sell goods or services online, your site is almost certainly covered.

What Automated Scanners Can and Cannot Find

There is a persistent myth — sold aggressively by overlay vendors — that installing a JavaScript widget makes you compliant. It does not. Overlays have been the subject of class-action lawsuits, FTC scrutiny, and widespread rejection by the disability community. The FTC fined accessiBe $1 million in 2025 for deceptive compliance claims.

Automated scanners, even rigorous ones running two engines (Abledly uses axe-core plus IBM Equal Access), detect roughly 30 to 40 percent of real WCAG failures. They are reliable for:

• Images without alt text
• Color contrast below 4.5:1 (normal text) or 3:1 (large text)
• Form inputs with no associated label
• Pages with no title or a duplicate title
• Missing document language
• Empty buttons or links
• Heading levels that skip (e.g., h1 jumping to h4)

They cannot reliably detect whether a video has accurate captions, whether a complex widget is actually operable by keyboard, whether a screen reader receives meaningful feedback from a custom dropdown, or whether error messages are understandable. Those require human judgment.

The ADA / WCAG 2.1 AA Checklist for 2026

Work through these eight areas. Each maps directly to WCAG 2.1 AA criteria that appear repeatedly in demand letters and court findings.

1. Alt Text on Images

Every meaningful image must have an alt attribute that describes its content or function. Decorative images should have an empty alt attribute (alt="") so screen readers skip them. Images that are links need alt text describing the destination, not the image itself. A scanner catches most missing alt attributes, but only a human can judge whether the text is accurate and useful.

2. Color Contrast

Normal body text needs a contrast ratio of at least 4.5:1 against its background. Large text (18pt or 14pt bold) needs 3:1. This is one of the most common failures — many brand palettes use light gray text on white backgrounds that looks modern but fails the threshold. Automated tools flag this reliably.

3. Form Labels

Every input, select, and textarea must be programmatically associated with a visible label using the for/id pair, aria-label, or aria-labelledby. Placeholder text alone does not count as a label — it disappears when the user starts typing and is not reliably announced by screen readers.

4. Keyboard Operability

A user who cannot use a mouse must be able to reach and activate every interactive element — navigation menus, buttons, forms, modals, accordions, carousels — using only the Tab, Shift+Tab, Enter, Space, and arrow keys. This is almost entirely outside what scanners can test. Sit down and try it on your own site.

5. Visible Focus Indicator

When keyboard users Tab through a page, there must be a clearly visible indicator showing which element has focus. Many sites suppress the browser's default outline with CSS (outline: none or outline: 0) for aesthetic reasons, leaving keyboard users with no way to track where they are. WCAG 2.2 AA strengthens this criterion further.

6. Heading Structure

Headings (h1 through h6) must reflect a logical document outline, not just visual styling. There should be one h1 per page. Subheadings should nest correctly. Screen reader users navigate by heading to skim long pages; a broken heading structure makes this impossible. Scanners catch skipped levels but not semantically wrong headings.

7. Accessible Forms and Error Handling

When a form submission fails validation, the error message must identify which field failed and explain what to fix, in text — not by color alone, and not by an icon with no label. Required fields must be identified to assistive technology, typically with aria-required="true" or the required attribute alongside a visible indicator.

8. Video Captions and Audio Descriptions

Pre-recorded video must have synchronized captions. Auto-generated captions (YouTube, Zoom) often contain errors significant enough to fail the accuracy standard; they need human review and correction. If the video contains meaningful visual information not explained in the audio track, audio descriptions are also required.

How to Actually Check Your Site

A two-step approach gives you a realistic picture. First, run a scan: Abledly runs axe-core and IBM Equal Access in parallel, then applies an AI review layer that catches ambiguous cases and contextual problems the rule engines miss. You get a prioritized issue list with WCAG criterion references and remediation guidance — not a pass/fail score that papers over real problems.

Second, do a manual keyboard walk-through of your most critical user journeys: navigation, search, a product page, the checkout or contact form, and any modal dialogs. Use a screen reader (NVDA on Windows is free; VoiceOver ships with macOS and iOS) to hear what assistive technology actually announces. Even an hour of manual testing will surface issues no scanner can catch.

If you need to demonstrate compliance to a regulator, client, or court, Abledly can also generate a free accessibility statement documenting your conformance posture and known limitations — the EU EAA requires one for covered entities, and it signals good faith under the ADA as well.

What Happens If Your Site Is Not Compliant

The most common path is a demand letter from a plaintiff's attorney, giving you a deadline — often 10 to 30 days — to negotiate a remediation timeline and pay legal fees. Most cases settle. Refusing to engage or making hollow promises (like installing an overlay and claiming compliance) tends to result in litigation. Documented good-faith remediation efforts — a scan history, a remediation log, an accessibility statement — are your best evidence that you are not a willful violator.

The EU Accessibility Act (EAA) adds a separate enforcement layer for businesses selling into the EU market, with member-state regulators enforcing compliance from June 28, 2025 onward. If you have EU customers, the overlap between WCAG 2.1 AA and EN 301 549 means fixing for ADA largely fixes for EAA as well.