In 2023, over 4,600 website accessibility lawsuits were filed in the US — a record. The businesses named weren’t all large corporations. Small retailers, restaurants, service businesses, and healthcare providers were targeted. Most had no idea their websites had a legal exposure until they received a demand letter.
Website accessibility is not just a good-faith effort to serve users with disabilities. For many businesses, it’s a compliance requirement with real legal consequences.
What Website Accessibility Actually Means
Accessibility in the web context means that people with disabilities can perceive, understand, navigate, and interact with your website. That includes users who are:
- Blind or have low vision (using screen readers, braille displays, or zoom)
- Deaf or hard of hearing (relying on captions for video content)
- Motor-impaired (using keyboard navigation instead of a mouse)
- Cognitively impaired (needing clear language, consistent navigation, and no time-out pressure)
An accessible website works for all of these users without requiring them to use workarounds. It also works better for everyone: search engine crawlers, users on slow connections, users on mobile devices, and users in bright sunlight who can’t see low-contrast text.
The Legal Framework: ADA, Section 508, and State Laws
The Americans with Disabilities Act (ADA) doesn’t mention websites explicitly — it was written in 1990, before the web existed. But Title III, which prohibits discrimination by “places of public accommodation,” has been consistently interpreted by courts as applying to websites and mobile apps.
The Department of Justice finalized a rule in 2024 explicitly requiring websites of state and local governments to meet WCAG 2.1 Level AA. For private businesses, the DOJ has confirmed that the ADA requires web accessibility, but hasn’t set a specific technical standard by rule. Courts have applied WCAG as the functional standard in ADA lawsuits.
Section 508 applies explicitly to federal agencies and contractors. If your business receives federal funding or contracts with federal agencies, Section 508 compliance is a direct contractual requirement.
State laws add another layer. California’s Unruh Civil Rights Act extends ADA protections and allows private lawsuits. New York’s Human Rights Law has been used in web accessibility cases. Florida has seen significant activity around accessibility litigation targeting small businesses.
The practical result: if your business serves the public through its website — which means virtually any business with an online presence — you have legal exposure from web accessibility failures.
WCAG: The Technical Standard
Web Content Accessibility Guidelines (WCAG) are developed by the World Wide Web Consortium (W3C) and define specific technical criteria for accessibility. The current operative version is WCAG 2.1. WCAG 2.2 was published in 2023 with additional criteria.
WCAG organizes requirements into three levels:
- Level A: The minimum. Sites that fail Level A criteria have fundamental barriers for users with disabilities.
- Level AA: The standard used in most regulations and court decisions. This is the target for compliance.
- Level AAA: The highest standard, typically impractical to achieve across an entire site.
When people refer to “WCAG compliance,” they mean WCAG 2.1 Level AA unless specified otherwise.
The Most Common Accessibility Failures on Business Websites
These are the issues that appear most frequently in accessibility audits and in accessibility lawsuit demand letters:
Missing alt text on images. Screen readers read alt text aloud to describe images to blind users. An image with no alt text is invisible to that user. An image with alt text that says “image001.jpg” is worse — it tells the user nothing while wasting their time.
Low color contrast. WCAG requires a contrast ratio of at least 4.5:1 for normal text and 3:1 for large text (18pt+ or 14pt+ bold). Many design trends favor light gray text on white backgrounds, which frequently fails this ratio. Automated contrast checkers (like the free tool at webaim.org/resources/contrastchecker) can test your specific colors.
Forms without labels. Every form field — text inputs, dropdowns, checkboxes — must have a programmatic label that screen readers can announce. A placeholder inside the field doesn’t count; it disappears when the user starts typing.
No keyboard navigation. Users who can’t use a mouse must be able to navigate your entire site using only a keyboard (Tab, Shift+Tab, Enter, arrow keys). Dropdown menus that only open on hover, modal dialogs that trap keyboard focus, and custom interactive elements built without keyboard support all fail this requirement.
Videos without captions. Pre-recorded video with speech or audio content requires accurate captions. Auto-generated captions from YouTube are often inaccurate enough to fail the WCAG standard. Human-reviewed captions are the safe standard.
Missing page titles. Every page must have a descriptive title tag that identifies the page’s content. “Home” is inadequate. “Contact Us | Business Name” is acceptable.
No skip navigation link. Users navigating by keyboard must Tab through every navigation item on every page to reach the main content — unless a “Skip to main content” link is provided as the first focusable element. This is one of the most common failures.
How to Audit Your Site’s Accessibility
Three levels of audit, from fast to thorough:
Automated scan (5 minutes): Run your site through WAVE (wave.webaim.org), a free browser tool that identifies many WCAG violations. Automated tools catch about 30–40% of accessibility issues — useful for a quick baseline, but not sufficient for compliance validation.
Manual keyboard test (30 minutes): Navigate your entire site using only the Tab key. Can you reach every interactive element? Do you always know where focus is? Can you complete your contact form? Can you close any modal dialogs that open?
Screen reader test (1 hour): NVDA is a free screen reader for Windows. VoiceOver is built into Mac and iOS. Navigate your site with the screen reader running. Is every image described? Is every form field labeled? Does the reading order make sense?
A professional accessibility audit by a certified accessibility specialist (CPACC or WAS credential) is required for a defensible compliance position. These audits run $1,500–$5,000 depending on site size and complexity.
Accessibility Overlays: Why They Don’t Work
Accessibility overlay tools — AccessiBe, UserWay, AudioEye — inject JavaScript that attempts to automatically fix accessibility issues. They’re marketed as one-line-of-code compliance solutions.
They don’t work. Multiple studies, including research from accessibility specialists and user testing with actual screen reader users, have shown that overlays frequently make the experience worse for users with disabilities — adding noise, interfering with existing assistive technology, and creating new barriers while claiming to remove them.
More critically: courts have not accepted overlay tools as a defense against accessibility lawsuits. Businesses using overlays have been sued and lost.
The fix for accessibility problems is code changes — correct HTML structure, proper ARIA attributes, keyboard-accessible interactions. An overlay sitting on top of inaccessible code doesn’t fix the underlying HTML.
Building Accessible WordPress Sites
WordPress itself is largely accessible, but themes and plugins frequently are not. Common accessibility failures in WordPress themes include:
- Navigation menus that aren’t keyboard accessible
- Custom sliders and carousels built without ARIA roles
- Color schemes chosen for aesthetics without contrast ratio testing
- Form plugins that generate fields without proper label associations
- Modal dialogs that don’t manage focus correctly
Page builders compound these problems. Elementor and Divi generate deeply nested HTML with ARIA attributes that are frequently incorrect or missing. The flexibility that makes page builders visually appealing comes with a cost to semantic HTML structure that accessibility depends on.
A hand-coded WordPress theme built with accessibility as a specification produces semantically correct HTML, proper landmark regions, keyboard-accessible navigation, and correct ARIA implementation where needed. This is not difficult to build — it requires knowing what to build, not advanced technical skill. But it requires intentionality that most theme and page builder code lacks.
What to Do If You Receive a Demand Letter
Receiving an ADA website accessibility demand letter is stressful and time-sensitive. A few things to know:
First, don’t ignore it. Most demand letters have a 30–60 day response window. Ignoring them results in escalation to litigation, which is more expensive.
Second, engage accessibility-experienced legal counsel. ADA website litigation is a specialized field. A general business attorney without accessibility case experience may not know the current case law.
Third, begin remediation and document it. Courts have been more favorable to businesses that demonstrate active, good-faith remediation efforts — even if they were not fully compliant when the demand letter arrived.
Fourth, get a professional accessibility audit. A documented audit from a credentialed specialist establishes a baseline and guides remediation priority.
FAQ
Does my small business website need to be ADA compliant? If your business is subject to Title III of the ADA — which includes most businesses that serve the public — courts have consistently held that your website is covered. There is no small-business exemption in the case law.
What is the difference between WCAG 2.1 and WCAG 2.2? WCAG 2.2 adds nine new success criteria, focused primarily on cognitive accessibility and mobile interaction. WCAG 2.1 Level AA remains the most commonly referenced standard in regulation and litigation. WCAG 2.2 AA is backward compatible — a site meeting 2.2 AA also meets 2.1 AA.
How much does it cost to make a website accessible? For a site with moderate issues, remediation typically runs $2,000–$8,000. For a site with fundamental structural problems (no semantic HTML, page builder-generated content), rebuilding is often more cost-effective than patching. Ongoing accessibility maintenance to catch new content and features is an additional consideration.
Can I use an AI tool to fix my accessibility issues? AI tools can help identify issues and suggest code fixes, but they require human review. Accessibility requires understanding the user experience — context that automated tools frequently miss. Don’t publish AI-generated fixes without testing with actual assistive technology.
Does Google care about accessibility? Indirectly. Google’s crawler behaves similarly to a screen reader — it reads text, follows links, and interprets HTML structure. Accessibility best practices (semantic HTML, proper heading hierarchy, descriptive link text, alt text) are also SEO best practices. Better accessibility frequently correlates with better search performance.
Is a mobile site more or less accessible than a desktop site? Mobile accessibility has its own specific requirements — touch target size (minimum 24x24 CSS pixels), no requirement for hover states, proper zoom support. WCAG 2.2 added specific mobile-focused criteria. A site that’s accessible on desktop needs to be tested on mobile separately.
Accessibility built into a site’s foundation — as a specification, not an afterthought — costs far less than retrofitting a non-compliant site. Our custom WordPress development treats accessibility compliance as a build requirement: semantic HTML structure, keyboard navigation, contrast testing, and proper form labeling are standard output, not add-ons. Get started with a project conversation.