Complete Guide to ADA & WCAG Compliance
Everything you need to know about making your website accessible and legally compliant.
Everything you need to know about making your website accessible and legally compliant.
Web accessibility means designing and developing websites so that people with disabilities can use them effectively. This includes people who are blind or have low vision, people who are deaf or hard of hearing, people with motor impairments who cannot use a mouse, and people with cognitive disabilities who may need content presented in specific ways.
Accessibility is not just about compliance or avoiding lawsuits, though those are valid concerns. Accessible websites are better websites for everyone. The principles that make sites usable for people with disabilities also make them easier to use on mobile devices, faster to load, more compatible with different browsers, and easier for search engines to index.
Consider how accessibility features benefit all users:
According to the CDC, 1 in 4 U.S. adults has a disability. That's 61 million potential customers. Beyond market reach, accessible websites typically have better SEO, lower bounce rates, and higher conversion rates because they're simply easier for everyone to use.
The Americans with Disabilities Act (ADA) was signed into law in 1990 to prohibit discrimination against people with disabilities. Title III of the ADA requires that "places of public accommodation" be accessible. While the law predates the modern internet, courts have consistently held that websites qualify as places of public accommodation.
The ADA does not explicitly mention websites or specify technical standards. However, the Department of Justice has repeatedly affirmed that websites must be accessible under Title III. In 2022, the DOJ issued guidance confirming that "the ADA's requirements apply to all the goods, services, privileges, or activities offered by public accommodations, including those offered on the web."
This applies to virtually any business website:
Website accessibility lawsuits have increased dramatically over the past decade. In 2023, over 4,000 ADA website accessibility lawsuits were filed in federal court alone, and many more are settled before litigation. Any business with a website can be targeted, regardless of size.
ADA website lawsuits typically settle for $10,000 to $150,000 or more, plus attorney fees. This doesn't include the cost of actually fixing the website, which is required as part of most settlements. Proactive accessibility is almost always less expensive than reactive remediation.
While the ADA doesn't specify technical standards, courts and settlement agreements consistently reference WCAG (Web Content Accessibility Guidelines) as the benchmark. Most settlements require conformance with WCAG 2.1 Level AA within 6 to 12 months. Understanding and following WCAG is the most practical way to reduce your legal risk.
WCAG stands for Web Content Accessibility Guidelines. It is an international standard developed by the World Wide Web Consortium (W3C), the same organization that develops HTML and CSS standards. WCAG provides specific, testable criteria for making web content accessible.
WCAG 2.0 (2008) established the foundational accessibility requirements that are still relevant today. It introduced the four principles (Perceivable, Operable, Understandable, Robust) and three conformance levels (A, AA, AAA).
WCAG 2.1 (2018) added 17 new success criteria addressing mobile accessibility, low vision, and cognitive disabilities. This is currently the most commonly referenced version in legal contexts.
WCAG 2.2 (2023) is the latest version, adding 9 new criteria with a focus on users with cognitive disabilities and improved mobile experiences. Each version is backward compatible: meeting 2.2 means you also meet 2.1 and 2.0.
Level A is the minimum level of conformance. It addresses the most critical barriers that would completely prevent users from accessing content. Examples include providing text alternatives for images and ensuring functionality works with a keyboard.
Level AA is the recommended level for most organizations and is what legal settlements typically require. It includes all Level A criteria plus additional requirements like sufficient color contrast, resize support, and consistent navigation.
Level AAA is the highest level of conformance. It includes some requirements that may not be feasible for all content, such as sign language interpretation for audio and enhanced contrast ratios. Most organizations aim for AA with AAA where practical.
Target WCAG 2.2 Level AA conformance. This meets current legal expectations and positions you well for future requirements. Our scanner tests against WCAG 2.2 AA criteria to help you identify gaps.
WCAG is organized around four principles, often referred to by the acronym POUR. Understanding these principles helps you think about accessibility holistically rather than just checking boxes.
Information and user interface components must be presentable in ways users can perceive. This means content cannot rely solely on a single sense (like vision) to be understood.
User interface components and navigation must be operable. Users must be able to interact with all controls and navigate all content regardless of how they interact with their computer.
Information and the operation of the user interface must be understandable. Users must be able to comprehend both the content and how to use the interface.
Content must be robust enough to be interpreted reliably by a wide variety of user agents, including assistive technologies.
While WCAG contains dozens of success criteria, a handful of issues account for the majority of accessibility barriers. Addressing these issues will significantly improve your site's accessibility.
Images without alternative text are the single most common accessibility issue. Screen readers cannot describe images to blind users without alt text. Every meaningful image needs descriptive alt text that conveys its purpose. Decorative images should have empty alt attributes (alt="") so screen readers skip them.
Text that doesn't contrast enough with its background is difficult or impossible to read for users with low vision or color blindness. WCAG requires a contrast ratio of at least 4.5:1 for normal text and 3:1 for large text. Tools can measure contrast ratios automatically.
Form inputs without properly associated labels leave users guessing what information to enter. Each input needs a label element with a "for" attribute matching the input's "id". Placeholder text is not a substitute for labels.
Many users cannot use a mouse and rely on keyboards to navigate. All interactive elements must be reachable and usable with only a keyboard. Custom widgets built with JavaScript often fail this requirement.
Headings (H1, H2, H3, etc.) create a navigable outline of the page. Screen reader users often navigate by jumping between headings. Pages should have a logical heading hierarchy without skipping levels (like jumping from H1 to H4).
Links with text like "click here" or "read more" don't tell users where the link goes. Screen reader users often navigate by listening to a list of links, so each link should make sense out of context. Use descriptive text that explains the link's destination.
Every page needs a unique, descriptive title element. Page titles are announced by screen readers when pages load and appear in browser tabs and bookmarks. Missing or generic titles make navigation difficult.
Effective accessibility testing combines automated scanning with manual testing. Neither approach is sufficient on its own.
Automated tools like our scanner can quickly identify many common issues: missing alt text, insufficient contrast, missing labels, invalid ARIA, and similar technical problems. Automated testing is fast, consistent, and can be integrated into development workflows.
However, automated tools can only catch about 30-40% of accessibility issues. They cannot determine whether alt text is actually meaningful, whether tab order is logical, or whether content makes sense when read linearly. Automated testing is a starting point, not a complete solution.
Manual testing involves actually using your website the way users with disabilities would:
Run automated scans whenever you make significant changes. Monthly scans help catch regressions. Manual testing should happen during development of new features and periodically for comprehensive review.
When you find accessibility issues, prioritize them by impact rather than trying to fix everything at once.
Fix issues that completely block access first. This includes keyboard traps (users can get into something but not out), missing form labels that prevent form submission, and interactive elements that don't work with assistive technology.
Address issues that significantly impair usage. Missing alt text on important images, insufficient contrast on body text, and missing page titles fall into this category. These don't completely block access but make the site very difficult to use.
Handle issues that cause friction but don't block usage. Examples include heading structure problems, low contrast on less critical elements, and missing skip links. These improve the experience significantly but aren't immediate blockers.
Finally, address issues that represent best practices rather than strict requirements. This might include enhanced focus indicators, additional ARIA landmarks, or improved error messaging.
Keep records of your accessibility testing and remediation efforts. This documentation can be valuable if you ever face legal action, as it demonstrates good faith effort toward compliance. Track what issues you found, when you fixed them, and any ongoing accessibility work.
Now that you understand the fundamentals of web accessibility, here's how to move forward:
Accessibility is not a one-time project but an ongoing commitment. By understanding these fundamentals and implementing regular testing, you can create a website that works for everyone while reducing your legal risk.
Get your free accessibility report in under 60 seconds.
Run Free Scan Explore Resources