ADA Website Compliance: Risks for US Online Businesses

For online businesses in the United States, ADA website compliance can feel like a question with two unsatisfying answers: alarming predictions about lawsuits, or assurances that a quick scan will solve everything. Neither helps you decide what to do. The useful questions are how exposure arises, which accessibility barriers your customers encounter, and how you can document meaningful improvements.

The Americans with Disabilities Act (ADA) creates real exposure for businesses open to the public, including through private lawsuits and demand letters. But that does not establish the likelihood of a claim against your particular website. A sensible approach combines legal advice about your circumstances with technical testing and a practical remediation process.

Where ADA website compliance exposure comes from

For businesses open to the public under ADA Title III, exposure comes mainly from private lawsuits and demand letters. A court can order a website to be made accessible and award the prevailing party attorneys’ fees. These are concrete reasons to take accessibility seriously, without assuming that every inaccessible page will lead to litigation.

The relevant federal authority is the U.S. Department of Justice, Civil Rights Division. The Department of Justice can also sue and seek civil penalties. Private claims and government enforcement are therefore distinct sources of exposure; the issue is not simply whether a regulator has contacted your business.

For an individual online business, a general article cannot determine whether the ADA applies to its specific circumstances or predict the outcome of a dispute. Those are questions for an attorney. Technical accessibility work answers a different question: what prevents people from using the website, and how can those barriers be removed?

What WCAG means for a private business website

No federal regulation sets a technical standard for business websites. The Department of Justice’s March 2022 guidance on web accessibility and the ADA names WCAG as helpful guidance. That distinction matters when evaluating claims that a particular audit or certificate will settle every legal question.

The Department of Justice’s 2024 rule adopting WCAG 2.1 AA applies to state and local governments under Title II, not to private businesses. An online retailer should not treat that government-specific rule as its own private-sector technical regulation.

For technical planning, a WCAG 2.1 AA audit can nevertheless provide a structured benchmark. It gives designers, developers, and business owners a shared framework for investigating accessibility and describing findings. Its value is in the testing and actionable evidence, not in a promise of a particular legal outcome.

Keep the distinction clear when commissioning work: ask for an assessment against the stated standard, with its scope and limitations explained. Do not mistake a technical report for a legal opinion about ADA website compliance.

Start with the journeys customers need to complete

The most useful starting point is not a badge or an overall score. It is a map of the tasks people come to your website to perform. For an online store, that might mean finding an item, choosing options, adding it to a cart, and completing checkout. For a service business, it might mean requesting a quote or booking an appointment.

Build your testing scope around those journeys, including the screens and interactions between the main pages. Consider:

• Keyboard access: Can someone reach and operate menus, forms, dialogs, and checkout controls without a mouse?
• Screen-reader use: Do controls have meaningful names, and are important changes or errors communicated?
• Form completion: Are instructions clear, and can customers understand and correct mistakes?
• Visual presentation: Can people read content and use controls when text is enlarged?
• Outside components: Have embedded booking, payment, or support tools been included in testing?

These are testing prompts, not a complete checklist. A homepage scan can offer an initial view, but it does not establish how an account area, checkout, or interactive form behaves. Automated checks should be paired with manual evaluation of important tasks.

Why documented findings and remediation matter

An undocumented statement that “we checked accessibility” gives a team little to act on. A useful website accessibility audit connects a finding to a specific location, explains the user impact, and provides enough detail for someone else to reproduce the problem.

For each issue, maintain a record that includes:

• The affected page, component, or customer journey.
• The steps and testing conditions used to identify the barrier.
• The observed behavior and its impact on the user.
• The relevant WCAG criterion, where applicable.
• The proposed fix, responsible owner, and current status.
• The result of retesting after the change.

This record helps developers reproduce issues, gives managers visibility into unfinished work, and makes it easier to distinguish proposed fixes from verified improvements. It can also give your attorney a clearer factual account of what was tested and changed if a legal question arises.

Documentation is not immunity from a claim. Its practical value is that it makes the work traceable. An audit identifies issues; remediation addresses them; retesting checks whether the intended improvement actually works. None of those steps should be presented as a guarantee of legal protection.

What to do if you receive an ADA website demand letter

If a demand letter arrives, consult an attorney about its allegations and the appropriate response. Do not rely on a scan score, a vendor’s assurance, or a general blog article to decide whether the claim has merit. Legal assessment and technical investigation should inform each other without being confused.

Give your attorney the letter and any existing accessibility reports, remediation records, and information about recent website changes. Ask how to coordinate technical investigation and communications. Your technical team can then investigate the reported barriers, record what it finds, and identify related problems in shared components.

For example, a reported problem with one form may also affect other forms using the same design. Fixing only the named page could leave the underlying component unchanged. Treat the allegation as something to investigate carefully, not as a complete inventory of the website’s accessibility issues.

Build a manageable accessibility process

You do not need to wait for a demand letter to establish a useful workflow. Scope the essential journeys, assess them, prioritize barriers that prevent completion, and assign owners to the fixes. Retest changes and retain a clear record of what remains unresolved.

Add accessibility checks when introducing new templates, redesigning navigation, or replacing important integrations. Reusable components deserve particular attention because a single improvement can benefit multiple parts of the site.

If your team needs outside support, professional audit services such as geta11y can help identify issues. Evaluate any service by its testing scope, clarity of findings, and stated limitations rather than by promises of legal certainty.

The sober answer is that ADA website claims are a real source of exposure, but their likelihood and outcome cannot be reduced to an audit score. Get legal advice for legal questions, investigate the experience your website provides, and keep a reliable record of improvements. That produces something more useful than reassurance alone: a clearer understanding of the barriers and a practical plan to remove them.