WCAG Compliance
Requirements, penalties, and how to check your website against Web Content Accessibility Guidelines / ADA Title III.
Test your website for WCAG compliance for free
Enter your domain to start a free scan and open an account - no integration required.
Does WCAG apply to my business?
Answer a few questions for an instant, plain-English read on whether Web Content Accessibility Guidelines / ADA Title III likely applies to you.
Answer a couple of questions to see whether web accessibility standards (WCAG, enforced in the US through ADA Title III) are likely to apply to your website.
This tool offers general guidance, not legal advice. Accessibility obligations can vary by jurisdiction - confirm with qualified counsel.
Who WCAG applies to
- In the US, business websites are widely treated as places of public accommodation under ADA Title III, with WCAG 2.1 AA as the de facto compliance standard.
- There is no revenue or size threshold - accessibility lawsuits target businesses of every size, and the majority target companies under $25 million in revenue.
- Accessibility obligations also arise from employment law, government contracting, and non-US laws such as the European Accessibility Act.
Common questions
- Does ADA website accessibility apply to small businesses?
- Yes. There is no size threshold. In fact the majority of website accessibility lawsuits target companies under $25 million in revenue, because they are less likely to have remediated their sites.
- Is WCAG legally required?
- WCAG itself is a technical standard, not a law, but US courts and regulators use WCAG 2.1 AA as the benchmark for whether a website meets ADA Title III, so in practice it is the requirement you are judged against.
Overview
The Web Content Accessibility Guidelines (WCAG) and ADA Title III aim to ensure that websites and digital content are accessible to individuals with disabilities. These regulations apply to all businesses that provide goods or services to the public, including private entities and non-profits.
Penalties
$75,000 first offense, $150,000 subsequent offenses (ADA Title III)
What Complyy checks
5 automated tests — 5 passive, 0 active
Passive (instant scan)
Images have descriptive alt text
WCAG 2.1 SC 1.1.1 requires text alternatives for non-text content so screen readers can convey meaning. Missing alt text is the single most-cited issue in ADA Title III website lawsuits.
Site is fully navigable by keyboard
SC 2.1.1 requires all functionality to be operable via a keyboard. Mouse-only menus, traps, and drag-only interactions block users of switch devices and screen readers.
Text has sufficient color contrast ratio (4.5:1 minimum)
SC 1.4.3 requires a 4.5:1 contrast ratio for normal text (3:1 for large text). Insufficient contrast is the most-cited automated-scan finding in demand letters.
All form fields have associated accessible labels
SC 3.3.2 requires every form input to have a programmatically associated label. Placeholder-only inputs are non-compliant because the label disappears on focus.
Skip navigation link present for screen readers
SC 2.4.1 requires a mechanism to bypass repeated content. A "Skip to main content" link as the first focusable element is the standard implementation expected by assistive-tech users.
Learn More About Web Content Accessibility Guidelines / ADA Title III
What is WCAG compliance?
The Web Content Accessibility Guidelines (WCAG) are a set of international standards established to ensure digital content is accessible to everyone, including individuals with disabilities. These guidelines are vital as they help organizations develop online interfaces that are usable by people with varying disabilities such as visual, auditory, physical, speech, cognitive, or neurological impairments. In production, WCAG compliance necessitates that websites are not only visually appealing but also functionally accessible. Businesses must adapt their online content to meet these requirements by implementing user-friendly navigation, providing text alternatives for non-text content, ensuring sufficient color contrast, and supporting assistive technologies.
WCAG 2.1 is divided into three levels of compliance: A, AA, and AAA, with each level representing a more advanced degree of accessibility. Level AA represents a standard typically recognized as the minimum benchmark for legal compliance. It's crucial for businesses to integrate accessibility features during the website's design and development stages, as retrofitting can be costly and may lead to legal challenges if compliance is not maintained.
Who must comply with WCAG?
WCAG guidelines apply broadly to any entity that manages or has a significant online presence, especially in regions like the United States, where access is covered under the Americans with Disabilities Act (ADA) Title III. Although WCAG itself is not a law, it provides the technical criteria that support legal compliance. Entities such as businesses, educational institutions, and public sector organizations are required to align their websites with these guidelines, regardless of size or revenue.
There are no specific thresholds for revenue or user-count that determine applicability. Instead, the applicability is overarching for any website that functions in a public capacity, meaning all websites should aim for at least Level AA compliance to safeguard against accessibility lawsuits. The burden of proof rests on the entity to demonstrate reasonable efforts have been made to comply with these guidelines.
Key requirements and obligations
Perceivable Information: Textual alternatives for all non-text content provide equivalent communication like braille, speech, symbols, or simpler language to accommodate diverse needs.
Operable User Interface: All web applications must remain functional through varied modalities including keyboards, with users having ample time to interact.
Understandable Information: Interface functionality must be straightforward and predictable, with clear navigation features guiding users seamlessly.
Robust Content: Compatibility with a wide array of assistive technologies, ensuring content is adaptable and remains accessible for people using technologies like screen readers.
Penalties and fines for non-compliance
Non-compliance with WCAG, as interpreted through ADA Title III, can result in significant fines and penalties. While the ADA does not specify exact fine values for web accessibility, legal action for non-compliance can lead to financial settlements ranging from approximately $20,000 to $100,000 per case. Businesses are not only liable to face fines directly but also bear reputational risks and the financial burden of legal fees and remediation costs, which can significantly exceed initial expenditures toward compliance.
Moreover, there is a possibility for private lawsuits from individuals who encounter accessibility barriers. This private right of action has led to an increase in litigation, making it essential for businesses to maintain compliance proactively to avoid costly legal disputes.
Any major amendment or closely related law
While WCAG itself remains a set of guidelines rather than legislation, a relevant legal framework is the ADA Title III, which mandates accessibility for disabled persons in the public sphere. Further, the "21st Century Communications and Video Accessibility Act" underscores the accessibility of digital media, ensuring users with disabilities have equivalent access to online communications technologies.
ADA Title III has increasingly been interpreted to include web accessibility, with numerous lawsuits affirming that web content should meet WCAG standards. There is ongoing legal evolution as courts continue to clarify the digital obligations of businesses under these statutory provisions.
How to check if your website is compliant
Checking for WCAG compliance involves multiple practical steps. Firstly, businesses should conduct periodic accessibility audits using automated tools that evaluate websites against WCAG criteria. Engaging users with disabilities for feedback and conducting manual testing using various assistive technologies such as screen readers can provide critical insights. Moreover, ensuring accessibility features are built into the development lifecycle can proactively sustain compliance.
Maintaining a compliance checklist based on Level AA recommendations assists businesses in achieving consistent results. Complyy tests these continuously from the outside and captures timestamped evidence to ensure ongoing adherence to guidelines.
Frequently asked questions
Who does WCAG apply to?
WCAG guidelines apply to any online content made available to the public, spanning businesses, educational institutions, and public sector organizations.
Does WCAG apply to small businesses or non-profits?
Yes, WCAG applies to small businesses and non-profits if they have a public-facing website, though applicability may vary based on region-specific legislation.
What are the penalties for not complying with WCAG?
Penalties for non-compliance can lead to legal settlements ranging from $20,000 to $100,000, not including additional legal fees and reputation damage.
What is the deadline to respond to a WCAG non-compliance request?
Deadlines are not explicitly defined under WCAG, but addressing accessibility issues promptly is advised to avoid legal consequences.
Who is exempt from WCAG compliance?
WCAG does not typically exempt any entities that publish online content for public access, though local laws may have specific exemptions.
How can I make my website compliant with WCAG?
Ensure your website includes features like text alternatives, keyboard navigation, clear structure, and proper color contrast, aligning with Level AA guidelines.
What are the key levels of WCAG compliance?
WCAG compliance is structured into three levels: A, AA, and AAA, with AA being the minimum recommended standard for most organizations.
Are there any amendments to WCAG?
WCAG 2.1 is an update to the pre-existing guidelines, enhancing accessibility but not changing the core structure established in earlier versions.
Recently Scanned Websites
Live compliance reports from Complyy's public directory.
Related WCAG articles
Insights and analysis from Complyy on WCAG compliance.

You Can't Buy ADA Compliance With a Widget. The FTC Just Put a Price on Proving It.
The FTC fined accessiBe $1 million over claims its overlay widget made websites ADA compliant. It doesn't - overlays sit on top of the same broken markup a screen reader still can't use. Here's what real accessibility testing looks like, and why a badge is not a defense.

Ensure Compliance with the European Accessibility Act
Learn how to prepare your audits for the European Accessibility Act to avoid potential legal pitfalls and ensure user inclusivity.

The Privacy Policy Was Perfect. The Website Fired 86 Trackers Before Consent
A children's brand with a textbook privacy policy scored 54/100 - because its live website fired 86 tracking cookies before consent, with no banner in sight. Here's the gap between what a policy promises and what a website does, and how to test your own.
The Platform
How Complyy enforces WCAG compliance
Complyy continuously tests your site against Web Content Accessibility Guidelines / ADA Title III using synthetic identities that behave exactly like regulators — and your customers.
Discover
We visit your website as a real user — finding your privacy policy, cookie banner, opt-out links, and contact details.
Scan & Test
Passive checks run instantly. Active agents sign up, submit deletion requests, and wait for responses — just like regulators do.
Score & Evidence
Every finding is timestamped, SHA-256 hashed, and RFC 3161 certified. Your compliance report is audit-ready from day one.
Why Complyy
The only platform that tests compliance the way regulators do
Real synthetic identities
We register actual accounts — adult and minor — on your platform. No theoretical checks. Real interactions, real evidence.
Active + passive tests
Most tools only check your privacy policy text. Complyy also submits DSAR requests, verifies deletion, and waits for real responses.
Court-admissible artifacts
Every screenshot, response, and timestamp is cryptographically sealed. Built for regulators, DPAs, and legal teams — not just developers.
4
Regulations monitored
19
Compliance tests
∞
Agentic identities
3 min
Avg. first evidence artifact
Is your company WCAG-compliant?
Get a free compliance scan in minutes. No credit card. No setup. Complyy visits your site, runs every test, and delivers a full evidence report.