Web Accessibility (ADA Compliance): Complete Guide for US Websites in 2026

Web accessibility is no longer optional for US businesses. With ADA website lawsuits reaching record numbers and regulatory scrutiny increasing, ensuring your website is accessible to people with disabilities is both a legal imperative and a business opportunity. An accessible website opens your business to the estimated 61 million Americans living with disabilities, improves your search engine rankings, and enhances the user experience for all visitors. This comprehensive guide covers everything you need to know about web accessibility and ADA compliance for US websites in 2026. —

What Is Web Accessibility and Why It Matters

Web accessibility means that websites, tools, and technologies are designed and developed so that people with disabilities can use them. More specifically, people can perceive, understand, navigate, and interact with the web, and they can contribute to the web. Web accessibility encompasses all disabilities that affect access to the web, including auditory, cognitive, neurological, physical, speech, and visual disabilities. The legal foundation for web accessibility in the United States is the Americans with Disabilities Act (ADA), signed into law in 1990. While the ADA was enacted before the modern internet existed, federal courts have increasingly interpreted it to apply to websites. Title III of the ADA prohibits discrimination on the basis of disability in places of public accommodation, and courts have ruled that websites connected to physical businesses or offering goods and services to the public qualify as places of public accommodation. Section 508 of the Rehabilitation Act is another key regulation that requires federal agencies and organizations receiving federal funding to make their electronic and information technology accessible. While Section 508 applies primarily to the federal sector, its standards have influenced the broader accessibility landscape and are often used as a benchmark for private sector compliance. The business case for accessibility extends beyond legal compliance. Approximately 26% of adults in the United States have some form of disability, representing a significant market that cannot be ignored. Accessible websites also tend to perform better in search engines, as many accessibility best practices overlap with SEO best practices. Companies like Digimau understand that accessibility is not just about compliance; it is about creating better experiences for all users.

ADA Website Lawsuits in the US

The volume of ADA website lawsuits has grown dramatically over the past decade, making web accessibility a critical risk management issue for US businesses.

Lawsuit Trends and Data

According to data from UsableNet, which tracks ADA digital accessibility lawsuits, there were over 4,500 federal ADA website lawsuits filed in 2024, and the trend continues upward in 2026. This represents a more than 300% increase from 2018. The vast majority of these lawsuits are filed in federal courts in New York, California, and Florida, but cases have been filed in virtually every state. The average settlement for an ADA website lawsuit ranges from $10,000 to $100,000, depending on the size of the business, the severity of the accessibility barriers, and the jurisdiction. Legal fees can add $10,000 to $50,000 or more to the total cost. Beyond the direct financial impact, lawsuits can damage brand reputation and require significant time and resources to resolve.

Industries Most Targeted

Certain industries face a disproportionate share of ADA website lawsuits. Retail and e-commerce businesses are the most frequently targeted, accounting for approximately 60% of all cases. This makes sense because retail websites are heavily transactional, and accessibility barriers directly prevent purchases. Other commonly targeted industries include restaurants and food service (15%), hospitality and travel (8%), healthcare (5%), financial services (4%), and education (3%). However, businesses in every industry have been sued, and no sector is immune.

Notable Cases

Several high-profile cases have shaped the ADA website compliance landscape. The Domino’s Pizza v. Guillermo Robles case (2019) was a landmark ruling by the Ninth Circuit Court of Appeals, which held that the ADA applies to websites and that the lack of specific DOJ regulations for web accessibility does not shield businesses from liability. The Winn-Dixie v. Juan Carlos Gil case (2017) was one of the first to find a retailer’s website in violation of the ADA, resulting in an order to make the website accessible. The Harvard and MIT lawsuits (2015 and 2020) resulted in settlements requiring these institutions to make their online content, including video, accessible to people with disabilities.

WCAG 2.2 Guidelines Overview

The Web Content Accessibility Guidelines (WCAG), developed by the World Wide Web Consortium (W3C), are the internationally recognized standards for web accessibility. WCAG 2.2, published in October 2023, is the latest version and is increasingly referenced in legal proceedings and settlement agreements.

The Four Principles (POUR)

WCAG is organized around four foundational principles, often referred to by the acronym POUR. Perceivable: Information and user interface components must be presentable to users in ways they can perceive. This means providing text alternatives for non-text content, captions for audio content, and content that can be presented in different ways without losing meaning. Operable: User interface components and navigation must be operable. This means all functionality must be available from a keyboard, users must have enough time to read and use content, content must not cause seizures, and users must be able to navigate and find content. Understandable: Information and operation of user interfaces must be understandable. This means text must be readable and understandable, content must behave in predictable ways, and users must be helped to avoid and correct mistakes. Robust: Content must be robust enough to be interpreted reliably by a wide variety of user agents, including assistive technologies. This means content must be compatible with current and future technologies.

Conformance Levels

WCAG defines three levels of conformance. Level A is the minimum level of accessibility and addresses the most basic and critical accessibility issues. Level AA is the standard level targeted by most organizations and is referenced in most legal proceedings. It includes all Level A criteria plus additional requirements that address a wider range of disabilities. Level AAA is the highest level of conformance and includes criteria that address the needs of users with the most severe disabilities. Full Level AAA conformance is rarely achievable for all content and is not typically required by law. For ADA compliance, WCAG 2.2 Level AA is the practical standard that businesses should target. Most settlement agreements, consent decrees, and legal opinions reference Level AA conformance as the benchmark for compliance.

Common Accessibility Issues

Understanding the most common accessibility issues helps you prioritize your remediation efforts and avoid the problems that most frequently lead to lawsuits.

Missing or Inappropriate Alt Text

Alt text (alternative text) provides a text description of images for screen reader users and is displayed when images fail to load. Missing alt text is the single most common accessibility issue found on websites. Every informative image should have descriptive alt text that conveys the meaning and purpose of the image. Decorative images should have empty alt attributes (alt=””) so screen readers skip them.

Keyboard Navigation Barriers

Many websites have elements that cannot be accessed or operated using a keyboard alone. This includes dropdown menus, modal dialogs, carousels, form controls, and interactive widgets. All functionality must be accessible via keyboard, with a visible focus indicator that shows users which element is currently selected. The tab order should follow a logical sequence that matches the visual layout.

Insufficient Color Contrast

WCAG requires a minimum contrast ratio of 4.5:1 for normal text and 3:1 for large text (18px or 14px bold) between text and its background. Many websites fail this requirement, particularly for body text, form labels, placeholder text, and text displayed over images. Low contrast makes content difficult or impossible to read for users with color vision deficiencies, low vision, or who are viewing the screen in bright light.

Missing Form Labels and Error Messages

Forms that lack proper labels, instructions, and error messages are a significant accessibility barrier. Every form input must have a visible label that is programmatically associated with the input field. Error messages must be specific and clear, identifying the error and explaining how to fix it. Form validation should provide real-time feedback and not rely solely on visual indicators like color changes.

Missing Focus Indicators

When users navigate a website using a keyboard, a visible focus indicator (typically an outline or highlight) shows which element currently has keyboard focus. Many websites remove or style over the default focus indicator for aesthetic reasons, making it impossible for keyboard users to track their position on the page. Focus indicators must be visible and have sufficient contrast against the background.

Missing Video Captions and Audio Descriptions

Videos without captions exclude users who are deaf or hard of hearing. Auto-generated captions are not sufficient because they often contain errors. Captions must accurately represent the audio content, including dialogue, sound effects, and music. Audio descriptions provide additional narration for users who are blind, describing visual content that is not conveyed through dialogue.

Improper Heading Structure

Heading elements (h1 through h6) provide a hierarchical structure that helps screen reader users navigate content. Many websites skip heading levels, use headings for visual styling rather than structure, or lack headings entirely. Pages should have a single h1 element followed by properly nested subheadings that create a logical content outline.

How to Make Your Website Accessible

Making your website accessible is a structured process that involves auditing, prioritizing, remediating, and maintaining accessibility over time.

Step 1: Conduct an Accessibility Audit

Start with a comprehensive accessibility audit that identifies all current barriers. This should include automated scanning using tools like Lighthouse, axe, or WAVE to catch common technical issues, manual testing using keyboard navigation and screen readers, and a professional manual audit by an accessibility specialist who can identify issues that automated tools cannot detect. The audit should produce a prioritized list of issues with severity ratings and specific remediation recommendations.

Step 2: Establish Remediation Priorities

Not all accessibility issues are equal. Prioritize remediation based on impact and effort. Critical issues that prevent users from completing key tasks (purchasing, filling out forms, accessing content) should be addressed first. Issues that affect a large number of users should be prioritized over those that affect a small subset. Quick wins that require minimal effort should be addressed early to build momentum.

Step 3: Implement Fixes

Remediation involves both technical code changes and content updates. Common code-level fixes include adding ARIA attributes, improving keyboard navigation, adjusting color contrast, adding focus indicators, and implementing proper semantic HTML. Content-level fixes include adding alt text to images, writing captions for videos, restructuring headings, and rewriting link text to be descriptive.

Step 4: Test and Verify

After implementing fixes, re-test using the same combination of automated tools, manual testing, and assistive technology testing used in the initial audit. Document all changes and test results to demonstrate your compliance efforts. Consider engaging a third-party accessibility auditor to verify your remediation work.

Step 5: Establish Ongoing Monitoring

Accessibility is not a one-time project; it requires ongoing attention. New content, features, and updates can introduce accessibility barriers. Establish processes for ongoing monitoring, including pre-launch accessibility reviews for new features, regular automated scanning of your website, periodic manual audits (quarterly or semi-annually), and accessibility training for your content creators and developers.

Web Accessibility Tools and Platforms

A wide range of tools and platforms are available to help businesses achieve and maintain web accessibility. No single tool catches all issues, so a multi-tool approach is essential.

Automated Testing Tools

Google Lighthouse is a free, built-in tool in Chrome DevTools that provides an accessibility score and identifies common issues. axe by Deque is a leading accessibility testing library that integrates with Chrome, Firefox, and popular development frameworks. WAVE (Web Accessibility Evaluation Tool) by WebAIM provides visual feedback about accessibility issues directly on your web pages. Pa11y is an open-source command-line tool for automated accessibility testing of web pages. These tools catch approximately 30% to 40% of accessibility issues, as they can only detect programmatic barriers, not semantic or usability problems.

Overlay and Widget Solutions

Accessibility overlays like accessiBe, AudioEye, UserWay, and Equality Cloud are JavaScript-based tools that can be installed on your website to address some common accessibility issues. These tools typically provide a widget with options for text sizing, color contrast, font changes, and screen reader compatibility. Pricing ranges from $49 to $590 per month depending on features and website traffic. However, it is important to understand the limitations of overlays. The Department of Justice and accessibility advocacy groups have noted that overlays cannot fix underlying code problems, and they do not provide full WCAG compliance. They should be used as a supplement to, not a replacement for, code-level remediation.

Manual Testing with Screen Readers

Testing with actual screen readers is essential for understanding the user experience of people who are blind or have low vision. NVDA (NonVisual Desktop Access) is a free, open-source screen reader for Windows that is widely used for testing. JAWS (Job Access With Speech) by Freedom Scientific is the most commonly used commercial screen reader, with a paid license. VoiceOver is built into all Apple devices (macOS and iOS) and is free to use. ChromeVox is a built-in screen reader for ChromeOS. Test your website with at least two different screen readers to account for differences in how they interpret web content.

Accessibility Testing Methods

Effective accessibility testing requires a combination of automated, manual, and user testing methods.

Automated Testing

Automated tools scan your website’s code for technical accessibility issues. They are fast, inexpensive, and can be integrated into your development process. However, automated tools can only detect about 30% to 40% of WCAG success criteria. They cannot assess whether alt text is meaningful, whether heading structure makes sense, or whether the overall user experience is accessible. Automated testing should be your starting point, not your ending point.

Manual Testing

Manual testing involves human evaluators navigating your website using different methods and assistive technologies. Key manual tests include keyboard-only navigation (can all features be accessed and operated without a mouse?), screen reader testing (is content read in the correct order? Are images properly described?), zoom testing (does the website remain usable at 200% and 400% zoom?), color contrast verification (using tools like Colour Contrast Analyser), and mobile accessibility testing (with VoiceOver on iOS and TalkBack on Android).

User Testing with Disabled Individuals

The most effective way to evaluate accessibility is to test with actual users who have disabilities. This includes users who are blind or have low vision, users who are deaf or hard of hearing, users with motor impairments, and users with cognitive disabilities. User testing reveals real-world barriers that automated and manual testing cannot identify. Organizations like Fable, Level Access, and the National Federation of the Blind offer user testing services with people who have disabilities.

Accessibility for Specific Disabilities

Understanding how different disabilities affect web browsing helps you design more inclusive experiences.

Visual Disabilities

Users who are blind rely on screen readers to access web content. They navigate by headings, links, landmarks, and keyboard shortcuts. Proper semantic HTML, ARIA labels, and logical reading order are critical for screen reader users. Users with low vision may use screen magnifiers, browser zoom, or high-contrast modes. Sufficient color contrast, resizable text, and responsive design are essential. Users with color vision deficiencies (color blindness) need information conveyed through means other than color alone, such as text labels, patterns, or icons.

Auditory Disabilities

Users who are deaf or hard of hearing need captions for video content, transcripts for audio content, and visual alternatives for audio cues. Auto-play media should have visible controls, and any content conveyed through sound should have a visual equivalent.

Motor Disabilities

Users with motor impairments may have difficulty using a mouse and rely on keyboard navigation, voice control, switch devices, or eye tracking. Large click targets (minimum 44×44 pixels), generous spacing between interactive elements, and keyboard-accessible functionality are essential. Avoid features that require precise mouse movements, drag-and-drop interactions without keyboard alternatives, or time-limited actions without the ability to extend the time.

Cognitive Disabilities

Users with cognitive disabilities include those with dyslexia, ADHD, autism spectrum disorders, memory impairments, and intellectual disabilities. Clear and simple language, consistent navigation, predictable behavior, error prevention and recovery, and the ability to control timing and animation are important for these users. Avoid complex layouts, auto-playing content, distracting animations, and content that requires extensive reading comprehension.

Accessible Web Design Best Practices

Accessible design is not about limiting creativity; it is about designing with empathy and inclusion. These best practices ensure your designs are both beautiful and accessible.

Color and Contrast

Use color strategically and ensure all text meets minimum contrast requirements. Never rely on color alone to convey information; use text, icons, or patterns as supplementary indicators. Test your color palette using tools like the WebAIM Contrast Checker to verify that all text and interactive elements meet WCAG AA contrast ratios. Provide a high-contrast mode or allow users to customize colors if possible.

Typography

Choose fonts that are easy to read at various sizes. Sans-serif fonts like Arial, Helvetica, Open Sans, and Roboto are generally preferred for body text. Maintain a minimum font size of 16px for body text and use relative units (rem, em) rather than fixed units (px) to support user-defined font sizes. Ensure adequate line height (1.5 times the font size for body text) and line length (50 to 75 characters per line).

Spacing and Layout

Provide generous spacing between interactive elements to prevent accidental clicks, especially for users with motor impairments. Use consistent spacing patterns throughout your website. Ensure content is organized in a logical, predictable layout with clear visual hierarchy. Use whitespace effectively to separate content sections and improve readability.

Navigation

Provide multiple ways to find content, including navigation menus, search functionality, breadcrumbs, and sitemaps. Ensure the current page is clearly indicated in navigation. Keep navigation consistent across all pages. Provide skip navigation links that allow keyboard users to bypass repetitive navigation and jump directly to the main content.

Forms

Design forms with accessibility in mind from the start. Every input must have a visible, programmatically associated label. Group related fields using fieldsets and legends. Provide clear instructions and examples. Show error messages inline, near the relevant field, with specific guidance on how to fix errors. Use autocomplete attributes to help users fill in forms more efficiently.

Accessible Content Creation

Accessible content is content that all users can perceive and understand, regardless of their abilities. Here are the key principles for creating accessible content.

Heading Structure

Use headings (h1 through h6) to create a logical document outline. Every page should have exactly one h1, followed by h2 elements for major sections, h3 for subsections, and so on. Never skip heading levels (e.g., jumping from h1 to h3). Use headings for their semantic purpose, not for visual styling.

Link Text

Write descriptive link text that makes sense out of context. Screen reader users often navigate by listing all links on a page, so “Click here” and “Read more” are not helpful. Instead, use descriptive text like “Read the full accessibility guide” or “Download the 2026 compliance checklist.” Avoid using URLs as link text.

Image Alt Text

Write alt text that conveys the meaning and purpose of the image, not just its appearance. For informational images, describe the key information the image conveys. For decorative images, use empty alt attributes (alt=””). For complex images like charts or infographics, provide a detailed description in the surrounding text or in a linked long description. Keep alt text concise but descriptive, typically under 150 characters.

Video Captions

All video content should have accurate, synchronized captions. Auto-generated captions are a starting point but must be reviewed and corrected for accuracy. Captions should include dialogue, speaker identification, sound effects, and music descriptions. Provide transcripts for audio-only content.

Readable Language

Write in clear, simple language that is accessible to users with cognitive disabilities and non-native English speakers. Use short sentences, common words, and active voice. Define technical terms and acronyms. Use bulleted and numbered lists to break up complex information. Aim for a reading level appropriate for your audience, and provide summaries for long-form content.

Accessibility and SEO Benefits

Web accessibility and search engine optimization share many common goals and best practices, which means that improving accessibility often improves SEO performance simultaneously.

Overlapping Best Practices

Proper heading structure improves both screen reader navigation and search engine understanding of your content. Alt text for images helps both screen reader users and search engine image indexing. Clear link text benefits both accessibility and SEO by providing context about the linked page. Fast page load times benefit users with slower connections and improve Core Web Vitals scores. Mobile-responsive design is essential for both accessibility (accommodating different devices and assistive technologies) and SEO (Google’s mobile-first indexing). Semantic HTML helps screen readers interpret page structure and helps search engines understand content hierarchy.

SEO-Specific Accessibility Benefits

Accessible websites tend to have lower bounce rates, longer session durations, and higher engagement metrics, all of which are positive signals to search engines. The structured data and semantic markup required for accessibility also enhance rich results and featured snippets in search results. Google has publicly confirmed that accessibility is a factor in their ranking algorithms, and this emphasis is expected to increase in 2026 and beyond.

Building an Accessibility Program

For organizations serious about accessibility, building a formal accessibility program ensures sustained compliance and continuous improvement.

Accessibility Policy

Develop a formal accessibility policy that states your organization’s commitment to accessibility, defines the standards you follow (WCAG 2.2 Level AA), outlines responsibilities for accessibility across teams, and establishes procedures for handling accessibility issues and requests. Publish this policy on your website as part of your accessibility statement.

Training and Awareness

Provide regular accessibility training for all team members who create or influence digital content, including developers, designers, content creators, product managers, and QA testers. Training should cover the business case for accessibility, WCAG guidelines and success criteria, assistive technology basics, accessible design and development techniques, and testing methods and tools.

Governance and Accountability

Assign clear ownership for accessibility within your organization. This might be a dedicated accessibility team, an accessibility coordinator, or designated accessibility champions within each department. Establish regular accessibility reviews as part of your development and content processes. Include accessibility criteria in performance reviews and project acceptance criteria.

Accessibility Documentation

Proper documentation demonstrates your accessibility efforts and provides transparency to users, regulators, and the courts.

Accessibility Statement

An accessibility statement is a public page on your website that describes your commitment to accessibility, the standards you follow, any known limitations, and how users can report accessibility issues. It should be linked from your website footer and include contact information for accessibility-related inquiries. A well-written accessibility statement demonstrates good faith compliance efforts and provides a channel for resolving issues before they escalate to legal action.

VPAT and ACR

A Voluntary Product Accessibility Template (VPAT) is a document that describes how a product or service conforms to accessibility standards. An Accessibility Conformance Report (ACR) is a completed VPAT based on actual testing. VPATs and ACRs are commonly required in government procurement and are increasingly requested by enterprise clients. They are based on the ITI VPAT template and address WCAG, Section 508, and EN 301 549 (European accessibility standards).

Accessibility Compliance Costs

The cost of web accessibility compliance varies widely depending on the size and complexity of your website, the current state of accessibility, and the level of conformance you need to achieve.

Compliance Activity	Small Website	Mid-Size Website	Enterprise Website
Automated Overlay Tool	$49-$149/mo	$149-$349/mo	$349-$590/mo
Automated + Manual Audit	$2,000-$5,000	$5,000-$15,000	$15,000-$50,000
Code Remediation	$3,000-$10,000	$10,000-$50,000	$50,000-$200,000
Content Remediation	$1,000-$3,000	$3,000-$15,000	$15,000-$50,000
Ongoing Monitoring	$500-$1,000/mo	$1,000-$3,000/mo	$3,000-$10,000/mo
Training Program	$500-$2,000	$2,000-$10,000	$10,000-$50,000
User Testing	$2,000-$5,000	$5,000-$15,000	$15,000-$50,000

When compared to the cost of an ADA lawsuit ($10,000 to $100,000+ in settlements plus $10,000 to $50,000+ in legal fees), the investment in proactive accessibility compliance is a clear business decision. The cost of remediation is almost always less than the cost of litigation, and the reputational damage from a lawsuit can be far more costly than any legal settlement.

State-Level Accessibility Laws Beyond Federal ADA

While the ADA provides the primary federal framework for web accessibility, several states have enacted their own accessibility laws that may impose additional requirements.

California

California’s Unruh Civil Rights Act requires businesses to be accessible to people with disabilities. The law has been interpreted to apply to websites, and California has some of the highest volumes of ADA website lawsuits in the country. California also has the California Consumer Privacy Act (CCPA), which intersects with accessibility in terms of data privacy and user rights.

New York

New York City’s Local Law 126 (2023) requires certain websites to meet WCAG 2.1 Level AA standards. The law applies to businesses that offer goods or services to the public and have a physical location in New York City. New York State also has human rights laws that have been applied to website accessibility.

Other States

Several other states have accessibility requirements that may apply to websites, including Colorado, Illinois, Texas, and Massachusetts. Additionally, states that have adopted the Model Accessibility Policy (MAP) or similar frameworks may have specific requirements for state government websites that influence broader accessibility standards.

Accessibility for E-Commerce

E-commerce websites face unique accessibility challenges because accessibility barriers directly prevent purchases. Making your online store accessible is both a legal requirement and a significant revenue opportunity.

Product Pages

Ensure product images have descriptive alt text. Provide multiple images from different angles. Write clear, detailed product descriptions in accessible language. Make product options (size, color, quantity) fully keyboard accessible. Display prices and availability in accessible formats.

Shopping Cart and Checkout

The checkout process must be fully accessible, including form labels, error messages, progress indicators, and confirmation pages. Minimize the number of checkout steps to reduce cognitive load. Provide clear order summaries and total prices. Ensure payment forms are accessible and compatible with assistive technologies.

Account Management

Account creation, login, password recovery, and order tracking must all be accessible. Provide accessible alternatives for CAPTCHA (such as audio CAPTCHA or hCaptcha). Ensure that customer service options (chat, email, phone) are accessible.

Mobile App Accessibility Overview

As mobile usage continues to grow, mobile app accessibility is becoming increasingly important. While ADA website lawsuits are more common, lawsuits targeting mobile apps are on the rise.

Mobile Accessibility Standards

Mobile apps should follow WCAG 2.2 guidelines adapted for mobile contexts, as well as platform-specific accessibility guidelines: Apple’s Human Interface Guidelines for iOS apps and Google’s Material Design Accessibility guidelines for Android apps. Key mobile accessibility requirements include touch target size (minimum 44×44 points on iOS, 48×48 dp on Android), screen reader compatibility (VoiceOver on iOS, TalkBack on Android), gesture alternatives for users who cannot perform complex gestures, and sufficient color contrast for mobile screens.

Testing Mobile Accessibility

Test mobile apps using platform-specific accessibility inspectors (Xcode Accessibility Inspector for iOS, Accessibility Scanner for Android), as well as manual testing with screen readers and users who have disabilities. Include mobile accessibility testing in your regular QA process to catch issues before they reach users. Web accessibility is not just a legal requirement; it is a fundamental aspect of building inclusive digital experiences that serve all users. By understanding the regulatory landscape, implementing WCAG 2.2 standards, using the right tools and testing methods, and building accessibility into your development process, you can create websites that are both compliant and competitive. Whether you are just starting your accessibility journey or looking to enhance an existing program, the investment in accessibility pays dividends in legal protection, market reach, and user experience. For businesses looking for expert guidance on building accessible websites, agencies like Digimau offer comprehensive web development services that prioritize accessibility from the ground up.

Frequently Asked Questions

What is ADA website compliance?

ADA website compliance means your website meets the accessibility standards required by the Americans with Disabilities Act, ensuring that people with disabilities can perceive, understand, navigate, and interact with your website. This is typically measured against WCAG 2.1 or 2.2 guidelines at the AA level.

Does the ADA apply to websites?

Yes. While the ADA does not explicitly mention websites, federal courts have consistently ruled that websites are places of public accommodation under Title III of the ADA. The Department of Justice has confirmed that the ADA applies to websites of businesses open to the public.

What is WCAG and what level should I target?

WCAG (Web Content Accessibility Guidelines) is the international standard for web accessibility. Most US businesses should target WCAG 2.2 Level AA compliance, which is the standard referenced in most lawsuits and settlement agreements. Level A is the minimum, Level AA is the practical standard, and Level AAA is the highest but rarely required.

How much does website accessibility compliance cost?

Accessibility compliance costs vary widely: automated tool overlays cost $49 to $590/month, basic audits and remediation for small sites cost $3,000 to $10,000, mid-size website remediation costs $10,000 to $50,000, and enterprise-level accessibility programs cost $50,000 to $250,000+. Ongoing monitoring adds $500 to $5,000/month.

What are the most common website accessibility issues?

The most common issues include missing or inappropriate alt text on images, lack of keyboard navigation support, insufficient color contrast ratios, missing form labels and error messages, no visible focus indicators, missing video captions and audio descriptions, and improper heading structure.

Can I be sued for an inaccessible website?

Yes. ADA website lawsuits have been increasing steadily, with over 4,000 federal lawsuits filed annually in recent years. Industries most commonly targeted include retail, restaurants, hospitality, healthcare, financial services, and education. Settlements typically range from $10,000 to $100,000 plus legal fees.

What accessibility tools should I use?

Use a combination of automated tools (Lighthouse, axe, WAVE), overlay solutions for quick fixes (accessiBe, AudioEye, UserWay), manual testing with screen readers (NVDA, JAWS, VoiceOver), and professional audits. No single tool catches all accessibility issues, so a multi-tool approach is essential.

What is the difference between ADA and Section 508?

The ADA is a civil rights law that applies to private businesses open to the public. Section 508 is a federal law that requires federal agencies and their contractors to make their electronic and information technology accessible. Section 508 specifically references WCAG standards and is more prescriptive than the ADA.

How do I test my website for accessibility?

Start with automated scanning tools like Lighthouse, axe, or WAVE to identify common issues. Then conduct manual testing including keyboard-only navigation, screen reader testing with NVDA or VoiceOver, color contrast checking, and testing with browser zoom. For comprehensive results, hire an accessibility professional for a manual audit.

Is using an accessibility overlay enough for ADA compliance?

No. Accessibility overlays (like accessiBe or UserWay) can help address some common issues but cannot fix underlying code problems. The DOJ and accessibility experts have stated that overlays are not sufficient for full compliance. A comprehensive approach including code-level remediation, manual testing, and ongoing monitoring is required.