What does “ADA compliant website design” actually mean?
ADA compliant website design means building a site that people with disabilities can use as fully as anyone else. The Americans with Disabilities Act itself does not contain a website checklist for private businesses, so in practice the industry measures accessibility against the Web Content Accessibility Guidelines (WCAG) at Level AA.
The U.S. Department of Justice’s guidance on web accessibility and the ADA, published on March 18, 2022, says the ADA’s requirements apply to all the goods, services, privileges or activities offered by public accommodations, including those offered on the web. It also says businesses can currently choose how they ensure their online programs, services and goods are accessible, and it points to WCAG and the Section 508 Standards as helpful technical resources.
So there is no certificate, badge or registration that makes a site “ADA compliant”. Anyone selling one is overselling. What you can have is a site designed and coded to WCAG AA, tested with the tools disabled people actually use, with known gaps documented and a clear way for visitors to ask for help. That is what we build, and it is also what tends to hold up best when someone asks hard questions later.
Does my business website need to be ADA compliant?
If your business is open to the public, you should assume your website needs to be accessible. DOJ’s position is that Title III covers goods and services offered on the web by public accommodations such as stores, restaurants, hotels, clinics, banks and service providers.
Courts have not all agreed on how far that reaches, especially for businesses that operate only online with no physical location. That uncertainty is a legal question and depends on where you do business and where a claim might be filed, so your own attorney is the right person to assess your exposure.
From a practical point of view, the answer is simpler. Accessible sites work better for everyone: older customers with fading eyesight, people on phones in bright sun, someone with a broken wrist using a keyboard, and search engines reading your structure. State and local government entities, and vendors building for them, have a specific standard under Title II, covered later in this guide. For everyone else, WCAG AA is the sensible target regardless of how the legal debate settles.
WCAG 2.1 or 2.2 AA: which standard should ADA compliant website design follow?
Build to WCAG 2.2 Level AA. It includes everything in WCAG 2.1 AA plus a few newer requirements, so a site meeting 2.2 AA also meets 2.1 AA, the version DOJ adopted for state and local governments.
According to the W3C’s WCAG 2.2 Recommendation, version 2.2 adds nine success criteria and removes one (4.1.1 Parsing, now marked obsolete). The new criteria at Level A and AA are the ones that matter for most businesses:
- 2.4.11 Focus Not Obscured (Minimum), AA: a focused control must not be completely hidden by sticky headers, cookie banners or chat bubbles.
- 2.5.7 Dragging Movements, AA: anything done by dragging, such as a slider, needs a single-pointer alternative.
- 2.5.8 Target Size (Minimum), AA: pointer targets at least 24 by 24 CSS pixels, with some spacing exceptions.
- 3.2.6 Consistent Help, A: help options such as a phone link or chat appear in the same place across pages.
- 3.3.7 Redundant Entry, A: don’t make people retype information they already gave in the same process.
- 3.3.8 Accessible Authentication (Minimum), AA: logins must not rely on memory puzzles or transcription without an alternative, and must allow password managers and paste.
The rest of WCAG is organized under four principles, often shortened to POUR: content must be perceivable, operable and understandable, and the code must work reliably with assistive technology. The build checklist table further down maps the most common Level AA requirements to what we actually do in code.
ADA website lawsuits and demand letters: what are the trends?
Website accessibility claims against US businesses are frequent and rising in some courts. The ADA Title III blog published by the law firm Seyfarth Shaw reported 3,117 website accessibility lawsuits filed in federal court in 2025, a 27% increase over the 2,452 it counted for 2024.
The same report shows filings are concentrated. New York federal courts led with 1,021 lawsuits, Florida followed with 961, and Illinois came third with 585. It counted only four new website accessibility lawsuits in California federal courts, which the authors connect to rulings there on businesses that operate only online. Those figures cover federal court only; claims are also brought in state courts and many disputes start and end with a demand letter that never becomes a lawsuit.
What should a business do with this? Not panic, and not buy a quick fix. Plaintiffs’ firms often use automated scans to find sites with obvious failures such as missing alt text, unlabeled form fields and low contrast, so a site with none of those is simply a less attractive target. If you receive a demand letter, speak to an attorney before changing anything publicly; we can then supply technical findings and fix the code on a clear timeline.
What does an ADA compliant website design build include?
An ADA compliant website design build includes accessible templates and components, correct semantic HTML, sufficient contrast, keyboard operability, text alternatives, accessible forms, captions for media and documented testing. It is a way of building, not a plugin.
We start with the design system. Colors are checked before any page is designed: WCAG requires a contrast ratio of at least 4.5:1 for normal text and 3:1 for large text, and we apply similar thinking to buttons, icons and focus outlines. Type sizes and line spacing are chosen to survive 200% zoom, and layouts reflow to a single column without sideways scrolling.
Then the components: a header with a skip link, a menu that opens with the keyboard and announces its state, buttons that are real buttons, modals that trap and return focus, carousels that pause, accordions that say whether they are open. Pages use one H1, headings in order, and landmarks (header, nav, main, footer) so screen-reader users can jump around. Images get alt text written for their purpose, decorative images get empty alt, and icons with no text get accessible names.
In ADA compliant website design, forms are where accessibility most often costs a business real money, because a customer who cannot complete a booking or checkout simply leaves. Every field needs a visible label, clear instructions and error messages that say what went wrong and how to fix it.
We build forms with labels tied to inputs, required fields marked in text rather than color alone, grouped radio buttons and checkboxes with a legend, autocomplete attributes so browsers and password managers can fill details, and error summaries that move focus to the problem. Nothing times out without warning, and CAPTCHA puzzles are replaced with less hostile spam protection where possible.
Third-party widgets are the hard part. Booking engines, payment forms, chat bubbles and map embeds come from vendors. We test each one with a keyboard and screen reader before choosing it, pick the most accessible option your business can use, and document any remaining vendor issues in your statement with an alternative route, such as a phone number. For stores, product filters, variant pickers and cart updates get special attention; accessible ecommerce builds start at US$750.
For ADA compliant website design, prerecorded video needs accurate captions, audio needs a transcript, and important information should live in accessible HTML pages rather than scanned PDFs. DOJ’s guidance specifically mentions captions for people with hearing disabilities.
Automatic captions from video platforms are a starting point, not the finish: names, product terms and numbers are often wrong. We either correct them or ask you to use a captioning service for important videos. Videos never autoplay with sound, and any moving content that lasts more than a few seconds can be paused. Where a video shows information only visually, such as a demonstration without narration, WCAG AA asks for audio description or an equivalent text alternative.
PDFs are a frequent weak spot, especially menus, price lists, forms and brochures. A scanned PDF is just a picture to a screen reader. We convert the most-used documents into HTML pages, which also helps search engines, and advise on tagging the remaining PDFs properly in the tool that created them.
Do accessibility overlay widgets make a website ADA compliant?
No. An overlay adds a toolbar or script on top of your pages, but it cannot reliably fix inaccessible code underneath, and many screen-reader users find overlays get in the way of the assistive technology they already use.
Overlays are appealing because they promise a one-line install. The problems they target, though, live in your templates: a menu built from generic div elements, a form with placeholder text instead of labels, a checkout that traps keyboard focus. A script running in the browser can guess at fixes, but guesses about what an unlabeled button does are often wrong, and people using screen readers, magnifiers or switch devices usually have their own settings configured already.
We don’t install overlays on the sites we build. If your current site has one, we can remove it as part of a rebuild or remediation, after checking with your attorney if it is part of a settlement or response to a claim. The money usually does more good spent on fixing templates, which fixes every page built from them.
How is ADA compliant website design tested with screen readers?
Test with a mix of automated scans and manual checks, because automated tools find only part of the problems. Manual testing with a keyboard and real screen readers is what shows whether someone can actually complete a task.
Our testing pass for each template and key journey (find a service, book, buy, contact) runs like this. Automated scans with tools such as axe and WAVE catch missing alt attributes, contrast failures and empty links. Then keyboard-only: can we reach, operate and see focus on everything, in a logical order, without getting stuck? Then zoom to 200% and 400% reflow. Then screen readers: NVDA with Firefox or Chrome on Windows, VoiceOver on macOS and iPhone, and TalkBack on Android.
We record what we tested, on which devices and browsers, and what we found and fixed. That record goes to you with the launch. We are developers, not disabled users, so for high-stakes projects we recommend adding usability testing with people with disabilities or a specialist audit firm; we will fix whatever they find.
What should a website accessibility statement say?
In ADA compliant website design, the accessibility statement should say that you are committed to accessibility, which standard you aim for, what known limitations exist and how someone can get help or report a problem. Plain language beats legal boilerplate.
The W3C WAI guidance on accessibility statements lists commitment, the standard applied (such as WCAG 2.2) and contact information as the minimum, and suggests adding known limitations, measures you take, compatibility and technical requirements, and applicable laws. It also advises describing problems in plain terms, such as “videos do not have captions” rather than quoting a success criterion number, and provides a free generator.
We draft the statement from our test notes, list honest known issues with workarounds (for example, “the third-party booking calendar is difficult to use with a screen reader; call us and we will book for you”), give a phone number and email that someone monitors, and date it. Your attorney should review it before publication, since it is a public statement about your business.
How much does ADA compliant website design cost?
With BtechWaleTech, ADA compliant website design starts at US$150 for an accessible site of up to 100 pages, US$750 for an online store and US$300 for large content sites. Accessibility is built into those prices, not billed as an extra.
Elsewhere, quotes vary widely. A new accessible build, a remediation of an existing site, an audit report and an overlay subscription are four different products, and prices are often compared across them as if they were the same. Ask what you will actually receive: working accessible code, a report, or a script.
What moves our quote: the number of unique templates (ten product pages built from one template cost less than ten custom layouts), third-party tools that need replacing, video captioning, PDF conversion, login or account areas and custom interactive features. Retrofitting accessibility into an existing site costs more per page than building it in from the start, which is why a rebuild is often the better value for older sites. See the pricing page for every starting plan.
Choose a fresh ADA compliant website design build when the site is old, slow or built on a theme full of inaccessible components; remediate when the site is fairly modern and the problems are concentrated in a few templates or content issues.
A quick way to decide: we run an automated scan and a thirty-minute keyboard check on your top templates. If most issues come from content (missing alt text, bad headings, low-contrast text in images), remediation is cheaper. If the menu, forms, checkout and page builder itself are the problem, every fix fights the theme, and a rebuild costs less over a year.
Either way, we keep your URLs, content and search rankings in mind. Our website accessibility remediation page covers fixing sites after an audit or demand letter, and website redesign services covers rebuilding without losing traffic. Many businesses combine the two: remediate the urgent journeys now, rebuild on accessible templates next quarter.
ADA compliant website design works on any platform, and any platform can also produce an inaccessible site. What matters is the theme or components, the plugins and apps, and how content editors work.
On WordPress, we avoid heavy page builders that generate deeply nested, unlabeled markup, and use a lean block theme or custom theme with tested components. See WordPress website design for the setup. On Shopify, theme choice is critical, and every app that injects widgets (reviews, pop-ups, upsells) needs a keyboard and screen-reader check before installing; our Shopify developer page goes into detail. Custom static sites built with a framework such as Astro give the most control and speed.
Content editors matter as much as code. After launch, a new blog post with an image and no alt text, or a heading picked for its size rather than its level, reintroduces problems. We hand over a one-page editor guide covering alt text, headings, link text, color use and captions, and set up the editor so the right choices are the easy ones.
Title II deadlines for public entities and the vendors who build for them
State and local government entities have a specific technical standard: DOJ’s April 2024 Title II rule adopted WCAG 2.1 Level AA for their web content and mobile apps. Vendors that build sites or apps for public entities are often asked to meet it too.
In April 2026, DOJ extended the rule’s compliance dates by one year, according to a notice in the Federal Register. Public entities serving populations of 50,000 or more now have until April 26, 2027, and smaller entities and special district governments until April 26, 2028. The substantive standard, WCAG 2.1 AA, did not change.
If you are a contractor, a library, a transit service provider or a company whose product is used by a city or school district, building to WCAG 2.2 AA covers the 2.1 AA requirement with margin. Procurement teams may ask for an accessibility conformance report such as a VPAT; we supply test notes and technical detail that the report author can use, but we do not issue certifications.
Working with an accessibility-focused web team in India from the US
Remote ADA compliant website design runs through WhatsApp and short screen-share calls in your morning, which is our evening. Accessibility testing is naturally remote: we share recordings of keyboard and screen-reader passes so you can see exactly what a disabled visitor would experience.
Quotes are in USD, payment goes by Wise, bank wire or PayPal, and invoices come from India. The written quote lists templates, testing scope, deliverables and ownership, and our terms cover anything else. You keep the domain, hosting and code in your name and add us as users during the build.
Days 1–3
Automated scan and keyboard check of your current site, list of third-party tools, agreement on templates and key journeys to test.
Days 4–9
Accessible design system and templates built; forms and navigation tested with keyboard and screen readers as they are completed.
Days 10–14
Content moved in, captions and PDFs handled, full test pass on desktop and phone, statement drafted for your attorney’s review, launch.
What we won’t do
Give legal advice, respond to demand letters, sign legal certifications or claim a site is lawsuit-proof. We say so in writing before you pay.
Worked example: ADA compliant website design for a furniture store in Ohio
This is a hypothetical example to show the process. Imagine a family-run furniture store in Columbus, Ohio, with a showroom, a catalog of about 300 products and a delivery booking form. Their current theme uses a mega-menu that cannot be opened with a keyboard, product photos have no alt text and the booking form marks required fields in red only.
Our scan and keyboard check show most issues come from the theme, so a rebuild makes sense. The plan: an accessible design system, a keyboard-operable menu, product templates with alt text written from the product data, accessible filters and variant pickers, a checkout tested with VoiceOver on iPhone and NVDA on Windows, a delivery booking form with proper labels and errors, and a statement listing one known limitation (a third-party financing widget) with a phone alternative.
An accessible store like this starts at US$750. The store’s attorney reviews the statement, and two months of free fixes cover issues found as staff add new products. That is the whole scenario; it is illustrative, not a past project.
ADA compliant website design checklist before launch
Run this list before any ADA compliant website design project goes live, ideally with someone who did not build the site.
- Every page reachable and usable with a keyboard; focus always visible and never hidden.
- Text contrast at least 4.5:1 (3:1 for large text); no information conveyed by color alone.
- Every meaningful image has alt text written for its purpose; decorative images have empty alt.
- One H1 per page, headings in order, landmarks present, link text makes sense out of context.
- Forms have labels, instructions, clear errors and allow autocomplete and paste.
- Videos captioned, audio transcribed, nothing autoplays with sound.
- Pages reflow at 400% zoom without sideways scrolling; targets at least 24 by 24 CSS pixels.
- Tested with NVDA, VoiceOver and TalkBack on key journeys; statement published with a working contact.