Website accessibility and ADA compliance for online stores

Every time a customer with a disability cannot navigate your checkout process, fill out a product filter, or read your product descriptions, you have just lost a sale. More than 1 in 4 adults in the US have some form of disability. That is not a small market segment. It is your market.

Website accessibility is not just an ethical issue. It is a legal requirement. The Americans with Disabilities Act (ADA) requires that businesses make their services accessible to people with disabilities. This includes online stores. Thousands of websites receive legal demands every year for accessibility violations, and e-commerce sites are the most frequently targeted. This article covers what accessibility means, why it matters for your store, what the law requires, and how to implement it without expensive specialized tools.

What is website accessibility?

Website accessibility means your site is usable by everyone, including people with disabilities. This includes people who are blind or have low vision, deaf or hard of hearing, have motor disabilities that make using a mouse difficult, have cognitive or learning disabilities, or have other conditions that affect how they use the web.

Accessible websites work with assistive technologies like screen readers (software that reads text aloud), keyboard-only navigation (for people who cannot use a mouse), and magnification tools. An accessible site also uses clear language, sufficient color contrast, proper heading structure, and form labels that screen readers can understand.

The key principle: your customers should be able to accomplish what they came to do. They should browse, filter, read descriptions, add to cart, and complete checkout, no matter what assistive technology or adaptations they use.

What is the ADA and why does it apply to your store?

The Americans with Disabilities Act (ADA), passed in 1990, is US federal law that prohibits discrimination against people with disabilities. Title III of the ADA requires that all businesses open to the public provide equal access to people with disabilities. This includes websites and online services. The law does not carve out exemptions for small businesses or online retailers.

Your online store counts as a public accommodation under the ADA. That means your website must be accessible. You cannot argue that your store is too small, too new, or that accessibility is too expensive. The law applies. Courts have consistently ruled that the ADA applies to websites, and the US Department of Justice has stated that website accessibility is a civil rights issue, not optional.

WCAG 2.1 Level AA: the accessibility standard

The web accessibility standard used in legal cases and compliance requirements is called WCAG (Web Content Accessibility Guidelines) 2.1 Level AA. WCAG is maintained by the World Wide Web Consortium (W3C), a nonprofit that sets standards for the web.

WCAG 2.1 Level AA includes guidelines in four main areas:

Perceivable: users can see or hear your content

Your content must be presented in ways customers can perceive. This means providing text descriptions (alt text) for all product images, adding captions to videos, ensuring text and buttons have sufficient color contrast (4.5:1 ratio minimum for standard text), and avoiding content that flashes more than 3 times per second, which can cause seizures.

Operable: users can navigate and interact with your store

Users must be able to navigate your store using only a keyboard (no mouse required). Links and buttons must be keyboard accessible. Forms must have clear labels that screen readers can understand. Your store should not trap keyboard users in infinite loops or require timed interactions that users cannot adjust. Menu items and form inputs must be easy to find and use.

Understandable: users can comprehend what your store says and does

Your store must be easy to understand. Use clear language and short sentences. Define jargon on first use. Organize your pages logically with proper heading structures (one H1 per page, followed by H2s, H3s in order). Explain form validation errors clearly. Make your site consistent so users can predict how navigation and interactions work.

Robust: your store works with assistive technologies

Your code must be written correctly so that screen readers and other assistive tools can understand it. This means using proper HTML semantic markup (buttons are actual button elements, not divs styled to look like buttons), proper heading hierarchy, and ARIA labels where needed to describe complex interactive elements. Your store should work across browsers and devices.

Common accessibility barriers in online stores

These are the most frequent accessibility problems found in e-commerce stores:

Missing or poor alt text for product images

Many online stores have no alt text for product images, or vague alt text like "image" or "product photo". Screen reader users cannot see images. Alt text must describe what is important about the image. For a red t-shirt, good alt text is "red cotton crew-neck t-shirt with front pocket" not "shirt" or "red shirt pic". For a product variant selector, alt text might describe the color swatch or style option clearly. Every product image needs accurate, descriptive alt text.

Forms without proper labels

When a form field (email box, phone box, address field) has no associated label, or the label is only visual placeholder text, screen reader users do not know what to enter. Properly labeled forms have invisible but accessible label elements that tell screen readers what each field is for.

No keyboard navigation

Some sites require a mouse to navigate or complete a purchase. Keyboard-only users cannot use dropdown menus, cannot see which item is focused, or cannot tab through form fields in a logical order. Every function should be keyboard accessible. Keyboard focus should be visible on the page so users know where they are.

Poor color contrast

Text that is light gray on a white background might be readable to you. It is not readable to people with low vision. WCAG Level AA requires a contrast ratio of at least 4.5:1 for normal text. Buttons, links, and any text users need to read must meet this standard. Check your contrast using a free tool like WebAIM's contrast checker.

Confusing heading structure

Screen reader users often navigate pages by jumping between headings. If your page jumps from H1 to H3 to H2, or uses headings only for styling, screen readers create a confusing experience. Use headings in logical order to structure your page. One H1 per page, then H2s for major sections, H3s for subsections. Never skip heading levels.

Buttons and links without clear purpose

A button that says "click here" tells screen reader users nothing about what clicking does. Use descriptive button text: "Add to cart", "View reviews", "Proceed to checkout". If you need a button with an icon, include text or an ARIA label describing the action. Every interactive element must have a clear, descriptive label.

Inaccessible drop-down menus and filters

Product filter menus, category dropdowns, and sort options that only work with a mouse are common barriers. Keyboard users need to access these the same way. Complex interactive components need ARIA roles and keyboard support to work with assistive technology.

How to make your store accessible

Accessibility does not require hiring an expensive consultant or buying specialized software. Start with the fundamentals:

1. Write alt text for all product images

This is the single highest-impact change. Go through your products and write descriptive alt text for every image. Describe the product, its color, material, condition, and distinctive features. Test your alt text by reading it out loud. Does someone who cannot see the image understand the product? If not, improve it.

2. Ensure all forms have proper labels

Every form field must have a label element associated with it in your code. Do not rely on placeholder text. Remove placeholder text once the field is focused, or keep it but add a real label. For checkbox and radio groups, group them and label them clearly. Form validation errors should be specific and tell users exactly what to fix.

3. Make sure keyboard navigation works

Test your entire store using only your keyboard. Press Tab to navigate. Can you reach every button, link, and form? Can you see where focus is? Is the tab order logical (left to right, top to bottom)? If keyboard users get stuck or cannot reach something, fix it. Most accessibility barriers are keyboard barriers.

4. Check and improve color contrast

Use a free contrast checker tool on your product page, buttons, links, and form labels. Ensure text meets 4.5:1 contrast for normal text and 3:1 for large text (18pt or larger). Do not rely on color alone to convey information (e.g., "red items are on sale"). Add text labels or icons to support meaning.

5. Fix your heading structure

Audit your page structure. You should have one H1 (the main page title), then H2s for major sections, H3s for subsections. Never skip heading levels. Use headings to structure content logically, not for styling. If you need styled text that is not a real heading, use a div and CSS, not a heading tag.

6. Write clear link and button text

Screen reader users often pull up a list of all links on a page. Links should make sense out of context. "Learn more about shipping options" is better than "learn more". "View product reviews" is better than "read reviews". Buttons should clearly describe their action: "Add to cart", "Proceed to checkout", "Save for later".

7. Test with assistive technology

Download a free screen reader like NVDA (for Windows) or use the built-in accessibility tools on Mac and iPhone. Listen to how your site sounds. Can you complete a purchase using only keyboard and screen reader? This is the real test of accessibility. Many barriers become obvious when you try to use your own store as a blind or keyboard-only user.

Accessibility testing and auditing

After making changes, test your store for accessibility. Start with these tools:

Automated testing tools

Free tools like WebAIM, Axe, and Lighthouse (built into Chrome) will scan your pages and flag common issues like missing alt text, low contrast, and poor heading structure. These tools catch maybe 30% of accessibility problems, so they are a starting point, not the full answer. Use them for a quick scan, but do not assume an all-clear means your site is fully accessible.

Keyboard testing

Navigate your site using only Tab, Shift+Tab, Enter, and arrow keys. No mouse. This is the most important test. Can you complete every task? Do you get stuck? Is focus visible? Does tab order make sense? If keyboard navigation is broken, your store fails the accessibility standard, regardless of what automated tools say.

Screen reader testing

Listen to your site using NVDA (Windows) or VoiceOver (Mac). Does the screen reader describe product images clearly? Can you understand form labels? Does navigation make sense? Are there unexplained buttons or links? Professional accessibility audits often hire blind testers to use your site, but you can catch major issues by doing basic screen reader testing yourself.

Manual code review

Check your HTML code for proper semantic markup. Buttons should be button elements, not styled divs. Links should be anchor tags. Form fields need label elements. Headings should be h1, h2, h3 tags in order, not h1, h3, h2. Good semantic HTML is the foundation of accessibility.

How WEMASY helps with accessibility

WEMASY's website builder is built with accessibility in mind. The platform includes semantic HTML structure, proper form handling with accessible labels, keyboard-navigable menus and cart functions, and tools to add alt text to images easily. When you use WEMASY to build your store, the underlying HTML is already structured for accessibility. You do not inherit inaccessible code from the platform.

This does not mean your site is automatically fully accessible—you still need to provide good alt text, use clear language, and test with real users. But WEMASY's foundation removes many common barriers that plague other e-commerce platforms. See what is included in each plan at our pricing page.

The business case for accessibility

Beyond legal compliance, accessibility is good business. Accessible sites are more usable for everyone—not just people with disabilities. Clear language, good contrast, logical structure, and keyboard navigation benefit older users, users on mobile devices, users in noisy environments, and users with slow internet. A site accessible to people with disabilities is a better site for all users.

More directly: 1 in 4 US adults have a disability. That is roughly 65 million people. If your store is not accessible, you are excluding a huge market. You are also leaving money on the table. Blind and low-vision shoppers spend billions online. They want to buy from your store. Make it possible.

On the legal side, the risk is real. Over 5,000 website accessibility lawsuits were filed in 2025. E-commerce sites account for 70% of those cases. A demand letter for accessibility violations costs time and legal fees to defend. Settling without fixing the underlying problems just invites more claims. The smartest approach is to fix your site now, document your efforts, and avoid the problem entirely.

Getting started

If your store is not accessible, do not panic. Start with the highest-impact fixes: alt text, keyboard navigation, and contrast. These three changes will catch most accessibility barriers. Test with keyboard navigation and a screen reader. Fix the problems you find. Document your work. Retest regularly, especially after making changes to your site. Accessibility is not a one-time project—it is an ongoing practice of building inclusively.

FAQ

Related reading: Privacy policy, cookie consent, and GDPR for your store and How to protect your brand and products from being copied.