''' I remember the first time I got a demand letter. It was for one of my early companies, and the letter was about website accessibility. My first thought? "Is this even real?" My second was a cold shot of panic. Lawyers, lawsuits, and a legal maze I knew nothing about. It was a painful, expensive, and distracting lesson in something I wish I had understood from day one: The Americans with Disabilities Act (ADA) isn't just for brick-and-mortar stores. It's for your website, too.
And most founders are completely in the dark. I was.
Over the years, I’ve seen dozens of my portfolio companies get hit with the same kind of letter. It’s a rite of passage nobody wants. The legal landscape around website accessibility is a minefield, and the plaintiffs' lawyers know it. They have bots that crawl the web looking for non-compliant sites, and they fire off demand letters like a machine gun. For an early-stage startup, this can be an extinction-level event.
This isn't another dry, legal-jargon-filled post. This is the guide I wish I had when I was starting out. It’s a founder's-eye view of ADA compliance, stripped of the nonsense and focused on what you actually need to do to protect your business.
What is Website Accessibility, Really?
Let's cut through the noise. Website accessibility means that people with disabilities can use your website. This includes people who are blind, deaf, have motor impairments, or cognitive disabilities. They might use screen readers, special keyboards, or other assistive technologies to browse the web. If your site isn '''s not built for them, you’re effectively putting up a “closed” sign.
Think about it this way: would you build a physical office with no ramp for wheelchairs? Of course not. Your website is your digital office. The same principle applies.
Why This Matters More Than You Think
Let's get real. The primary reason most founders start paying attention to this is the threat of a lawsuit. And it's a very real threat. The number of website accessibility lawsuits has exploded in recent years. We're talking thousands of cases filed every year. These aren't just targeting big corporations; small startups are prime targets because they're often seen as easy payouts.
A typical demand letter will ask for something like $20,000 to $50,000 to settle. And that's just the settlement. Your legal fees will be on top of that. For a bootstrapped startup, that's a huge hit. It can mean missing payroll or cutting back on your product roadmap. It’s a massive, unnecessary distraction.
But here's the thing: this isn't just about avoiding lawsuits. It's about building a better product and a better business.
- Expanding Your Market: Over 60 million Americans have a disability. That's a huge potential market you're ignoring if your site isn't accessible. These are customers with real purchasing power.
- Improving Your SEO: Many of the principles of website accessibility, like clear headings, alt text for images, and clean code, are also best practices for SEO. Google rewards accessible websites.
- Building a Better Brand: Being inclusive isn't just a buzzword. It's a reflection of your company's values. Building an accessible product shows that you care about all of your users. That's a powerful message to send.
The Legal Landscape: A Founder's TL;DR
I'm not a lawyer, and this isn't legal advice. But I can give you the founder's-level summary of the legal situation. The ADA was passed in 1990, long before the internet was a thing. The law itself doesn't explicitly mention websites. This has created a legal gray area that lawyers have been exploiting for years.
The Department of Justice (DOJ) has repeatedly stated that the ADA applies to websites, but they haven't issued clear, binding regulations on what that means. In the absence of clear rules, courts have been left to decide. And their decisions have been all over the map.
So what are we supposed to do? The generally accepted standard is the Web Content Accessibility Guidelines (WCAG). Think of WCAG as the technical rulebook for website accessibility. It's a set of guidelines developed by the World Wide Web Consortium (W3C), the main international standards organization for the Internet.
There are different versions and levels of WCAG. The current standard is WCAG 2.1, and there are three levels of conformance: A, AA, and AAA. For most businesses, the target is WCAG 2.1 Level AA. This is the standard that is most often cited in legal cases and settlements.
Your Action Plan: A Step-by-Step Guide
Okay, enough with the theory. Let's get into what you actually need to do. Here's a simple, actionable plan for getting your website on the right track.
1. Get an Audit
You can't fix what you don't know is broken. The first step is to get a clear picture of where your website stands. There are a few ways to do this:
- Automated Tools: There are a number of free and paid tools that can scan your website and identify accessibility issues. These are a good starting point, but they're not perfect. They can only catch about 30% of potential issues. Some popular tools include WAVE, axe, and Siteimprove.
- Manual Audit: This is where a human expert goes through your website, using assistive technologies like screen readers to identify issues that automated tools miss. This is more thorough and more expensive, but it's the only way to get a complete picture.
- Hybrid Audit: This is the approach I recommend for most startups. It combines automated scanning with a manual review of your key pages and user flows. It's a good balance of cost and thoroughness.
When you get your audit report, don't panic. It's probably going to be a long list of issues. That's normal. The key is to prioritize.
2. Prioritize and Create a Roadmap
Not all accessibility issues are created equal. Some are critical, while others are minor. You need to work with your team to prioritize the issues from your audit and create a roadmap for fixing them. I recommend a simple priority system:
- P1 (Critical): These are issues that completely block a user from completing a key task, like signing up or checking out. These need to be fixed immediately.
- P2 (High): These are issues that create significant barriers for users but don't completely block them. These should be fixed in the next 1-2 sprints.
- P3 (Medium): These are issues that create a poor user experience but don't prevent users from completing tasks. These can be addressed over the next few months.
- P4 (Low): These are minor issues that have a low impact on the user experience. These can be backlogged and addressed when you have time.
Your roadmap should be a living document. It should be part of your regular product planning process.
3. Fix the Issues
This is where the rubber meets the road. Your engineering team needs to start working through the prioritized list of issues. Here are some of the most common issues I see:
- No Alt Text for Images: Every image on your site needs descriptive alt text so that screen reader users know what the image is.
- Poor Color Contrast: The text on your site needs to have enough contrast with the background so that people with low vision can read it.
- No Keyboard Navigation: Users should be able to navigate your entire site using only a keyboard. This is critical for users with motor impairments.
- Unclear Link Text: Links that just say "click here" are useless for screen reader users. The link text should be descriptive of where the link goes.
- Inaccessible Forms: Forms need to have clear labels and error messages that are accessible to screen readers.
These are just a few examples. The WCAG guidelines are long and technical. Your developers will need to spend some time learning the ropes. There are a ton of great resources online to help.
4. Write an Accessibility Statement
An accessibility statement is a public document that shows your commitment to accessibility. It should include:
- A statement of your policy and commitment.
- The accessibility standard you're targeting (e.g., WCAG 2.1 AA).
- The steps you're taking to improve accessibility.
- Contact information for users to report issues.
This is a simple but powerful step. It shows that you're taking this seriously, and it can be a huge help if you do get a demand letter. It shows that you're acting in good faith.
5. Train Your Team
Accessibility isn't just a one-time fix. It needs to be part of your company culture. Your entire team—designers, developers, and content creators—needs to be trained on the basics of accessibility. It should be part of your onboarding process for new hires.
When your team understands the "why" behind accessibility, they'll be more motivated to build accessible products from the start. This is how you make accessibility part of your DNA.
This is a Marathon, Not a Sprint
I know this sounds like a lot. And it is. But you don't have to do it all at once. The key is to start. Make a commitment. Create a plan. And start making progress, one step at a time.
Don't let the fear of a lawsuit be your only motivation. Do it because it's the right thing to do. Do it because it will make your product better. And do it because it will make your business stronger.
I've been through the fire on this one. I've paid the lawyers. I've dealt with the distraction. And I've come out the other side with a deep appreciation for why this matters. My hope is that this guide can help you avoid some of the pain I went through. Now go build something great, for everyone. '''
Frequently Asked Questions
Is this guide based on real experience?
Every recommendation in this guide comes from direct experience, either from building and selling my own companies, or from patterns I've observed across 200+ angel investments. I don't write about things I haven't personally tested.
Who is this guide designed for?
This guide is written for founders and operators who want practical, actionable advice rather than theoretical frameworks. Whether you're just starting out or scaling an existing business, the principles here apply across stages.
How should I work through this guide?
Don't try to absorb everything in one sitting. Read through once to get the big picture, then go back and work through each section as it becomes relevant to your current challenges. Bookmark it and return to it regularly.
How often is this guide updated?
I revisit and update my guides regularly as I learn new things and as the market evolves. The core principles tend to stay stable, but specific tactics and tools get refreshed based on what's working right now.