Web Accessibility (ADA/WCAG): Why It Matters and How to Get Compliant

In 2023, over 4,600 ADA-related web accessibility lawsuits were filed in the United States—a 300% increase since 2018¹. Target, Domino's, Netflix, and thousands of small businesses have been sued because their websites weren't accessible to people with disabilities. The courts are increasingly ruling that the ADA applies to websites, and businesses that ignore accessibility are exposed to real legal and financial risk.

But here's what the fear-based accessibility overlay companies don't tell you: accessibility isn't just a legal obligation. It's a business advantage. Over 1 billion people worldwide—roughly 16% of the global population—live with some form of disability². An inaccessible website doesn't just create legal risk; it actively turns away paying customers. And the overlap between accessibility best practices and SEO best practices is enormous. Making your site accessible almost always makes it rank better, too.

This guide covers what web accessibility actually means, the legal landscape, WCAG standards and how to meet them, common issues we see on client sites, how to audit your own site, and the business case that goes far beyond compliance.

What Web Accessibility Actually Means

Web accessibility means designing and building websites that can be used by everyone, including people with visual, auditory, motor, and cognitive disabilities. It's about removing barriers that prevent people from perceiving, understanding, navigating, and interacting with your website.

This includes people who are blind and use screen readers, people who are deaf and need captions for audio and video, people with motor impairments who navigate using a keyboard instead of a mouse, people with cognitive disabilities who need clear and simple language, and people with temporary impairments like a broken arm or situational limitations like bright sunlight on a phone screen.

Accessibility isn't about building a separate “accessible version” of your website. It's about building one website that works for everyone. When done right, accessible websites are faster, cleaner, better structured, and easier to use for all visitors—not just those with disabilities.

The Legal Landscape: ADA and Websites

The Americans with Disabilities Act (ADA) was signed into law in 1990, long before the internet existed as we know it. Title III of the ADA requires that “places of public accommodation” be accessible to people with disabilities. The courts have increasingly interpreted this to include websites, especially for businesses that have physical locations or sell goods and services online.

Key Legal Developments

• Domino's v. Robles (2019): The Supreme Court declined to hear Domino's appeal, letting stand a lower court ruling that the ADA applies to websites. This case set a powerful precedent that businesses cannot ignore³.
• DOJ guidance (2022): The Department of Justice issued formal guidance stating that web accessibility is covered under the ADA and pointing to WCAG 2.1 as the technical standard⁴.
• Demand letters: Many accessibility lawsuits never make it to court. Businesses receive demand letters from law firms representing plaintiffs and settle for $5,000 to $50,000+ to avoid litigation. These letters target e-commerce sites, restaurants, healthcare providers, and any business with an online presence.
• State laws: California, New York, and Florida lead the country in accessibility lawsuits. Some states have additional laws beyond the federal ADA that apply to digital accessibility.

The legal risk is real and growing. But here's the thing: if you build your website properly from the start, compliance is neither expensive nor difficult. The businesses getting sued are the ones that ignored accessibility entirely, not the ones that made a good-faith effort.

WCAG 2.1: The Standard You Need to Meet

The Web Content Accessibility Guidelines (WCAG), published by the World Wide Web Consortium (W3C), are the internationally recognized standard for web accessibility. WCAG 2.1 is the current standard referenced by the DOJ and courts. WCAG 2.2 was published in October 2023 and adds additional criteria, but 2.1 AA remains the most commonly cited legal benchmark⁵.

The Three Conformance Levels

• Level A (Minimum): The bare minimum of accessibility. If your site doesn't meet Level A, it's fundamentally broken for assistive technology users. This includes things like providing text alternatives for images and making all functionality available via keyboard.
• Level AA (Standard): The target for most organizations and the level cited in most legal proceedings. Level AA includes everything in Level A plus requirements for color contrast ratios, text resizing, consistent navigation, and error identification in forms. This is the level you should aim for.
• Level AAA (Enhanced): The highest level of accessibility. Meeting every AAA criterion is often impractical for entire websites, but individual pages or sections can target AAA for maximum inclusivity. Examples include sign language interpretation for audio content and enhanced contrast ratios.

The Four Principles of WCAG: POUR

Every WCAG guideline falls under one of four principles, known by the acronym POUR. Understanding these principles helps you think about accessibility holistically rather than as a checklist of technical fixes.

1. Perceivable

Information and user interface components must be presentable to users in ways they can perceive. This means content can't rely on a single sense. If something is visual, there must be a text alternative. If something is audio, there must be captions or a transcript.

• Text alternatives: Every non-text element (images, icons, buttons) needs descriptive alt text that conveys its purpose. Decorative images should have empty alt attributes (alt="") so screen readers skip them.
• Captions and transcripts: All video content needs synchronized captions. All audio content needs text transcripts. Auto-generated captions are a start but must be reviewed for accuracy.
• Color contrast: Text must have a minimum contrast ratio of 4.5:1 against its background for normal text, and 3:1 for large text (18px+ bold or 24px+ regular). This ensures readability for people with low vision or color blindness.
• Don't rely on color alone: If color conveys meaning (red for errors, green for success), provide additional indicators like icons, text labels, or patterns. Approximately 8% of men have some form of color blindness⁶.

2. Operable

User interface components and navigation must be operable by all users, regardless of how they interact with the web. Not everyone uses a mouse. Many people navigate entirely with a keyboard, a switch device, or voice commands.

• Keyboard accessibility: Every interactive element—links, buttons, forms, menus, modals—must be accessible and operable using only a keyboard. Try navigating your site with just Tab, Enter, and Escape. If you get stuck, keyboard users get stuck too.
• Visible focus indicators: When a user tabs through elements, there must be a visible focus indicator (usually an outline or highlight) showing which element is currently active. Many sites remove default focus outlines for aesthetic reasons, which makes keyboard navigation impossible.
• No time limits: Content shouldn't have time limits that prevent users from completing tasks. If time limits are necessary (like a checkout session), provide options to extend or disable them.
• Skip navigation: Provide a “Skip to main content” link at the top of every page so keyboard users don't have to tab through the entire navigation menu on every page load.
• No seizure-inducing content: Content that flashes more than three times per second can trigger seizures in people with photosensitive epilepsy. Avoid flashing content entirely.

3. Understandable

Information and the operation of the user interface must be understandable. Users must be able to comprehend the content and figure out how to use the interface.

• Readable content: Use clear, plain language. Specify the page's language in the HTML (lang="en") so screen readers pronounce words correctly. If content includes words in another language, mark those sections appropriately.
• Predictable behavior: Navigation should be consistent across pages. Elements should behave the way users expect. Don't open links in new windows without warning. Don't change context unexpectedly when a user interacts with a form field.
• Error identification: When a form submission fails, clearly identify what went wrong and how to fix it. Don't just turn the field red—provide a text message explaining the error. Position error messages near the fields they relate to.
• Labels and instructions: Every form field needs a visible label that clearly describes what input is expected. Placeholder text is not a substitute for labels—it disappears when the user starts typing, leaving them without guidance.

4. Robust

Content must be robust enough to be interpreted reliably by a wide variety of user agents, including assistive technologies. This is primarily a technical concern.

• Valid HTML: Use semantic, well-structured HTML. Proper heading hierarchy (h1, h2, h3), meaningful landmark elements (header, nav, main, footer), and correct use of ARIA attributes when native HTML isn't sufficient.
• ARIA where needed: Accessible Rich Internet Applications (ARIA) attributes help screen readers understand dynamic content and custom widgets. But the first rule of ARIA is: don't use ARIA if native HTML can do the job. Incorrect ARIA is worse than no ARIA.
• Name, role, value: All UI components must have an accessible name (what it is), role (what it does), and value/state (its current status). A toggle switch, for example, needs to communicate that it's a switch, what it controls, and whether it's on or off.

Most Common Accessibility Issues (And How to Fix Them)

The WebAIM Million study, which analyzes the home pages of the top 1 million websites, finds the same issues year after year. The good news? Most of these are straightforward to fix⁷.

How to Audit Your Website for Accessibility

A thorough accessibility audit combines automated testing (to catch the obvious issues) with manual testing (to catch everything automated tools miss). Automated tools can detect roughly 30-40% of accessibility issues⁸. The rest require human judgment.

Step 1: Automated Testing

• Run an automated scan: Use tools like axe DevTools, WAVE, or Lighthouse Accessibility audit. These will catch missing alt text, contrast issues, missing form labels, broken ARIA, and other machine-detectable problems.
• Test every page template: Don't just test the home page. Test your product pages, blog posts, contact forms, checkout flow, and any other unique page template. Issues vary by template.
• Prioritize by severity: Critical issues (keyboard traps, missing alt text on functional images, zero-contrast text) should be fixed immediately. Minor issues (suboptimal heading hierarchy, slightly below-ratio contrast) can be scheduled.

Step 2: Manual Testing

• Keyboard-only navigation: Put your mouse away and try to use your entire site with just a keyboard. Can you reach every link, button, and form field? Can you see where focus is? Can you escape modals and menus?
• Screen reader testing: Use VoiceOver (Mac), NVDA (Windows, free), or JAWS (Windows) to navigate your site. Listen to how your content is announced. Does it make sense without visual context? Are images described? Are forms labeled?
• Zoom testing: Zoom your browser to 200%. Does the layout break? Does content overlap? Can you still read everything and complete all tasks? WCAG requires sites to be usable at 200% zoom.
• Color and contrast: View your site in grayscale. Can you still distinguish all elements and understand the interface? If meaning is conveyed only through color, it's inaccessible.

Step 3: User Testing

The gold standard is testing with actual users who have disabilities. No amount of automated or manual testing by sighted developers can replace the insights of someone who uses a screen reader daily. Organizations like Fable and AccessWorks connect businesses with disabled testers for usability studies. Even a small-scale user test with two or three participants will reveal issues you never considered.

Accessibility Tools and Resources

Here are the tools we use and recommend for ongoing accessibility testing and monitoring.

A Warning About Accessibility Overlays

You've probably seen the widget icons in the corner of websites that promise one-click accessibility. Products like AccessiBe, UserWay, and AudioEye market themselves as instant accessibility solutions. They are not.

The National Federation of the Blind has issued a formal position statement opposing overlays⁹. Accessibility experts universally recommend against them. And critically, companies using accessibility overlays have been sued at the same rate as companies without them. Overlays cannot fix underlying structural issues, often interfere with screen readers, and create a false sense of compliance that increases legal risk.

There are no shortcuts. Real accessibility requires proper HTML structure, thoughtful design, and ongoing attention. It's an investment in your codebase and your user experience—not a widget you bolt on.

The Business Case Beyond Compliance

Legal compliance is the floor, not the ceiling. Here's why accessibility is a genuine business advantage.

Larger Addressable Market

Over 61 million adults in the United States live with a disability—that's 26% of the adult population¹⁰. They represent over $490 billion in disposable income. When you add in their families and friends who influence purchasing decisions, the addressable market of people affected by accessibility is even larger. An inaccessible website literally cannot serve a quarter of your potential market.

Better SEO Performance

The overlap between accessibility and SEO is significant. Alt text helps Google understand your images. Proper heading hierarchy helps Google understand your content structure. Descriptive link text helps Google understand your page relationships. Clean, semantic HTML helps Google crawl and index your site. Fast page loads improve both accessibility and Core Web Vitals. Every accessibility improvement is an SEO improvement.

Better User Experience for Everyone

Curb cuts were designed for wheelchair users but are used by everyone—parents with strollers, delivery workers with carts, travelers with luggage. Web accessibility works the same way. Captions help people watching video in noisy environments. High contrast helps people using their phone in bright sunlight. Keyboard navigation helps power users who prefer keyboard shortcuts. Clear error messages help everyone fill out forms correctly. Accessible design is better design, period.

Improved Brand Reputation

In an era where consumers increasingly choose brands based on values, demonstrating a commitment to inclusion isn't just ethical—it's good business. 73% of consumers say they would switch to a brand that demonstrates inclusive practices¹¹. Accessibility is a tangible, provable way to show that your business serves everyone.

Getting Started: A Practical Roadmap

If your site has never been audited for accessibility, here's how to approach it without getting overwhelmed.

• Audit first: Run automated scans on your key page templates. Catalog every issue by severity and effort to fix.
• Fix the critical issues: Missing alt text, zero keyboard accessibility, broken forms, keyboard traps. These are the issues most likely to trigger lawsuits and the ones causing the most harm to users.
• Address medium-priority issues: Contrast ratios, heading hierarchy, link text, focus indicators, skip navigation. These take more time but have significant impact.
• Build accessibility into your process: Don't treat it as a one-time project. Include accessibility requirements in design briefs, test during development, and audit quarterly. New content and features should be accessible from day one.
• Publish an accessibility statement: A public statement on your website that describes your commitment to accessibility, the standard you're targeting (WCAG 2.1 AA), known limitations, and how users can report issues. This demonstrates good faith and gives users a path to communicate problems.
• Iterate continuously: Accessibility is not a destination. Websites change, content is added, features are built. Ongoing testing and remediation are essential to maintaining compliance.

The Bottom Line

Web accessibility is not optional. It's a legal requirement, a business opportunity, and a fundamental aspect of building a good website. The businesses getting sued are not the ones making honest efforts to improve—they're the ones that never started.

The good news is that accessibility is achievable. Most issues are straightforward to fix. The standards are clear and well-documented. The tools are available and often free. And the return on investment—legal protection, larger audience, better SEO, improved UX—makes it one of the smartest investments you can make in your website.

Stop treating accessibility as a nice-to-have. It's a must-have. Your customers deserve a website they can use. Your business deserves a website that reaches its full audience. And the law increasingly demands both.

References

1. UsableNet, “ADA Digital Accessibility Lawsuits Annual Report,” UsableNet, 2024.
2. World Health Organization, “Disability and Health Fact Sheet,” WHO, 2024.
3. Domino's Pizza LLC v. Robles, No. 18-1539 (U.S. Supreme Court, cert. denied 2019).
4. U.S. Department of Justice, “Guidance on Web Accessibility and the ADA,” DOJ, 2022.
5. W3C, “Web Content Accessibility Guidelines (WCAG) 2.1,” World Wide Web Consortium, 2018.
6. National Eye Institute, “Color Blindness Statistics,” NEI, 2024.
7. WebAIM, “The WebAIM Million: Annual Accessibility Analysis,” WebAIM, 2024.
8. Deque Systems, “Automated vs. Manual Accessibility Testing,” Deque Blog, 2024.
9. National Federation of the Blind, “Statement on Accessibility Overlays,” NFB, 2024.
10. CDC, “Disability Impacts All of Us,” Centers for Disease Control and Prevention, 2024.
11. Accenture, “Getting to Equal: The Disability Inclusion Advantage,” Accenture, 2023.