Understanding ADA requirements for your website doesn't require a law degree or a developer. This portal breaks down WCAG 2.1 Level AA in plain language, walks you through free audit tools, explains the most common violations, and helps you understand the real legal landscape.
WCAG stands for Web Content Accessibility Guidelines. It's a technical standard published by the W3C — not a law itself, but the standard courts and the Department of Justice point to when evaluating ADA compliance for websites.
Level AA is the middle tier. Level A covers the most basic requirements. Level AAA is the highest, and often impractical for general commercial websites. Level AA is where the legal and practical expectations for small business websites sit.
The guidelines organize around four principles: content must be Perceivable, Operable, Understandable, and Robust. Every specific requirement flows from one of those four ideas.
Read the Full BreakdownEach topic is written for people who run a business — not for developers or attorneys. Plain language throughout.
Several browser-based tools can scan your site at no cost and generate a report of potential issues. WAVE, Axe DevTools, and Google Lighthouse are three widely used options. Each has a different interface and level of detail. We explain what each tool shows, what the output means, and which issues to address first.
Learn how to auditMissing image alt text, poor color contrast, unlabeled form fields, and broken keyboard navigation appear in a large share of accessibility complaints. Many of these can be corrected through your website's content management system without writing a single line of code. We walk through each one with specific steps.
See the violations listFederal courts have handled thousands of ADA website accessibility cases. The outcomes vary considerably based on jurisdiction, business size, and the nature of the alleged barrier. We review publicly documented cases to give you a factual picture of what has happened — without offering legal advice or predictions.
Review the legal landscapeAccessibility overlay tools promise to fix your site automatically. Some aspects of that claim hold up. Others don't — and in documented cases, overlays have made the experience worse for users who rely on assistive technology. We explain what overlays can and can't do so you can make an informed decision.
Understand overlaysADA website accessibility lawsuits have been filed against businesses of many sizes. Small businesses have not been exempt. The Americans with Disabilities Act, passed in 1990, was written before the modern web existed — which has created genuine legal ambiguity that courts continue to work through.
The Department of Justice issued guidance in 2022 affirming that web accessibility is covered under Title III of the ADA. That guidance doesn't carry the force of a formal regulation, but it signals the direction of federal interpretation.
For a small business owner, the practical question isn't whether the law is settled — it isn't, fully — but whether taking reasonable steps toward accessibility makes sense. Understanding what those steps are is the starting point.
Covers places of public accommodation. Courts have increasingly applied this to websites operated by businesses with physical locations — and in some circuits, to online-only businesses as well.
The Department of Justice clarified in March 2022 that web accessibility requirements apply under the ADA, pointing to WCAG as the relevant technical standard without mandating a specific version.
Accessible websites work better for everyone — users with slow connections, older adults, people using mobile devices in bright sunlight, and people with situational limitations alongside those with permanent disabilities.
No account required for any of these. Open your browser, paste your URL, and get a report.
WebAIM's WAVE tool overlays visual indicators directly on your page — red icons for errors, yellow for alerts. It's the most visually intuitive option for non-technical users. Available as a browser extension for Chrome and Firefox.
Deque's free Axe extension for Chrome integrates with developer tools. It reports issues with zero false positives — every flagged item is a genuine violation. Useful for understanding the technical cause behind each problem.
Built into Chrome DevTools under the Audits tab. Generates a score from 0 to 100 for accessibility alongside performance and SEO. The score alone isn't a compliance determination, but it surfaces specific issues with explanations.
A free desktop application from TPGi that lets you pick any two colors on your screen and instantly see the contrast ratio. Useful for checking text against backgrounds without needing to run a full audit. Available for Windows and macOS.
Automated tools catch roughly a third to a half of accessibility issues. Manual testing — including keyboard navigation and screen reader testing — is needed for a complete picture. We explain how to do both.
Accessibility complaints tend to cluster around a small set of issues. Knowing what they are means you can check for them directly, even before running a formal audit.
Images without descriptive text are invisible to screen readers. Decorative images need empty alt attributes. Informational images need meaningful descriptions.
WCAG requires a 4.5:1 contrast ratio for normal text and 3:1 for large text. Light gray text on white backgrounds is a frequent failure.
Every interactive element — links, buttons, form fields, menus — must be reachable and usable with a keyboard alone. Custom dropdown menus and modal dialogs are common problem areas.
Placeholder text inside a field is not a label. When focus enters the field, the placeholder disappears. Screen reader users need a persistent, programmatically associated label element.
Many common violations can be fixed directly in WordPress, Squarespace, or Wix without touching code.
This is educational context drawn from publicly available court records and DOJ guidance. It is not legal advice. For advice specific to your situation, consult a qualified attorney.
Federal circuits disagree on whether a website must have a connection to a physical place of public accommodation to fall under Title III. The Ninth and Eleventh Circuits have taken different positions. This matters because the outcome of a case can depend significantly on where the business is located.
A notable pattern in ADA web accessibility litigation involves plaintiffs filing large numbers of cases with similar complaints. Courts have responded differently — some have dismissed cases for lack of standing, others have proceeded to settlement or judgment. The pattern itself is documented in court filings and legal journalism.
Many accessibility disputes begin not with a lawsuit but with a demand letter. These letters allege specific barriers on a website and request remediation or a settlement payment. Receiving one does not automatically mean litigation will follow, but understanding what they typically contain helps business owners respond appropriately with counsel.
One of the most cited cases in this area. The Ninth Circuit ruled in 2019 that Domino's Pizza's website and app must comply with the ADA. The court noted that WCAG provides a reasonable technical standard, though it declined to mandate a specific version. The case is frequently referenced in legal discussions about website accessibility obligations.