Skip to main content

ADA Compliance: Website Guidance for US Online Stores

United States · By the geta11y team ·

For online store owners in the United States, advice about ADA compliance, website accessibility, and technical standards can seem contradictory. You want customers to browse and buy without barriers, but you also need to understand what applies to your business—not simply follow a checklist labeled “compliant.”

The useful distinction is between legal applicability and technical accessibility. The Americans with Disabilities Act (ADA) creates potential legal exposure for businesses open to the public. WCAG provides a practical framework for identifying and addressing accessibility barriers. Those are related questions, but an accessibility test cannot answer both.

Start by asking an attorney whether and how the law applies to your business. In parallel, you can assess your store’s shopping experience and begin removing barriers.

Understanding ADA website requirements for private stores

For businesses open to the public under ADA Title III, website accessibility 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. The U.S. Department of Justice, Civil Rights Division is the relevant federal enforcement authority; the Department of Justice can also sue and seek civil penalties.

That does not establish whether the law applies to your particular store. Treat that as a legal question for an attorney, rather than something a developer, scanner, or audit report can settle.

There is also an important technical distinction: 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. This makes WCAG a useful reference for accessibility work, without turning a test result into a legal conclusion.

Do not confuse government rules with business requirements

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 rule as the source of a technical mandate for its private store.

Equally, the absence of a federal technical regulation for business websites does not eliminate the exposure described above. The practical response is to get advice on applicability while using a defined accessibility standard to guide improvements.

Why use WCAG 2.1 AA as your working reference?

WCAG 2.1 AA gives your team a shared framework for evaluating accessibility. Instead of asking whether a page “looks accessible,” you can examine specific aspects of its content, controls, and behavior.

For an online store, that means considering whether customers can understand product information, operate menus and forms, choose options, and complete checkout. These tasks should shape your testing scope—not just the appearance of the homepage.

Some checks have measurable thresholds. Under WCAG 2.1 AA, minimum text contrast is 4.5:1 for ordinary text and 3:1 for large text. Other checks require closer attention to how the interface works: whether a keyboard user can reach an option, whether a field has an understandable label, or whether an error message helps a customer recover.

Use WCAG 2.1 AA as a technical target for assessment and remediation. Do not describe it as a federally prescribed standard for private business websites or assume that meeting a checklist guarantees a legal outcome.

How to test website accessibility: a practical checklist

Define a complete shopping journey

Write down a realistic path from arrival to completed purchase. Include navigation, search, product selection, the cart, checkout, and confirmation. Add account access and customer support where they are part of the experience.

Choose representative pages and states, not only URLs. A product page with no selected size behaves differently from the same page after an unavailable option is chosen. Checkout with validation errors needs separate attention from an empty checkout form.

Run an automated scan, then investigate

An automated scan can flag issues such as certain contrast failures or missing accessible names. Use the findings as a starting list to investigate, not as a complete assessment.

A homepage scan concerns the homepage. It does not tell you whether a customer can use product filters, update a cart, or submit payment details. Likewise, a scan that reports no detected issues is not proof that every relevant accessibility requirement is satisfied.

Try the journey using only a keyboard

Set the mouse aside and move through the shopping path with the keyboard. Watch where focus goes and whether you can see it.

  • Can you open and close navigation menus?
  • Can you select product options and add an item to the cart?
  • Can you operate dialogs without becoming trapped?
  • Can you reach checkout controls in a sensible order?
  • After an error or update, can you understand where you are?

Record the exact point where progress becomes difficult or impossible. “Cannot dismiss the cart dialog using the keyboard” is more actionable than “the cart is inaccessible.”

Review content, forms, and visual presentation

Check whether meaningful product images have useful text alternatives. Review headings and link text for clarity. In forms, look for persistent, understandable labels and instructions rather than relying only on placeholder text.

Trigger errors deliberately. Leave a required field empty or enter an invalid value, then check whether the problem and the correction are clear. Do not rely on color alone to communicate what went wrong.

Review text contrast and try enlarging text and zooming the page. Check whether descriptions, prices, controls, and error messages remain readable and usable without overlapping or disappearing.

Include assistive-technology testing

Add screen-reader testing to examine whether controls have meaningful names, product options convey their state, and important updates are understandable. If your team lacks experience, seek help from someone who can evaluate the interaction rather than simply switch a screen reader on.

Combine automated findings, manual checks, and assistive-technology testing. Each contributes evidence about the experience; none should be presented as a guarantee of legal compliance.

Turn findings into a manageable improvement plan

Prioritize barriers that prevent essential shopping tasks, then address recurring problems in shared components. Fixing a navigation menu, form component, or product template can be more useful than repeatedly correcting isolated instances.

Give each issue a clear description, steps to reproduce it, the affected component, and an owner. Retest after the fix. Keep a record of what was assessed, what changed, and what remains unresolved so that future work has a reliable starting point.

Include third-party checkout features and other integrations in your review. When you cannot change a component directly, document the barrier and raise it with the supplier.

Professional audit services such as geta11y can help identify accessibility issues when your team needs a structured assessment. An audit supports technical decisions; it does not determine legal applicability or guarantee legal outcomes.

The next step is straightforward: seek legal advice about your business, choose a representative shopping journey, and test it against a defined accessibility reference. You do not need to resolve every legal question before making your store easier to use.