This guide is educational and isn't legal advice. For advice on your specific situation, talk to a qualified attorney.
What does ADA compliance mean for a website?
ADA compliance for a website means your site doesn't block people with disabilities from the information, goods or services you offer online. The Americans with Disabilities Act (ADA) itself was written in 1990, before the modern web. It doesn't list website rules, but the DOJ has consistently said the ADA applies to what organizations offer online.
In practice, "ADA compliant" is measured against WCAG, a set of testable guidelines published by the World Wide Web Consortium (W3C). WCAG has three levels (A, AA, AAA). Level AA is the one laws, regulations and settlements reference.
Who needs an ADA compliant website?
Two parts of the ADA apply to websites:
Selling into Europe? The European Accessibility Act has applied to many digital products and services, including ecommerce, since June 2025, and it's also assessed against WCAG.
What about B2B companies? Title III covers "places of public accommodation". Whether a website with no physical location counts depends on the court and jurisdiction. The practical answer most legal teams give: follow WCAG 2.1 AA anyway. It reduces risk, widens your audience and usually improves SEO and conversions.
ADA compliant website checklist (WCAG 2.1 AA)
Use this checklist to review any website. It's grouped by WCAG's four principles, with the WCAG success criterion in brackets so your developer can look it up.
Perceivable: can everyone see and hear the content?
- Images have alt text that describes their purpose; decorative images are marked decorative (empty alt). [1.1.1]
- Videos have accurate captions; pre-recorded audio has a transcript. [1.2.1, 1.2.2]
- Important visual-only video information has audio description or a text alternative. [1.2.5]
- Headings, lists and tables use real HTML structure, not just bold or large text. [1.3.1]
- Text contrast is at least 4.5:1 (3:1 for large text). [1.4.3]
- Buttons, form borders and icons have at least 3:1 contrast against their background. [1.4.11]
- Color isn't the only way information is shown, for example errors marked in red only. [1.4.1]
- Text can be zoomed to 200% without breaking the layout, and content reflows at 320px wide without horizontal scrolling. [1.4.4, 1.4.10]
- No images of text where real text would work. [1.4.5]
Operable: can everyone use it?
- Everything works with a keyboard alone: menus, sliders, tabs, modals and forms. [2.1.1]
- No keyboard traps. Users can tab into and out of every component, including pop-ups. [2.1.2]
- A visible focus outline shows where the keyboard is. [2.4.7]
- A "Skip to main content" link lets users bypass repeated navigation. [2.4.1]
- Every page has a unique, descriptive title. [2.4.2]
- Link and button text makes sense on its own ("Download the pricing guide", not "Click here"). [2.4.4]
- Nothing flashes more than 3 times per second. [2.3.1]
- Auto-playing carousels and animations can be paused. [2.2.2]
- Time limits can be extended, for example on session timeouts or forms. [2.2.1]
Understandable: is it clear and predictable?
- The page language is set (
<html lang="en">). [3.1.1] - Every form field has a visible label connected to the input, not only placeholder text. [3.3.2, 1.3.1]
- Form errors are described in text, next to the field, with how to fix them. [3.3.1, 3.3.3]
- Navigation is consistent across pages. [3.2.3]
- Nothing changes unexpectedly when a field gets focus or a value is entered. [3.2.1, 3.2.2]
Robust: does it work with assistive technology?
- Custom components have correct names, roles and states (ARIA used properly, or native HTML elements). [4.1.2]
- Status messages are announced to screen readers, e.g. "Form submitted" or "3 results found". [4.1.3]
Beyond WCAG: what else should you have?
- An accessibility statement page with your standard (WCAG 2.1 AA), known issues and a way to report problems.
- Accessible PDFs and documents (tagged PDFs), or HTML versions of important documents.
- Accessible third-party tools: chat widgets, booking tools, cookie banners and embedded forms.
Aiming for WCAG 2.2? WCAG 2.2 (published in 2023) adds criteria such as a minimum target size for clickable elements, focus that isn't hidden behind sticky headers, and accessible logins without memory puzzles. Meeting 2.2 AA also covers 2.1 AA, so it's a sensible target for new builds.
How do you audit a website for ADA compliance?
Audit a website for ADA compliance by combining automated scans, manual keyboard and screen-reader testing, and a written record of what you found and fixed. Automated tools catch only part of the issues, so a manual review is essential.
- List your key pages and flows: homepage, main templates (service, product, blog post), forms, checkout or booking, login.
- Run an automated scan: WAVE, axe DevTools or Lighthouse on every template. Fix contrast, missing alt text, missing labels and heading errors.
- Test with a keyboard only: unplug the mouse. Can you reach, use and leave every menu, modal, slider and form? Is focus always visible?
- Test with a screen reader: NVDA (Windows, free), VoiceOver (Mac and iOS) or TalkBack (Android). Do images, buttons, links and form errors make sense when read aloud?
- Zoom and reflow: zoom to 200% and view at phone width. Does anything overlap or disappear?
- Check media and documents: captions on videos, and tagged PDFs.
- Check third-party embeds: chat widgets, schedulers, cookie banners.
- Record and prioritize: log each issue with the WCAG criterion, the page and severity. Fix blockers first: anything that stops someone completing a purchase, booking or form.
- Publish an accessibility statement and a contact method for accessibility feedback.
- Re-test after every major change. Accessibility slips every time new pages, components or plugins are added.
Do accessibility overlays make a website ADA compliant?
No. Accessibility overlays (JavaScript widgets that add a toolbar or claim to "fix" a site automatically) don't make a website ADA compliant on their own. They can't reliably fix underlying problems such as missing form labels, keyboard traps or unclear link text.
In April 2025 the US Federal Trade Commission approved a final order requiring overlay vendor accessiBe to pay $1 million. The FTC's complaint said accessiBe had made deceptive claims that its AI tool could make websites compliant with accessibility guidelines. Businesses using overlays have also continued to face accessibility lawsuits.
The reliable route is to fix the site itself: semantic HTML, correct labels, keyboard support, sufficient contrast, and testing.
What happens if your website isn't ADA compliant?
If your website isn't accessible, you face three kinds of risk:
- Legal risk. Businesses can receive demand letters or lawsuits under Title III. Some states add their own laws, such as California's Unruh Act. For public entities, the DOJ can enforce the Title II rule once the compliance dates arrive.
- Lost customers. People who can't use your checkout, booking or contact form go elsewhere.
- Weaker SEO and conversions. Many accessibility practices, such as clear headings, descriptive links, alt text, fast and clean markup and readable forms, also help search engines and all users.
Fixing accessibility during a build or redesign costs far less than retrofitting it after a complaint.
How much does it cost to make a website ADA compliant?
The cost of making a website ADA compliant depends on the size of the site and how it was built. An audit of a small site with a few templates is a modest one-time cost. Remediating a large site with custom components, PDFs and third-party tools is a bigger project.
The cheapest approach is to build accessibility in from the start: accessible templates, components and colors mean every new page inherits compliance. Retrofitting an older site is often combined with a redesign, because inaccessible templates usually need rebuilding anyway (see signs you need a website redesign).
How do you make your website ADA compliant on your platform?
Accessibility depends far more on how a site is built than on the platform. Some platform notes:
- Webflow: gives full control over semantic HTML, alt text, ARIA attributes and focus states, and includes a built-in accessibility audit panel. Interactions and custom components need manual keyboard testing. See is Webflow ADA compliant? and our Webflow accessibility guide.
- WordPress: depends heavily on the theme and plugins. Choose accessibility-ready themes and test every plugin that adds front-end features.
- Shopify, Squarespace, Wix: themes vary widely. Test the checkout and forms, and edit alt text and headings on every page.
At theCSS Agency, every Webflow site we build ships with WCAG checks, cross-browser QA and accessibility-first markup, so accessibility is part of the build rather than a fix afterwards. See our Webflow development agency services, or if your current site needs a rebuild, our website redesign services. Book a call to talk it through.
FAQs
1. What makes a website ADA compliant?
A website is considered ADA compliant when people with disabilities can perceive, operate, understand and use it. That means it meets the Web Content Accessibility Guidelines (WCAG) 2.1 Level AA, the standard referenced by the Department of Justice's Title II rule and most accessibility settlements.
2. Is ADA website compliance required for private businesses?
ADA Title III applies to businesses open to the public, and the Department of Justice says their online goods and services must be accessible. There is no fixed technical rule or deadline for businesses, but WCAG 2.1 AA is the standard courts and settlements usually point to.
3. What is the ADA website compliance deadline?
Under the Department of Justice's Title II rule, state and local governments serving 50,000 or more people must meet WCAG 2.1 AA by April 26, 2027. Smaller governments and special districts must comply by April 26, 2028. These dates come from the DOJ's April 20, 2026 Interim Final Rule. Private businesses have no fixed deadline.
4. What WCAG level is required for ADA compliance?
WCAG 2.1 Level AA is the level required by the DOJ's Title II rule and the benchmark most often used for ADA compliance. WCAG 2.2 AA is newer and includes all of 2.1 AA, so it's a good target for new websites.
5. Do accessibility overlays make a website ADA compliant?
No. Accessibility overlay widgets can't reliably fix underlying code problems like missing labels or keyboard traps. In 2025 the FTC ordered overlay vendor accessiBe to pay $1 million over deceptive claims that its tool could make websites compliant.
6. How do I check if my website is ADA compliant?
Check a website for ADA compliance by running automated scans (WAVE, axe or Lighthouse), then testing manually with only a keyboard and with a screen reader such as NVDA or VoiceOver. Also test zoom and mobile reflow, check captions and PDFs, and log every issue against its WCAG criterion.
7. What is an accessibility statement?
An accessibility statement is a page on your website that states the accessibility standard you aim to meet (for example WCAG 2.1 AA), any known limitations, and how users can report accessibility problems or request help.
.jpg)
