How do you make your website ADA compliant?

An ADA compliant website is one that people with disabilities can use without help, and in practice that means meeting WCAG 2.2 Level AA. Add text alternatives to images, caption videos, reach a 4.5:1 text contrast ratio, make every control work by keyboard and label every form field. Then test with a screen reader, fix issues template by template, publish an accessibility statement and retest with every release.

The ADA names no technical standard for private business websites, which is why owners keep asking what compliance means. The Department of Justice says the law covers what a business offers online, and plaintiffs test sites against WCAG. In 2025, 3,117 website accessibility lawsuits were filed in federal court. The audience is large too. The CDC reports that more than 1 in 4 US adults have some type of disability, led by cognition at 13.9 percent and mobility at 12.2 percent.

This article is general information, not legal or tax advice. If you have received a demand letter or a complaint, speak with an attorney licensed in your state before you reply to it or change the site.

On this page

• What the ADA requires from a business website
• Which ADA website rules and deadlines apply to you
• What changes if you sell to the EU or to government buyers
• What WCAG 2.2 Level AA requires
• What is new in WCAG 2.2
• The six errors found on most websites
• How to make your website ADA compliant, step by step
• Why checkout and third-party widgets need extra testing
• How long ADA remediation takes: a worked example
• What drives the cost of ADA remediation
• Why an accessibility overlay will not fix it
• Where ADA website lawsuits are filed
• Does ADA compliance help SEO and page speed
• How to keep an ADA compliant website compliant after launch

What the ADA requires from a business website

Title III of the ADA covers businesses open to the public, such as stores, restaurants, banks, hotels, clinics and law firms. The Department of Justice issued its guidance on web accessibility and the ADA on March 18, 2022. It states that the law applies to all goods, services and activities a public accommodation offers, including those offered on the web.

The same guidance confirms there is no Title III regulation with detailed web standards. Businesses "have flexibility in how they comply," and the Department names WCAG and the Section 508 standards as helpful references. Flexibility is no exemption. The guidance lists the barriers that draw complaints:

• Poor color contrast, and color used as the only way to convey information.
• Images without alt text.
• Videos without captions.
• Online forms without labels, clear instructions or error indicators.
• Pages that only work with a mouse.

Two other parts of the law reach websites. Title I covers employers with 15 or more employees, so an online job application has to work for disabled applicants. Title II covers state and local governments and now has a fixed technical rule with dates. Title III has no size threshold, so a five-person business open to the public is covered the same way a national chain is.

For a private business, that leaves no grace period. The law is in force today. WCAG 2.2 Level AA is the safest target, because a plaintiff's expert, a settlement agreement or a government buyer will most likely measure your site against it.

Which ADA website rules and deadlines apply to you

Deadlines depend on who you are, and the government dates moved in 2026. The 2024 Title II rule set WCAG 2.1 Level AA for state and local government websites and mobile apps. An interim final rule published on April 20, 2026 (91 FR 20902) pushed each compliance date back one year. The Department says the amendments do not alter any other provision of the 2024 rule.

What changes if you sell to the EU or to government buyers

The EU row catches US stores off guard. The European Accessibility Act lists e-commerce services among the services it covers. It exempts service microenterprises, defined as fewer than 10 staff with annual turnover or a balance sheet of no more than EUR 2 million. A US brand with 25 employees selling to shoppers in Germany or France likely falls inside the scope.

Government buyers create a second pull. The ADA.gov first steps page for the Title II rule says public entities stay responsible for content that vendors and contractors provide on their behalf. A city, school district or public hospital buying a portal, a booking tool or a website will likely write WCAG 2.1 AA into the contract. A vendor that can't show conformance risks losing the bid.

What WCAG 2.2 Level AA requires

WCAG, the Web Content Accessibility Guidelines published by the W3C, groups its success criteria into Levels A, AA and AAA. They sit under four principles: content must be perceivable, operable and understandable, and it must work with assistive technology. Level AA includes everything in Level A, and it is the level the Title II rule names.

The W3C advises against requiring Level AAA as a policy for whole sites, because some content cannot meet every AAA criterion. For a business site, the older Level A and AA rules do most of the work:

• Text contrast of at least 4.5:1, or 3:1 for large text.
• Contrast of 3:1 for icons, form borders and focus indicators against their background.
• Text that resizes to 200 percent without breaking the page.
• Captions on prerecorded video, a Level A requirement.
• Every function usable from a keyboard, also Level A.

Use WCAG 2.2 for any build or redesign in 2026. It keeps the 2.1 criteria, so a site built to 2.2 AA also clears the 2.1 AA bar in the government rule.

What is new in WCAG 2.2

WCAG 2.2 became a W3C Recommendation on October 5, 2023, and the current text is dated December 12, 2024. It retires 4.1.1 Parsing and adds nine criteria. Six of the nine sit at Level A or AA, and each one maps to a common pattern on business sites.

The six errors found on most websites

WebAIM's 2026 Million report scanned the home pages of the top one million websites. It found detectable WCAG 2 failures on 95.9 percent of them, with an average of 56.1 errors per page. Six error types made up 96 percent of everything detected, so they belong at the top of any fix list.

Automated scanners such as WAVE, axe and Lighthouse catch these six well. They can't judge whether alt text is accurate or whether focus moves in a sensible order. They also can't tell you whether a screen reader user can finish checkout. Treat a clean scan as the start of testing, then check by hand everything a scan cannot judge.

How to make your website ADA compliant, step by step

Work from the tasks customers complete, then the templates, then the content. That order puts the highest legal and revenue risk first. It also fixes the most pages per hour of developer time.

1. List your templates (home, category, product, article, contact) and the tasks a customer must finish, such as booking, checkout, login, account creation and the contact form.
2. Run an automated scan on one page per template and on every page inside each task.
3. Complete every task with the keyboard alone, using Tab, Shift+Tab, Enter, Space, the arrow keys and Escape. Focus must stay visible and must never get stuck in a menu or pop-up.
4. Repeat each task with a screen reader: NVDA or JAWS on Windows, VoiceOver on Mac and iPhone, TalkBack on Android.
5. Zoom the browser to 200 percent and test a 320 pixel wide view. Text should grow and content should reflow without sideways scrolling.
6. Fix issues in templates and shared components first, then in page content.
7. Check third-party pieces: booking widgets, chat, payment forms, review apps, maps and video players. Ask each vendor for its Accessibility Conformance Report, built on the VPAT template.
8. Fix documents and media. Caption videos, add transcripts for audio and either tag PDFs for screen readers or turn them into HTML pages.
9. Publish an accessibility statement that names the standard you target, lists known gaps and gives a phone number and email for anyone who hits a barrier.
10. Add accessibility checks to your release process and train the people who publish content.

Why checkout and third-party widgets need extra testing

Do not skip step 7. A complaint names the business that runs the site, not the plugin vendor, so an inaccessible booking or payment widget is your problem in practice.

New features carry the same risk. If an AI assistant is on the roadmap, put keyboard and screen reader support in the scope when you price an AI chatbot build. A chat window that traps keyboard focus fails 2.1.2 No Keyboard Trap. A chat bubble that covers the focused link fails 2.4.11 on every page where the widget loads.

Checkout deserves the most testing time. Unlabeled fields, errors shown only in red and a payment step a keyboard cannot reach all lock out disabled buyers. The same friction drives other shoppers away, which is why accessibility fixes overlap with the steps in the guide on how to reduce cart abandonment.

How long ADA remediation takes: a worked example

Say a home goods store in Florida runs on Shopify. It has 400 product pages, 25 collection pages, 40 blog posts and a four-step checkout. Its first automated scan flags 12,000 issues, which looks like months of work. Grouped by source, the picture changes. The header, footer and product template load on every product page, so one unlabeled search field counts 400 times and takes one fix.

In this example, 10,800 of the 12,000 issues trace back to five shared files: the header, footer, product template, collection template and cart drawer. Fixing those five files clears 90 percent of the list in one developer sprint. The other 1,200 issues sit in content, mostly 900 product images without alt text and blog posts with skipped heading levels. That work belongs to whoever manages the catalog.

Plan the content backlog at a fixed rate. At 100 product images a week, the 900-image backlog clears in nine weeks. New products launch with alt text from day one.

What drives the cost of ADA remediation

Effort tracks templates and custom components, not page count. A custom checkout, a JavaScript filter menu or an in-house booking tool takes more developer time than 400 product pages on one template. Platform choice matters less than theme quality. The trade-offs in the Shopify vs WooCommerce comparison apply here too, since both platforms ship accessible and inaccessible themes.

If the current theme fails on contrast, focus and target size across the site, a redesign can cost less than patching it. The guide to small business website costs shows how to budget a rebuild.

Some of the spend may come back as a tax credit. The Disabled Access Credit described on ADA.gov covers businesses with 30 or fewer employees or revenue of $1 million or less. They can claim half of eligible access spending between $250 and $10,250, up to $5,000. The examples ADA.gov gives are physical and service changes, so ask your tax adviser whether website remediation qualifies before you count on it.

Why an accessibility overlay will not fix it

Overlays are scripts that add a toolbar and try to repair a site inside the browser. They are sold as a one-line fix, and a federal regulator has already tested that claim. On April 22, 2025, the FTC approved a final order requiring accessiBe to pay $1 million. The FTC said the claim that its accessWidget can make any website WCAG compliant was false, misleading or unsubstantiated. The order bars that claim without evidence to back it.

The order doesn't ban overlays, and a toolbar that lets visitors enlarge text harms no one. The problem is reliance. An overlay can't write accurate alt text for a product photo or caption a video. It can't rebuild a checkout that traps keyboard focus either, so the code still fails the tests a plaintiff runs. Put that budget into fixing the templates instead.

Where ADA website lawsuits are filed

Federal website accessibility lawsuits rose to 3,117 in 2025, up 27 percent from 2,452 in 2024, according to the annual count by the Seyfarth Shaw ADA Title III team. Filings had fallen in 2023 and 2024 before the rebound. The totals leave out state court cases and demand letters, so the real number is higher.

New York leads because federal judges there have been more favorable to plaintiffs suing online-only businesses. Stricter standing rules lately have pushed many filers into New York and New Jersey state courts.

California's count of four is misleading. Seyfarth attributes it to federal and state appeals courts there concluding that online-only businesses are not covered by the ADA. The federal tally also excludes state court claims under the Unruh Act, where Civil Code section 52 sets damages of no less than $4,000 for each offense.

A business selling to customers in New York, Florida or Illinois, or running a physical location in California, should treat accessibility as current legal exposure rather than a future project.

Does ADA compliance help SEO and page speed

It helps in practical ways. Alt text, captions, transcripts and a clean heading structure give search engines and AI answer engines more text to read. Descriptive link text and real headings make each page easier for a crawler to parse, the same way they help a screen reader user. Removing a heavy overlay script also cuts JavaScript that slows the page and can hurt your Core Web Vitals.

How to keep an ADA compliant website compliant after launch

Accessibility breaks the same way it gets fixed, one release at a time. A hero banner with white text on a pale photo puts errors back on pages that passed last quarter. So does a marketing pop-up without a close button, or a product video uploaded without captions.

• Scan every template before each release and block releases that add new errors.
• Repeat keyboard and screen reader tests of checkout, login, booking and contact forms every quarter.
• Give content editors a one-page rule sheet: alt text on meaningful images, headings in order, link text that says where the link goes and captions on every video.
• Review third-party scripts whenever a vendor ships an update.
• Keep a log of fixes, test dates and user reports, which gives your attorney a dated record if a demand letter arrives.

Start this week with a keyboard-only run through your checkout, booking or contact form. If you can't finish it without a mouse, that is the first fix. The website design and development team at Techno Mantra audits sites against WCAG 2.2 AA and fixes theme and template code at the source. The team also sets up release checks so new pages stay compliant. Send your URL and the tasks your customers complete through the contact page or to info@technomantraa.com. Every inquiry gets a reply within one business day.