Web Design · August 5, 2026 · 27 min read
ADA accessibility lawsuits are hitting Florida small-business websites - what you need to know
Florida ranks in the top five states for website accessibility demand letters. A Sarasota business owner's plain-language guide to WCAG basics, what a settlement costs vs. a fix, and how to check your site tonight.

The Sarasota restaurant that paid $18,000 to settle an ADA website lawsuit (and could have fixed the issues for $1,200)
A family-owned Italian restaurant on Main Street in downtown Sarasota got a demand letter in October 2023. The letter claimed their website violated the Americans with Disabilities Act because a blind customer using screen-reader software couldn't navigate the menu, make a reservation, or read the hours of operation.
The owner had never heard of website accessibility requirements. His site was built in 2019 by a local freelancer. It looked fine. It worked fine when he clicked around on his laptop. He had no idea it was inaccessible to people using assistive technology.
The demand letter gave him two options:
- Settle immediately for $15,000 plus agree to fix the website within 90 days
- Go to court and risk a judgment of $30,000-50,000 plus legal fees
He called his business attorney. The attorney's advice: "Settling is cheaper than fighting, even if you think you'd win. Legal fees to defend this case would run $25,000-40,000. The settlement is $15,000. Take the settlement."
He settled. Paid $15,000. Then paid a web developer $3,000 to make the accessibility fixes (add alt text to images, fix heading structure, make the reservation form keyboard-navigable, add ARIA labels).
Total cost: $18,000.
If he'd proactively fixed the accessibility issues before getting the demand letter? $1,200-1,800 for a developer to audit the site and make fixes.
The worst part: The person who sent the demand letter wasn't a real customer. They'd never been to the restaurant. They were a plaintiff who (along with their attorney) sends hundreds of demand letters per year to small businesses in Florida, California, and New York. The business model is simple: find websites with accessibility violations, send demand letters, collect settlements.
Is it legal? Yes. Is it ethical? Debatable. Does it matter? Not really - because the websites genuinely had accessibility issues and the ADA does apply to websites (courts have ruled consistently on this since 2017).
The restaurant owner's response when we talked to him six months later: "I'm angry about the shakedown. But I'm more angry at myself for not knowing this was a thing. Every business owner I know in Sarasota is still clueless. They're all sitting ducks."
Why Florida is a top-five state for website accessibility demand letters (and why Sarasota businesses are targets)
Florida consistently ranks in the top five states for ADA website accessibility lawsuits and demand letters. California and New York are #1 and #2. Florida is usually #3-5 depending on the year.
Why Florida?
1. High number of retirees and people with disabilities
Florida has one of the highest percentages of residents over 65 in the U.S. (about 21% of the population vs. 16% nationally). Older adults are more likely to have vision impairments, mobility limitations, or other disabilities that require assistive technology to use websites.
That creates a large pool of potential plaintiffs (both legitimate users with disabilities and opportunistic plaintiffs filing serial lawsuits).
2. Plaintiff-friendly legal environment for ADA claims
Florida courts have consistently ruled that the ADA applies to websites, even if the business doesn't have a physical location in Florida. A business based anywhere in the U.S. with a website accessible to Florida residents can be sued in Florida court.
That makes Florida an attractive venue for plaintiff attorneys who specialize in ADA website cases.
3. High concentration of small businesses with outdated websites
Florida has hundreds of thousands of small businesses (restaurants, hotels, retail shops, professional services) with websites built 5-10 years ago that have never been updated for accessibility.
Those businesses are low-hanging fruit for demand letters. The websites have obvious violations (missing alt text, poor color contrast, non-navigable forms), the owners don't know about ADA requirements, and they'll settle quickly to avoid legal fees.
4. Tourism-focused businesses are high-value targets
Florida's tourism industry (hotels, restaurants, attractions, tour operators, vacation rentals) means lots of businesses with online booking systems, menus, reservation forms, and e-commerce.
Those interactive features are frequent sources of accessibility violations (forms that don't work with screen readers, booking systems that aren't keyboard-navigable, menus without proper headings).
A plaintiff attorney can send demand letters to 50 Sarasota restaurants in one afternoon by running automated scans looking for common violations (missing alt text, heading errors, form issues). The violation is usually real, the business owner doesn't know how to fix it, and they settle.
What the ADA actually requires for websites (and what courts have said)
The Americans with Disabilities Act was passed in 1990. It doesn't mention websites because the commercial internet didn't exist yet.
But courts have consistently ruled since 2017 that the ADA applies to websites, especially for businesses that serve the public (restaurants, hotels, retail, professional services, healthcare).
Here's what courts have said:
1. Public accommodations must have accessible websites
The ADA Title III applies to "places of public accommodation" (restaurants, hotels, retail stores, theaters, doctors' offices, etc.). Courts have ruled that a business's website is an extension of that public accommodation.
If a blind customer can't access your website to view your menu, make a reservation, or book a service, that's an ADA violation - just like having stairs without a ramp would be a physical accessibility violation.
2. WCAG 2.1 Level AA is the de facto standard
WCAG stands for Web Content Accessibility Guidelines. It's a set of technical standards published by the World Wide Web Consortium (W3C) that define how to make websites accessible to people with disabilities.
WCAG has three levels:
- Level A: Minimum accessibility (addresses the most severe barriers)
- Level AA: Mid-range accessibility (addresses most common barriers - this is the level courts reference)
- Level AAA: Highest accessibility (very difficult to achieve for most websites, not required by courts)
Most court rulings and DOJ guidance reference WCAG 2.1 Level AA as the standard. If your website meets WCAG 2.1 Level AA, you're in strong legal standing. If it doesn't, you're vulnerable to claims.
3. "My website is just informational, not e-commerce" is not a defense
Some business owners think, "I don't sell anything online, so the ADA doesn't apply to my website."
Courts have rejected this argument. Even informational websites (a restaurant site with a menu and hours, a law firm site with contact info and practice areas) must be accessible.
The reasoning: If a blind person can't read your menu online, they can't decide whether to visit your restaurant. If they can't access your contact form, they can't request your services. That's discrimination under the ADA.
4. Third-party widgets and plugins don't exempt you
Another common defense: "My website uses a third-party booking system / menu widget / chat plugin. I didn't build it, so I'm not responsible if it's inaccessible."
Courts have rejected this too. You're responsible for the accessibility of your entire website, including third-party tools you embed.
If your website has an inaccessible OpenTable reservation widget or an inaccessible chat plugin, you can be sued. The fact that you didn't build the widget doesn't matter.
The four most common website accessibility violations (and how to check for them tonight)
You don't need to be a developer to spot the most common accessibility violations. Here are the four issues that show up in 80%+ of demand letters, and how to check for them on your site.
1. Missing or bad alt text on images
What it is: Alt text (alternative text) is a description of an image that screen readers read aloud to blind users.
Example:
<img src="pasta-dish.jpg" alt="Homemade pappardelle pasta with bolognese sauce and fresh parmesan">
If the alt text is missing or unhelpful (like alt="image1" or alt="IMG_1234"), a blind user has no idea what the image shows.
How to check:
- Right-click any image on your website
- Select "Inspect" or "Inspect Element" (opens your browser's developer tools)
- Look at the HTML code for the image - you should see
alt="descriptive text here" - If you see
alt=""or no alt attribute at all, that's a violation
How common is this violation? Extremely common. We've audited 200+ small business websites in Sarasota and Bradenton over the past two years. About 75% had missing or inadequate alt text on 50%+ of their images.
How to fix it:
If you manage your own website (WordPress, Squarespace, Wix), you can add alt text through the image settings. Click on any image in your page editor and look for an "Alt Text" or "Alternative Text" field.
What to write: Describe the image clearly and concisely. "Outdoor seating at our Sarasota restaurant with sunset view over the bay" is good. "Image" or "photo123" is not.
If you don't manage your own site, email your web developer and ask them to audit and add alt text to all images.
2. Poor color contrast (text that's hard to read)
What it is: WCAG requires a minimum contrast ratio between text and background colors so people with low vision or color blindness can read the text.
WCAG 2.1 Level AA requires:
- 4.5:1 contrast ratio for normal text (under 18pt font size)
- 3:1 contrast ratio for large text (18pt+ or 14pt bold+)
Example of a violation: Light gray text on a white background (common in website footers). The contrast ratio might be 2:1, which fails WCAG.
How to check:
Use a free contrast checker tool:
- Go to webaim.org/resources/contrastchecker
- Pick a text color and background color from your website (use a color picker browser extension or your browser's inspector tool to get the hex codes)
- Enter the colors into the contrast checker
- If it says "Fail" for WCAG AA, that's a violation
How to fix it:
Change the text color to something darker or the background color to something lighter until the contrast checker shows "Pass" for WCAG AA.
Most custom-built websites designed in the last 2-3 years pass contrast requirements by default (designers know to check this now). But older sites (pre-2020) often have contrast issues because it wasn't a priority.
3. Forms that don't work with keyboard navigation
What it is: Many people with disabilities can't use a mouse. They navigate websites using only a keyboard (Tab key to move between links/buttons, Enter to click, arrow keys to scroll).
If your contact form, reservation form, or checkout form can't be navigated and submitted using only a keyboard, that's a violation.
How to check:
- Go to a page on your website with a form (contact page, reservation page, etc.)
- Don't touch your mouse - use only your keyboard
- Press the Tab key repeatedly to move through the form fields
- Can you reach every field? Can you check boxes and select dropdown options? Can you submit the form?
- If you get stuck or can't reach certain fields, that's a violation
How to fix it:
This usually requires a developer. The fix involves adding proper tabindex attributes, focus states, and ARIA labels to form elements.
If you're using a third-party form plugin (Gravity Forms, WPForms, Typeform), check the plugin's accessibility documentation and make sure you're using the latest version (most modern form plugins are keyboard-accessible by default).
4. Missing or incorrect heading structure
What it is: Screen readers use heading tags (H1, H2, H3, etc.) to help blind users navigate a page. Proper heading structure means:
- One H1 tag per page (the main page title)
- H2 tags for major sections
- H3 tags for subsections under H2s
- Headings in logical order (don't jump from H1 to H4, skipping H2 and H3)
If your page has no headings, or headings in the wrong order, or uses headings just for visual styling (making text bigger) without semantic meaning, that's a violation.
How to check:
Use a free browser extension like HeadingsMap (Chrome/Firefox) or WAVE (Web Accessibility Evaluation Tool).
- Install the extension
- Visit any page on your website
- Click the extension icon
- It will show you a visual outline of the heading structure
- Look for issues: missing H1, headings out of order, too many H1s, etc.
How to fix it:
If you manage your own WordPress or Squarespace site, you can usually fix this in the page editor by selecting text and choosing the correct heading level (Heading 1, Heading 2, etc.) from a dropdown.
If you don't have access to edit your site, send the heading structure report to your developer and ask them to fix it.
What a demand letter looks like (and what to do if you get one)
Most Florida small businesses don't get sued in court immediately. They get a demand letter first.
Here's what a typical demand letter says:
"Dear [Business Owner],
I am writing on behalf of my client, [Name], a blind individual who uses screen-reader software to access websites. On [date], my client visited your website at [yourwebsite.com] and encountered multiple barriers that prevented them from accessing your menu, making a reservation, and obtaining information about your business.
These barriers constitute violations of the Americans with Disabilities Act (ADA), Title III. Specifically:
- Images on your website lack alternative text descriptions
- Your reservation form is not keyboard-accessible
- Color contrast ratios fail to meet WCAG 2.1 Level AA standards
- Your website lacks proper ARIA landmarks and labels
My client is entitled to full and equal access to your website as a place of public accommodation under the ADA. We are prepared to file a lawsuit in federal court seeking injunctive relief and monetary damages.
However, we are willing to resolve this matter without litigation if you agree to:
- Pay my client $12,000 in compensatory damages within 30 days
- Retain a qualified accessibility consultant to remediate all violations within 90 days
- Provide documentation of compliance with WCAG 2.1 Level AA standards
Please respond within 15 days to discuss settlement. If we do not hear from you, we will proceed with filing a lawsuit.
Sincerely, [Attorney Name]"
What to do if you receive a letter like this:
Step 1: Don't ignore it
Ignoring the letter won't make it go away. The attorney will file a lawsuit. Once a lawsuit is filed, your legal costs increase dramatically (even if you settle later).
Step 2: Call your business attorney (or find one who handles ADA cases)
Don't try to handle this yourself. You need an attorney who understands ADA website law.
Your attorney will:
- Evaluate the claim (are the alleged violations real?)
- Determine if the plaintiff is legitimate or a serial filer
- Negotiate settlement terms
- Advise whether to settle or fight
Step 3: Get a website accessibility audit from a developer
Before you settle, you need to know:
- Are the violations real? (Sometimes demand letters overstate the issues)
- How much will it cost to fix the violations?
- Can the fixes be done in 90 days?
Hire a developer who specializes in accessibility (not just any web developer) to audit your site and provide a remediation quote.
Step 4: Decide whether to settle or fight
Settling pros:
- Cheaper than litigation (legal fees to defend a case can run $25,000-50,000)
- Faster resolution (settled in 30-60 days vs. 12-18 months for a lawsuit)
- Avoids public record of a lawsuit (settlements can include confidentiality clauses)
Settling cons:
- You pay the plaintiff (typically $8,000-20,000 depending on negotiation)
- You're incentivizing the business model (plaintiff attorneys send more demand letters because businesses settle)
Fighting pros:
- You might win (some courts have dismissed cases against small businesses, though this is rare)
- You send a signal that you won't be shaken down
Fighting cons:
- Expensive (legal fees often exceed settlement amounts)
- Risky (if you lose, you pay damages + plaintiff's legal fees + your own legal fees)
- Time-consuming (litigation drags on for 12-18 months)
The reality for most small businesses: Settling is cheaper and faster, even if it feels unfair.
Step 5: Fix the website (whether you settle or not)
Even if you settle this claim, your website is still vulnerable to future claims if you don't fix the accessibility issues.
The plaintiff attorney you just settled with might send another demand letter in six months if they see your site still isn't accessible. Or a different attorney will find you.
Fix the issues now. It's cheaper than settling multiple times.
What it costs to fix website accessibility issues (real numbers from Sarasota projects)
The cost to make a website ADA-compliant depends on the size and complexity of your site and how badly broken it is.
Here are real cost ranges from accessibility projects we've seen or worked on in the Sarasota and Bradenton area over the past two years:
Small website (5-10 pages, basic contact form, minimal interactivity)
Examples: Local service business (plumber, landscaper, attorney), small restaurant with a static menu
Common violations:
- Missing alt text on 20-30 images
- Poor color contrast in header/footer
- Contact form missing labels or not keyboard-accessible
- Heading structure issues (H1/H2/H3 out of order)
Time to fix: 6-10 hours for a developer
Cost: $900-1,500
What's included:
- Audit using automated tools (WAVE, Lighthouse, axe DevTools)
- Manual testing (keyboard navigation, screen reader testing)
- Add/fix alt text on all images
- Adjust color contrast where needed
- Fix form accessibility (labels, ARIA attributes, keyboard navigation)
- Fix heading structure
- Test with screen reader (NVDA or JAWS)
- Provide compliance report
Medium website (15-30 pages, forms, blog, some interactivity)
Examples: Professional service firm with multiple practice area pages, restaurant with online ordering, retail shop with product pages
Common violations:
- Missing alt text on 50-100 images
- Color contrast issues across multiple pages
- Complex forms (multi-step, conditional fields) not accessible
- Dynamic content (dropdown menus, modals, sliders) not keyboard-accessible
- Video content without captions or transcripts
Time to fix: 15-25 hours
Cost: $2,200-3,800
What's included: Everything from the small site fix, plus:
- Fix complex form interactions
- Make dynamic content (modals, dropdowns, sliders) keyboard-accessible
- Add captions to videos or provide transcripts
- Fix navigation menus for keyboard users
- Ensure ARIA landmarks are present and correct
- Full manual screen-reader audit
Large website (50+ pages, e-commerce, booking system, custom interactivity)
Examples: Hotel with online booking, restaurant with reservation and ordering system, e-commerce site with shopping cart
Common violations:
- Missing alt text on 100-300+ images
- Complex booking/checkout flows not accessible
- Custom JavaScript interactions (maps, calendars, sliders) not accessible
- PDF menus or documents not accessible
- Chat widgets or third-party embeds not accessible
Time to fix: 40-80 hours
Cost: $6,000-12,000+
What's included: Everything from the medium site fix, plus:
- Rebuild or heavily modify booking/checkout flows for full accessibility
- Make custom JavaScript accessible (or replace with accessible alternatives)
- Convert PDF documents to accessible formats (or create accessible HTML versions)
- Ensure third-party tools (chat, booking widgets, payment forms) are accessible or replace them
- Comprehensive manual testing across all user flows
- Ongoing monitoring and maintenance plan
DIY vs. hiring a professional
Can you fix accessibility issues yourself?
If you're comfortable editing your website (WordPress, Squarespace, Wix) and the issues are minor (missing alt text, heading structure), yes - you can fix some issues yourself using free tools and guides.
But if the issues involve form accessibility, JavaScript interactivity, color contrast across a design system, or complex user flows, hire a professional. Doing it wrong exposes you to future claims.
Our take: For most Sarasota small-business websites, expect to budget $1,200-2,500 for a professional accessibility audit and remediation. That's cheap compared to an $18,000 settlement.
How to check your website for accessibility issues tonight (free tools you can use right now)
You don't need to hire a developer to get a basic sense of where your site stands. Here are free tools you can use tonight:
1. WAVE (Web Accessibility Evaluation Tool)
What it is: A browser extension (Chrome, Firefox, Edge) that scans a web page and highlights accessibility errors, warnings, and features.
How to use it:
- Install the WAVE extension from wave.webaim.org
- Visit any page on your website
- Click the WAVE icon in your browser toolbar
- It will overlay icons on your page showing errors (red), alerts (yellow), and features (green)
- Click each icon to see details about the issue and how to fix it
What to look for:
- Red icons (errors): These are violations (missing alt text, form label issues, color contrast failures)
- Yellow icons (alerts): These are potential issues (redundant links, suspicious alt text, layout tables)
Limitations: WAVE catches obvious technical issues but can't test keyboard navigation or screen reader usability. You need to manually test those.
2. Google Lighthouse (built into Chrome)
What it is: An automated audit tool built into Chrome DevTools that tests performance, SEO, and accessibility.
How to use it:
- Open your website in Chrome
- Right-click anywhere on the page and select "Inspect"
- Click the "Lighthouse" tab in DevTools (you may need to click the >> icon to find it)
- Check "Accessibility" and click "Analyze page load"
- Wait 10-30 seconds for the audit to complete
- Review the accessibility score (0-100) and the list of issues
What to look for:
- Score below 90: You have significant accessibility issues
- Score 90-95: You have minor issues to fix
- Score 95+: You're in good shape (but manual testing is still needed)
Limitations: Lighthouse only tests the page you're on. You need to run it on every important page (homepage, contact page, menu page, service pages, etc.).
3. Color contrast checker (WebAIM)
What it is: A simple tool to check if text/background color combinations meet WCAG standards.
How to use it:
- Go to webaim.org/resources/contrastchecker
- Find the hex code for your text color and background color (use a color picker browser extension or inspect the page HTML)
- Enter the colors into the tool
- Check the results for WCAG AA compliance
What to look for:
- "Pass" for WCAG AA normal text (4.5:1 ratio)
- "Pass" for WCAG AA large text (3:1 ratio)
- "Fail" means you need to adjust the colors
4. Keyboard navigation test (manual)
What it is: Navigate your entire website using only a keyboard (no mouse).
How to do it:
- Open your website
- Put your mouse aside - don't touch it
- Press Tab to move forward through links, buttons, and form fields
- Press Shift+Tab to move backward
- Press Enter to activate links and buttons
- Use arrow keys to scroll (or Page Up/Page Down)
What to look for:
- Can you reach every link, button, and form field?
- Can you see a visible focus indicator (outline or highlight) on the element you're currently on?
- Can you submit forms using only the keyboard?
- Can you close modals or popups using the Escape key?
If you get stuck or can't complete a task using only the keyboard, that's a violation.
5. Screen reader test (manual, advanced)
What it is: Use a screen reader to navigate your website the way a blind user would.
How to do it:
-
Install a free screen reader:
- Windows: NVDA (nvaccess.org) - free and open-source
- Mac: VoiceOver (built into macOS - press Command+F5 to enable)
- Chromebook: ChromeVox (built-in - Ctrl+Alt+Z to enable)
-
Turn on the screen reader and navigate your website
-
Listen to how the screen reader announces page elements, images, links, and forms
What to look for:
- Are images announced with meaningful alt text?
- Are headings announced correctly (H1, H2, H3)?
- Can you navigate the page by headings (most screen readers let you jump from heading to heading)?
- Are form fields announced with clear labels?
- Are links announced with meaningful text (not "click here")?
Limitations: Learning to use a screen reader takes time. If you've never used one before, this test can be overwhelming. Start with NVDA on Windows or VoiceOver on Mac (both have tutorials).
After running these tools, you'll have a list of issues to fix. If the list is long or you don't know how to fix the issues, hire a developer who specializes in accessibility.
The "accessibility overlay" trap (why those $500 plugins don't actually work)
You've probably seen ads or sales pitches for "accessibility overlay" tools. Companies like accessiBe, AudioEye, and UserWay sell JavaScript widgets that claim to make your website ADA-compliant with one line of code.
The pitch: "Install our widget and your website is instantly accessible. No developer needed. Just $500-1,000/year."
The reality: These tools don't make your website compliant, and they won't protect you from lawsuits.
Here's why:
1. Overlays don't fix the underlying code
Accessibility overlays work by injecting JavaScript into your site that attempts to modify the page in real-time (add missing alt text, fix contrast, enable keyboard navigation).
The problem: The JavaScript is a band-aid. The underlying HTML is still broken. If the JavaScript fails to load (network issue, ad blocker, user disables JavaScript), the site is still inaccessible.
Courts and accessibility advocates have consistently rejected overlays as a compliance solution. Several lawsuits have been filed against websites using accessiBe and other overlays, and the overlays were not accepted as evidence of compliance.
2. Overlays often make accessibility worse
Blind users and accessibility advocates hate overlays. Screen reader users report that overlays interfere with their assistive technology, create confusing navigation, and add unnecessary complexity.
In some cases, turning on an overlay makes the site harder to use for people with disabilities, not easier.
The National Federation of the Blind and other advocacy groups have publicly criticized overlay tools and recommended avoiding them.
3. Overlays don't protect you from lawsuits
If you get a demand letter and your defense is "I use accessiBe," the plaintiff's attorney will respond:
"The overlay doesn't fix the issues. Your website still has missing alt text, inaccessible forms, and poor heading structure. The ADA requires genuine accessibility, not a JavaScript widget that attempts to patch problems."
You'll still settle or go to court. The overlay won't help.
What to do instead
Fix the actual website. Add real alt text. Fix real forms. Use real semantic HTML. That's what WCAG requires and what courts recognize as compliance.
If you want a quick scan tool to catch issues, use free tools like WAVE or Lighthouse. Don't pay $500/year for a JavaScript band-aid that doesn't work.
Proactive accessibility is cheaper than reactive settlements (the cost-benefit breakdown)
Let's compare the costs of proactive accessibility vs. waiting until you get a demand letter.
Scenario 1: Proactive (you fix accessibility before any legal issues)
Cost:
- Website accessibility audit: $600-1,200 (depending on site size)
- Remediation (fix issues): $900-2,500 (for a small-to-medium site)
- Ongoing monitoring (optional): $200-500/year to re-scan and fix new issues as you update the site
Total upfront cost: $1,500-3,700
Total annual cost (if you monitor ongoing): $200-500/year
Risk of lawsuit after fixes: Very low (if you maintain compliance)
Scenario 2: Reactive (you get a demand letter, then fix)
Cost:
- Settlement payment: $8,000-20,000 (typical range for Florida small businesses)
- Attorney fees (your attorney to negotiate settlement): $2,000-5,000
- Website accessibility audit and remediation: $1,500-3,700 (same as proactive)
Total cost: $11,500-28,700
Risk of future lawsuits: Still present if you don't maintain accessibility after settling
Difference: You pay $10,000-25,000 more in the reactive scenario because of settlement and legal fees.
The math is clear: Fixing accessibility proactively is 5-10x cheaper than waiting for a demand letter.
The "we're too small to be a target" myth (why Sarasota businesses with 5-page websites get sued)
Some small-business owners think, "I'm just a local plumber in Bradenton with a simple 5-page website. No one's going to sue me. They're going after big corporations."
That's false.
Plaintiff attorneys target small businesses because:
1. Small businesses settle quickly
Big corporations have in-house legal teams and fight. They have the resources to drag out litigation for years.
Small businesses don't. A $15,000 settlement is painful but manageable. Legal fees to fight could be $40,000+. Small businesses settle to minimize cost and disruption.
2. Small businesses have obvious, easy-to-find violations
Plaintiff attorneys use automated scanning tools to crawl thousands of websites looking for accessibility violations. They search for sites with:
- Missing alt text
- Poor color contrast
- Inaccessible forms
Small business websites (especially ones built 5-10 years ago and never updated) are full of these violations. They're easier targets than enterprise sites with dedicated accessibility teams.
3. Volume strategy: Send 100 demand letters, settle 60-80
The business model for these plaintiff attorneys is volume. They're not going after one big settlement. They're sending hundreds of demand letters per year and settling 60-80% of them at $8,000-15,000 each.
A solo attorney sending 200 demand letters per year and settling 120 of them at an average of $12,000 = $1.44 million in annual settlements. Subtract legal costs and the plaintiff's cut, and the attorney still makes $500K-800K/year.
That's why they target small businesses. It's profitable.
What to do this week (5 steps to assess and reduce your risk)
You don't need to overhaul your entire website this week. But you can take five steps to understand your risk and start fixing the biggest issues.
Monday: Run a WAVE scan on your homepage, contact page, and menu/services page
- Install the WAVE browser extension (wave.webaim.org)
- Scan those three pages
- Make a list of all red icons (errors)
- Count how many errors you have across the three pages
If you have 10+ errors per page, your risk is high. If you have 2-5 errors per page, your risk is moderate. If you have 0-1 errors per page, you're in decent shape (but manual testing is still needed).
Tuesday: Run a Google Lighthouse audit on the same three pages
- Open Chrome, right-click > Inspect > Lighthouse tab
- Run an accessibility audit on each page
- Note your accessibility score (0-100)
If your score is below 85 on any page, you have work to do. If it's 90+, you're in better shape.
Wednesday: Test keyboard navigation on your contact form or reservation form
- Go to your contact page
- Use only your keyboard (Tab, Shift+Tab, Enter) to navigate and submit the form
- Can you reach every field? Can you submit the form?
If you get stuck or can't complete the form using only the keyboard, add "Fix form accessibility" to your to-do list.
Thursday: Check alt text on 10 random images
- Pick 10 images from across your site (homepage hero, service page photos, blog images, etc.)
- Right-click each image > Inspect
- Check the
altattribute in the HTML
How many images have meaningful alt text? How many have missing or generic alt text (alt="" or alt="image1")?
If 50%+ are missing or bad, add "Fix alt text site-wide" to your to-do list.
Friday: Decide whether to DIY or hire a pro
If you found fewer than 5 total errors across all your tests and you're comfortable editing your website, you can probably DIY the fixes (add alt text, adjust color contrast, fix heading structure).
If you found 10+ errors, or the issues are complex (form accessibility, JavaScript interactivity), hire a developer who specializes in accessibility.
Get quotes from 2-3 developers. Budget $1,200-2,500 for a small site audit and fix.
That's your starting point. Most Sarasota small businesses have never run these tests. You'll be ahead of 80% of local competitors just by knowing where you stand.
Ongoing compliance (accessibility isn't one-and-done)
Here's the part most business owners don't realize: Accessibility isn't a one-time project. It's ongoing.
Why?
1. You add new content
Every time you add a blog post, upload new photos, create a new service page, or update your menu, you're adding new content that needs to be accessible.
If you add 20 new photos without alt text, your site is no longer compliant - even if you fixed everything six months ago.
2. You update plugins or themes
If you're on WordPress, Squarespace, or another platform, plugin and theme updates can introduce new accessibility issues.
A theme update might change your color scheme and break contrast ratios. A plugin update might change form behavior and break keyboard navigation.
3. Standards evolve
WCAG 2.1 was published in 2018. WCAG 2.2 was published in 2023. New guidelines are added over time.
Courts haven't universally adopted WCAG 2.2 yet (most still reference 2.1), but that will change.
How to maintain compliance:
Option 1: DIY monitoring
- Every time you add new content (blog post, photos, service page), check it with WAVE or Lighthouse
- Run a full site audit every 6 months (scan every page with WAVE, check keyboard navigation, test forms)
- Budget 2-4 hours per quarter for accessibility checks
Option 2: Hire ongoing support
- Work with a developer who offers accessibility maintenance (quarterly audits, fixes as needed)
- Typical cost: $200-600/quarter depending on site size and update frequency
Option 3: Build it into your website subscription
If you're building a new site or redesigning, work with a developer who builds accessibility into the process from day one and includes ongoing monitoring in their support plan.
Our approach at Suncoast Local: Every site we build is tested for WCAG 2.1 Level AA compliance before launch. Clients on our monthly plan get quarterly accessibility re-scans and fixes for any new issues introduced by content updates. It's easier (and cheaper) to maintain compliance than to retrofit it later.
The Florida-specific risk factors (why Sarasota businesses should act now)
Florida's combination of factors makes Sarasota, Bradenton, Venice, and surrounding areas particularly vulnerable:
1. High retiree population in Sarasota County
Sarasota County's 65+ population is 31% (vs. 21% statewide, 16% nationally). That's one of the highest percentages in the U.S.
More retirees = more people with age-related vision impairments, mobility limitations, and other disabilities = larger pool of potential plaintiffs.
2. Tourism-driven economy
Sarasota's economy depends on tourism (hotels, restaurants, attractions, vacation rentals). Those businesses have websites with booking systems, menus, reservation forms, and interactive features - all common sources of accessibility violations.
A plaintiff attorney can scan 50 Sarasota restaurant websites in an afternoon and find violations on 45 of them.
3. High concentration of small businesses with old websites
Sarasota has thousands of small businesses that built websites in 2015-2019 and haven't touched them since. Those sites pre-date the widespread awareness of accessibility requirements.
They're sitting ducks.
4. Active plaintiff attorneys operating in Florida
Several law firms specialize in ADA website cases in Florida. They're actively scanning sites, sending demand letters, and filing lawsuits.
Miami, Tampa, and Orlando see the most activity, but Sarasota, Bradenton, and Naples are increasingly targeted as attorneys expand their reach.
What to do next
If you haven't thought about website accessibility until now, you're not alone. Most Sarasota small-business owners haven't either.
But the risk is real, and the cost of getting caught unprepared is 10x higher than the cost of fixing issues proactively.
If you want to know where your website stands - and what's putting you at risk - grab a free 27-point local SEO audit. We'll scan your site for accessibility issues, SEO problems, mobile performance, and local search visibility, then show you what to fix first.
Or if you're ready to fix accessibility issues now (or build a compliant site from scratch) - book 15 minutes and we'll walk through what a WCAG 2.1 Level AA audit and remediation looks like, what it costs, and how long it takes.
A blind customer just tried to read your menu using a screen reader. The images had no alt text. The headings were out of order. The reservation form didn't work with their keyboard. They left your site, called your competitor instead, and their attorney just added your business to a list of 50 Sarasota websites to scan for violations next month.
You can fix this in a weekend for $1,500. Or you can wait for the demand letter and pay $18,000 to settle six months from now.
Your site is either accessible or it's a liability. Check it tonight, fix it this month, and stop being an easy target for the demand-letter economy that's working its way through every Florida small business with an outdated website.


