The average ADA website accessibility lawsuit settles for $3,000 to $25,000. Most defendants never saw it coming. They assumed their site was fine because it looked clean, loaded fast, and worked on their phone.
But "works for me" is not the same as "works for everyone."
Website accessibility is the practice of designing and building websites so people with disabilities (visual, motor, auditory, cognitive) can perceive, navigate, and interact with your content. It is not a niche concern. It is a design quality problem with legal, financial, and conversion consequences that most startup founders discover too late.
This article gives you an 8-point website accessibility checklist you can run in 15 minutes, the specific thresholds you need to pass, and the free tools to test with. No developer required.
Why Website Accessibility Matters Now
The numbers have shifted from "should do" to "have to do" territory.
79.1% of the top 1 million websites fail basic WCAG contrast requirements, averaging 29.6 instances of low-contrast text per homepage. That means nearly 4 out of 5 sites are failing the single most testable accessibility standard.
ADA website accessibility lawsuits surged 37% in the first half of 2025, with 2,014 cases filed in six months. These aren't targeting Fortune 500 companies. Small businesses, ecommerce shops, and startups with no accessibility policy are the primary defendants.
The European Accessibility Act went into effect on June 28, 2025, requiring digital services sold in the EU to meet accessibility standards. If you have European customers, this applies to you.
And here's the number that reframes the entire conversation: people with disabilities represent 16% of the global population. That's roughly 1.3 billion people. If your website excludes them, you're not just risking a lawsuit. You're ignoring a market segment larger than the population of Europe.
WCAG Compliance Levels: A, AA, and AAA
Most founders have heard "WCAG" but don't know which level they need. Here's the breakdown:
| WCAG A | WCAG AA | WCAG AAA | |
|---|---|---|---|
| What it covers | Bare minimum. Alt text for images, keyboard operability, no seizure-inducing content. | Everything in A, plus contrast ratios (4.5:1), text resizing up to 200%, consistent navigation. | Everything in AA, plus enhanced contrast (7:1), sign language for video, simplified reading levels. |
| Who it's for | No one should stop here. It's the floor, not the standard. | Most businesses and startups. This is the level referenced by ADA lawsuits and EU regulations. | Government agencies, healthcare, education. Aspirational for most commercial sites. |
| Legal relevance | Insufficient for most legal defenses. | The standard most courts and regulations reference. | Not legally required for commercial sites. |
| Practical recommendation | Skip it as a standalone target. | Aim here. It's achievable, defensible, and covers the issues that actually affect users. | Pursue selectively for high-impact items (enhanced contrast is easy; sign language for all video is not). |
The short answer: aim for WCAG AA. It's the standard courts reference, regulations require, and users benefit from. WCAG A alone won't protect you legally or functionally. WCAG AAA is excellent but impractical as a blanket target for a startup.
The 8-Point Website Accessibility Checklist
One checklist. Eight checks. Fifteen minutes. Each item includes what to check, the specific pass/fail threshold, and how to test it for free.
1. Color Contrast
Check: Is your body text contrast ratio at least 4.5:1 against its background? Is large text (18px bold or 24px regular) at least 3:1?
How to test: Use the WAVE accessibility tool or paste your hex codes into a free contrast checker like WebAIM's Contrast Checker.
Common failures: Light gray text on white backgrounds. Placeholder text in form fields. Colored buttons with white text that looks fine on your monitor but fails in sunlight or on low-quality screens.
Understanding how color choices affect conversions goes beyond aesthetics. If your users can't read it, they can't click it.
2. Text Size and Readability
Check: Is your body text at least 16px? Can users zoom to 200% without content breaking or overlapping?
How to test: Open your site, press Ctrl/Cmd + three times to reach 200% zoom. Check that no text is cut off, overlapping, or hidden behind other elements.
Common failures: Fixed-width containers that force horizontal scrolling at zoom. Text set in pixels that doesn't scale. Hero sections that collapse into unreadable stacks. Many of these overlap with the typography mistakes that hurt readability on startup sites.
3. Keyboard Navigation
Check: Can you reach every interactive element (links, buttons, form fields, menus) using only the Tab key? Can you activate them with Enter or Space? Is there a visible focus indicator showing where you are?
How to test: Put your mouse in a drawer. Open your homepage. Press Tab repeatedly. If you can't tell where focus is, or if you get trapped in a menu with no way to escape, you fail.
Common failures: Custom dropdown menus that only respond to mouse clicks. Modal popups with no keyboard close option. Focus indicators removed with outline: none in CSS because someone thought the blue ring was ugly. These issues frequently stem from the same navigation design mistakes that hurt all users.
4. Image Alt Text
Check: Does every meaningful image have descriptive alt text? Do decorative images have empty alt attributes (alt="")?
How to test: Right-click any image, select "Inspect," and look for the alt attribute. Or run WAVE, which flags every image missing alt text.
Common failures: Logo images with alt text that says "logo" instead of "CompanyName home." Product screenshots with no alt text at all. Decorative background patterns described in detail (they should be silent to screen readers).
5. Form Labels and Error Handling
Check: Does every form input have a visible label (not just placeholder text)? Do error messages explain what went wrong and how to fix it? Are required fields marked before submission, not just after?
How to test: Tab through your signup or contact form using only a keyboard. Submit it empty. Do the error messages make sense without seeing the visual layout?
Common failures: Placeholder-only labels that disappear when you start typing. Error messages that say "Invalid input" without specifying which field. Forms that clear all fields on error, forcing users to start over. These are the same patterns covered in form design fixes that reduce friction.
6. Heading Structure
Check: Does your page use headings (H1, H2, H3) in a logical, sequential order? Is there exactly one H1? Do headings describe the content that follows?
How to test: Install the HeadingsMap browser extension, or run Lighthouse's accessibility audit. Check that headings don't skip levels (H1 to H3 with no H2).
Common failures: Using heading tags for visual styling instead of document structure. Multiple H1 tags. Skipping from H2 to H4 because H3 looked too big in the template. Screen readers use headings as a table of contents. If your heading structure is broken, blind users can't navigate your page.
7. Link Text Clarity
Check: Does every link describe where it goes? No "click here," "read more," or "learn more" without context.
How to test: Read your links out of context (screen readers often list all links on a page). If a link says "here" or "this," a screen reader user has no idea where it leads.
Common failures: Blog post cards where the only link text is "Read more" repeated twelve times. CTAs that say "Learn more" in three different sections, each pointing somewhere different.
8. Touch and Tap Target Sizes
Check: Are all clickable elements at least 44x44 pixels? Is there enough spacing between targets that users won't accidentally tap the wrong one?
How to test: Check your site on a phone. Try tapping close-set navigation links or small icon buttons with your thumb. If you miss on the first try, your targets are too small.
Common failures: Tiny social media icons in the footer. Close-set text links in navigation menus. "X" buttons on modals that require surgical precision. This directly connects to your mobile design audit checklist, where tap targets are one of the most common failures.
Free Tools to Test Your Website Accessibility
You don't need to buy anything. Run these three tools and you'll catch 80% of automated accessibility issues:
WAVE (wave.webaim.org): The most visual accessibility checker available. Paste your URL and it overlays errors, warnings, and structural elements directly on your page. Free. Takes 30 seconds.
axe DevTools (browser extension): More technical than WAVE but catches different issues. Install the Chrome extension from Deque, open DevTools, click the axe tab, and scan. It explains each issue with a link to the relevant WCAG criterion.
Lighthouse Accessibility Audit: Built into Chrome DevTools. Open DevTools, go to Lighthouse, check "Accessibility," and run the audit. But be aware that Lighthouse only catches about 30% of accessibility issues. A score of 100 does not mean your site is accessible. If you've read about why a perfect Lighthouse score isn't enough, you know automated scores have blind spots. The same principle applies here: these tools catch the measurable stuff. They miss design judgment calls like confusing layouts, unclear visual hierarchies, and inconsistent interaction patterns.
SiteCritic scores color and contrast as one of 8 design dimensions in its critique, catching the design-layer accessibility issues that automated scanners overlook. It won't replace a full WCAG audit, but it fills the gap between "Lighthouse says 100" and "a real designer would flag this."
Website Accessibility and SEO: The Overlap Most Founders Miss
Here's the motivation boost if legal risk alone doesn't move you: many accessibility fixes directly improve your search rankings.
The overlap is structural. Search engine crawlers and assistive technologies parse the same signals:
- Alt text helps Google understand your images and helps screen readers describe them.
- Heading hierarchy (H1, H2, H3 in order) gives search engines a content outline and gives screen reader users a way to navigate.
- Semantic HTML (using
<nav>,<main>,<button>instead of generic<div>for everything) tells both crawlers and assistive tech what each element does. - Page speed improvements from optimized images and clean code benefit accessibility and Core Web Vitals simultaneously.
The W3C's business case for accessibility documents that organizations improving accessibility see measurable traffic and engagement gains. You're not doing two separate projects. You're doing one project that pays off in two directions.
Common Accessibility Questions Founders Ask
Can I get sued for an inaccessible website?
Yes. ADA Title III has been interpreted by courts to cover websites, and 2,014 lawsuits were filed in the first six months of 2025 alone. Small businesses are frequent targets. Having a documented accessibility policy and demonstrable WCAG AA compliance is your strongest defense.
Do I need WCAG AA or AAA for my startup?
Aim for WCAG AA. It's the level referenced by most regulations (including ADA case law and the EU Accessibility Act), it's achievable without a specialist, and it covers the issues that actually block users. Pursue AAA selectively for high-impact, low-effort items like enhanced contrast ratios.
Does accessibility affect my conversion rate?
Directly. Inaccessible forms lose signups. Low-contrast text loses readers. Missing alt text loses context. Research from the Nielsen Norman Group consistently shows that accessibility improvements benefit all users, not just those with disabilities. Clearer labels, larger tap targets, and better contrast improve usability across the board.
Are AI-built websites accessible?
Rarely by default. Most AI website builders optimize for visual appeal, not semantic structure or WCAG compliance. They produce gorgeous layouts with missing alt text, broken heading hierarchies, and contrast failures baked in. If you've built with an AI tool, you need to audit manually. This is one of several reasons AI website builders produce generic designs that look polished but underperform on the fundamentals.
How often should I audit accessibility?
After every significant design change, template swap, or content restructure. At minimum, run a quarterly check with WAVE or axe. Accessibility isn't a one-time checkbox. It's ongoing maintenance, just like security updates or performance monitoring.
Start With One Pass
You don't need to fix everything today. Run WAVE on your homepage. Count the contrast errors. Fix the worst ones. That single action puts you ahead of 79% of websites on the internet.
Then work through the rest of the checklist. One section at a time. The 8-point audit above is designed to be completed in 15 minutes, and the fixes for most issues take less time than the audit itself.
Want to see how your site scores across all 8 design dimensions, including accessibility? Paste your URL into SiteCritic and get a scored, timestamped critique in under a minute. It won't replace a full WCAG audit, but it will show you exactly where your design is failing the people trying to use it.