ADA Website Compliance Costs, Risks, and What to Fix First

Most business owners learn about ADA website compliance one of two ways: a demand letter arrives in the mail, or a lawyer friend mentions lawsuits at dinner. Neither is a calm moment to make good decisions. This article gives you the information before either of those things happens.

The law is real, the exposure is real, and the fix is usually less expensive than the fear. But the fix also requires more than a $49/month plugin, and that distinction matters a great deal.

ADA website compliance requires that your website be usable by people with disabilities, and it applies to nearly all US businesses with a public-facing website under Title III of the Americans with Disabilities Act. The technical standard courts and the DOJ reference is WCAG 2.1 Level AA. A remediation project for a typical small business website runs $2,500 to $15,000 depending on site size and existing code quality, and qualifying small businesses can offset up to $5,000 of that cost through the IRS Disabled Access Credit.

Does the ADA Apply to Your Website?

The short answer is yes, if you operate a business that is open to the public and you have a website.

The ADA’s web guidance from the Department of Justice makes the agency’s position clear: Title III of the Americans with Disabilities Act applies to “all the goods, services, privileges, or activities offered by public accommodations, including those offered on the web.” Public accommodations is the ADA’s term for businesses open to the public, and it covers retail, restaurants, hotels, healthcare providers, banks, and the vast majority of service-based businesses.

Title II, a separate section, covers state and local governments. In April 2024, the DOJ published a final rule under Title II that formally adopts WCAG 2.1 Level AA as the technical compliance standard for government websites, with deadlines running through April 2026 and April 2027 depending on entity size. Private businesses under Title III have no equivalent formal rule yet, but courts have consistently treated WCAG 2.1 Level AA as the operative benchmark when evaluating complaints.

There is one caveat worth naming. Online-only businesses with no physical location occupy a contested legal space. California state and federal courts have ruled that online-only businesses may not be covered by Title III; New York federal courts have generally taken the opposite position. If you have a physical location of any kind, the law almost certainly applies. If you are purely online, your exposure depends significantly on where your customers are and where any lawsuit would be filed.

What WCAG 2.1 Level AA Actually Requires

WCAG stands for Web Content Accessibility Guidelines, published by the W3C Web Accessibility Initiative. The guidelines are organized around four principles: content must be Perceivable, Operable, Understandable, and Robust. Level AA is the middle conformance tier, more demanding than Level A but more achievable than Level AAA.

In practical terms, WCAG 2.1 Level AA means your site must do all of the following:

• Color contrast: Text must have a contrast ratio of at least 4.5:1 against its background (3:1 for large text). Light gray on white fails. Many “modern minimal” design choices fail.
• Alt text: Every meaningful image needs a descriptive text alternative readable by screen readers like JAWS or NVDA. Decorative images need empty alt attributes so screen readers skip them correctly.
• Keyboard navigation: Every interactive element, menus, buttons, forms, modals, must be operable without a mouse. This is where a large percentage of WordPress sites fail because of custom JavaScript components that were never tested with a keyboard.
• Video captions: Any video with meaningful audio content needs synchronized captions. Auto-generated captions from YouTube are not sufficient for compliance; they must be edited for accuracy.
• Accessible forms: Form fields need programmatic labels, not just visual placeholder text. Error messages must identify what went wrong and how to fix it, not just turn a field red.
• Readable structure: Pages need proper heading hierarchy (H1, H2, H3 in logical order), not headings chosen for font size. Screen readers use heading structure to navigate.
• Focus indicators: Keyboard users need a visible focus indicator showing where they are on the page. Many CSS resets strip the browser’s default outline without replacing it.
• No seizure triggers: Nothing should flash more than three times per second.

WCAG 2.2, published in October 2023, added 9 new success criteria beyond what WCAG 2.1 requires, including minimum touch target sizes (24×24 CSS pixels), requirements around accessible authentication (no CAPTCHA puzzles that require visual recognition), and focus-indicator visibility rules. The DOJ’s 2024 Title II rule references WCAG 2.1 specifically, but if you are building new or rebuilding, targeting WCAG 2.2 is the more forward-looking choice.

The Six Most Common Failures on Business Websites

These are the issues that appear most frequently in automated audits and in demand letters, roughly ordered by how often they trigger complaints.

Insufficient color contrast is the single most widespread failure. It shows up in brand color palettes that were approved by designers looking at large monitors in bright offices and never tested by anyone with reduced vision. Running your site’s color pairs through a contrast checker takes 20 minutes and often reveals a dozen failures.

Missing or inadequate alt text is the second most common. This is not just missing alt text on photos; it includes PDF files that are image scans (not searchable text), infographics with no text descriptions, and button images using the image file name as the alt attribute.

Keyboard inaccessibility is the failure most likely to generate a formal complaint, because it makes entire sections of a site unusable. Mega-menus, hamburger menus on mobile, date pickers, modal dialogs, sliders, and carousels are the usual offenders. Each one needs to be openable, navigable, and closeable using only Tab, arrow keys, Enter, and Escape.

Missing video captions is straightforward to audit but time-consuming to fix at scale. If you have a YouTube channel embedded on your site with dozens of videos and auto-generated captions, expect remediation time measured in hours per video.

Inaccessible contact and checkout forms generate disproportionate legal exposure because they gate access to a business’s core service. A form that sighted users navigate by looking at labels is unusable to a screen reader user if those labels are not programmatically connected to their fields via HTML for/id pairs or ARIA attributes.

No skip navigation link is a smaller issue in isolation, but it signals a site that was never audited by someone who uses a keyboard. A skip link lets keyboard users jump past the navigation and directly to main content, avoiding 30+ Tab keystrokes on every page load.

The Overlay Widget Problem

You have probably seen the accessibility widget: a small icon, often a person in a circle, that sits in the corner of a website. Click it, and a panel opens with options to increase font size, change contrast, and adjust the layout. Tools like AccessiBe, UserWay, and AudioEye’s basic tier use this approach.

The honest assessment of these widgets is not complicated: they do not make your site compliant, and they may make your legal exposure worse.

The data from accessibility.works showed that 25% of all accessibility lawsuits in a recent measurement period cited overlay widgets specifically as the problem, not the solution. Plaintiffs’ attorneys have successfully argued that an overlay that disrupts a screen reader’s native functionality is itself an accessibility barrier. Courts have not accepted “we installed a widget” as a defense.

Overlays scan for and surface some issues automatically, primarily simple ones like missing alt text. They cannot fix keyboard navigation problems embedded in JavaScript components, structural heading failures, or form labeling that was done incorrectly in the underlying code. The problems that generate lawsuits are exactly the ones overlays cannot reach.

A tool that tests your site using the axe or WAVE engine is genuinely useful for auditing. An overlay widget installed as a compliance solution is a different thing entirely, and conflating them is a mistake that costs businesses twice: once for the widget subscription and again in legal fees.

What Does ADA Website Compliance Actually Cost?

The range is wide because the variables are significant. Here is an honest breakdown by cost driver.

Work Type	Cost Range	What Drives the Spread
Automated audit + manual review	$1,000 – $5,000	Site size; number of page templates; presence of PDFs and video
Code and design remediation	$2,500 – $25,000	Number of failing components; whether theme code is modifiable; custom JS volume
Document accessibility (PDFs, forms)	$500 – $5,000	Number of documents; whether source files exist
Video captioning	$1-$3 per minute of video	Quality requirements; number of videos
Ongoing monitoring and re-testing	$500 – $3,600/year	Frequency of site updates; new content volume
Overlay widget (does not equal compliance)	$49 – $499/month	Subscription tier

A 10-page brochure site built on a well-structured WordPress theme with no custom JavaScript, no video, and no PDF downloads sits at the low end. Expect a $1,500-$3,500 remediation if issues are found. A 150-page WooCommerce store with custom checkout flows, product videos, and a years-old custom theme built before accessibility was a consideration can run $12,000-$25,000 to remediate properly. The audit comes first; no honest vendor can quote remediation without one.

The tax credit most businesses miss. If your business earned $1 million or less in the prior tax year or had 30 or fewer full-time employees, you likely qualify for the IRS Disabled Access Credit. It covers 50% of eligible accessibility expenditures between $250 and $10,250, for a maximum credit of $5,000 per year, claimable via Form 8826. That credit is renewable each year you incur qualifying expenses. Separately, businesses of any size can deduct up to $15,000 per year for accessibility-related expenditures under the Barrier Removal Tax Deduction (Section 190). Neither credit requires a lawsuit to trigger.

The Legal Exposure Is Specific

Federal website accessibility lawsuits filed under Title III of the ADA reached 3,117 in 2025, a 27% increase from 2024, according to data from Seyfarth Shaw’s ADA Title III practice. New York accounted for 1,021 of those cases, Florida for 961. These are not class action suits brought by advocacy organizations. The majority are demand letters followed by individual lawsuits filed by a small set of repeat plaintiff firms.

A typical settlement for a small business runs $5,000-$10,000 in plaintiff’s attorney fees plus whatever the plaintiff claims as damages, plus the cost of remediating the site as a condition of settlement, plus your own legal fees. The total exposure on a single complaint handled without pushback typically lands between $15,000 and $40,000. Contested litigation is more expensive for everyone.

The pattern of cases is also worth understanding. Plaintiffs’ attorneys use automated scanning tools to identify sites with obvious failures, send demand letters at volume, and settle the majority without going to trial. A site with a passing automated audit score is not guaranteed protection from a human-tested complaint, but it is a substantially weaker target than a site with obvious failures on the first automated pass.

ADA Compliance and SEO: The Overlap Is Real

Several WCAG 2.1 requirements and Core Web Vitals optimizations address exactly the same underlying code behavior.

Alt text on images helps screen readers and gives Google’s image crawler text to index. Proper heading structure aids keyboard navigation and gives Googlebot a page hierarchy to parse. Fast, accessible JavaScript component loading reduces keyboard interaction delay and also reduces Interaction to Next Paint (INP), one of Google’s three Core Web Vitals. Logical DOM order, required so keyboard users experience content in a sensible sequence, also makes a page’s content structure cleaner for crawlers. Accessible form labels, with proper for/id connections, reduce user confusion and reduce bounce from the kinds of form errors that kill conversions.

None of this means Google has an explicit ranking factor for WCAG conformance. It does not, as of any known algorithm documentation. But the engineering disciplines overlap enough that an accessibility audit will surface structural problems that also affect crawlability, page speed, and usability, all of which do affect rankings.

How to Prioritize Remediation If You Cannot Fix Everything at Once

Start with automated testing. Run your site through WAVE (free, browser extension) or Google’s Lighthouse accessibility audit (built into Chrome DevTools). Note: a 100/100 automated score does not mean full compliance; automated tools catch roughly 30-40% of real-world accessibility failures. But they identify the lowest-hanging, highest-frequency issues fast.

Fix critical path issues first. Contact forms, checkout flows, login pages, and navigation are the components most likely to generate complaints because they gate access to your service. Fix those before tackling blog post images.

Audit PDFs separately. Many business websites have downloadable menus, brochures, application forms, or product specs as PDFs. Each one is a separate accessibility document that needs to be either remediated or replaced with accessible HTML.

Test with a real screen reader. NVDA is free for Windows. VoiceOver is built into Mac and iOS. Spend 30 minutes on your own site using only your keyboard and a screen reader before your first vendor conversation. You will understand the problem at a visceral level that no audit report can deliver.

Do not let perfect be the enemy of documented progress. Courts and the DOJ have looked more favorably on businesses that have an accessibility policy, an ongoing remediation plan, and a mechanism for users to report issues, even if the site is not yet fully conformant.

FAQ

Does the ADA apply to my small business website if I have fewer than 15 employees?

The ADA’s Title III provisions on public accommodations, which cover website accessibility for private businesses, do not have an employee threshold. Even a sole proprietor operating a storefront or a service business open to the public is potentially covered. The 15-employee threshold applies to Title I of the ADA, which covers employment discrimination, not web accessibility.

Can I just install a WordPress accessibility plugin and call it done?

No. Plugins like WP Accessibility by Joe Dolson are genuinely useful tools that help you surface and fix specific issues, such as removing title attributes, adding skip links, and improving focus visibility. They are audit aids and targeted fixers. They are not compliance generators. Full WCAG 2.1 Level AA compliance requires hands-on code review, manual keyboard testing, and often theme or template modifications. An automated plugin that claims to make your entire site compliant with one click is making a claim the technology cannot support.

What is the difference between WCAG 2.1 and WCAG 2.2, and which one do I need?

WCAG 2.2, published in October 2023, adds 9 new success criteria to what WCAG 2.1 requires, including minimum touch target sizes, accessible authentication rules, and improved focus indicator requirements. The DOJ’s April 2024 final rule for Title II (government entities) specifically references WCAG 2.1 Level AA. For Title III private businesses, there is no formal rule yet, so WCAG 2.1 AA remains the primary benchmark courts use. If you are building or rebuilding a site today, targeting WCAG 2.2 AA is the more future-proof choice.

Will becoming ADA compliant improve my search rankings?

Not directly. Google has no confirmed ranking signal for WCAG conformance. Indirectly, yes: accessibility fixes overlap with SEO best practices in meaningful ways. Alt text, heading structure, keyboard-accessible JavaScript, and logical DOM order all produce cleaner code that search engines parse more effectively, and they contribute to Core Web Vitals metrics like INP and CLS that do influence rankings.

What does a demand letter actually mean, and do I have to respond?

A demand letter from a plaintiff’s attorney alleging ADA website non-compliance is a precursor to a formal lawsuit. You are not legally required to respond, but ignoring it typically accelerates the filing. Most attorneys recommend responding promptly with an acknowledgment that you are reviewing the matter and remediating any issues. Consulting a lawyer familiar with ADA Title III before responding costs less than a default judgment.

How long does it take to make a website ADA compliant?

For a small site (under 20 pages, one theme, no custom JavaScript), a thorough audit takes 5-10 business days and remediation takes 2-4 weeks. For a larger site, a WooCommerce store with dozens of templates, custom components, and years of content, the audit alone can take 2-3 weeks and remediation can run 6-12 weeks. Scope the audit first; no honest timeline can be quoted without it.

Get a Scoped Accessibility Audit Before a Demand Letter Gets There First

If you are not sure where your site stands, the right first step is a technical audit that maps your actual failures against WCAG 2.1 Level AA, not a plugin installation and a crossed-fingers approach. We scope and price accessibility audits based on your site’s size and tech stack, and we separate the audit from the remediation so you own the findings regardless of who does the work.

Request a scoped accessibility audit at betatech.co/contact-us/