For many teams, the question comes up during a sales call, after a customer complaint, or when someone forwards a demand letter. Whether web accessibility is legally required depends on where you operate, what kind of organization you run, and who your users are. For most public-facing organizations, some obligation applies, and the legal pressure is growing.
Why Accessibility Laws Exist
Accessibility laws are fundamentally about equal access.
The internet is no longer optional infrastructure. People rely on websites and apps to apply for jobs, access healthcare, complete purchases, attend school, manage their finances, and communicate with businesses and government agencies.
When websites aren’t accessible, users can be blocked from completing those tasks independently. A checkout flow that doesn’t work with a keyboard can prevent someone from making a purchase. A form without labels may be unusable with a screen reader. Poor color contrast can make critical information unreadable. Accessibility laws exist because those aren’t minor inconveniences; they’re real barriers.
The Laws Most Commonly Referenced
Americans with Disabilities Act (ADA): United States
The ADA predates the modern web, so it doesn’t mention websites by name. But courts have consistently interpreted it as applying to digital experiences, particularly for businesses that serve the public, including retailers, healthcare providers, financial services, restaurants, hotels, and private schools.
Under Title III, which covers private businesses and nonprofits, there’s no specific technical standard written into regulation yet. In practice, courts and the Department of Justice use WCAG (Web Content Accessibility Guidelines) 2.1 Level AA as the benchmark. Settlements typically run $5,000–$75,000, plus attorney fees and remediation costs.
Under Title II, which covers state and local governments, a 2024 DOJ final rule explicitly requires WCAG 2.1 AA compliance. Deadlines depend on jurisdiction size: April 2027 for larger governments, April 2028 for smaller ones.
In 2025, roughly 3,100 federal web accessibility lawsuits were filed, a 27% increase over 2024. Most targeted small and mid-sized businesses that had no prior warning.
Section 508: U.S. Federal Agencies and Contractors
Section 508 of the Rehabilitation Act applies to federal agencies and organizations that receive federal funding or work with federal agencies. It requires websites, documents, software, and internal systems to be accessible. If your organization works with government agencies, Section 508 likely applies to your digital products.
European Accessibility Act (EAA)
The EAA became enforceable across EU member states on June 28, 2025. It covers e-commerce, banking, transport booking platforms, and other digital services, and it applies to any organization that sells to EU consumers, regardless of where the company is based. A US business serving European customers is subject to it.
The EAA references EN 301 549, which incorporates WCAG 2.1 Level AA. Penalties vary by member state: Germany can fine up to €100,000 per violation; France up to €20,000 per site per year.
The European Accessibility Act applies to any business selling to EU consumers, including companies based in the US or UK. There’s no geographic carve-out.
Other Countries
Canada’s Accessible Canada Act covers federally regulated organizations (banks, telecoms, broadcasters) with penalties up to CAD 250,000. Ontario’s AODA has required WCAG 2.0 AA compliance from large organizations since 2021. The UK’s Equality Act covers digital services, and public sector bodies must meet WCAG 2.1 AA under the Public Sector Bodies Accessibility Regulations. Australia has obligations under the Disability Discrimination Act.
The details vary, but the direction is consistent across jurisdictions: digital accessibility expectations are increasing, not shrinking.
This overview covers the laws most relevant to businesses operating in or selling to North American, European, and Anglophone markets. For a comprehensive country-by-country reference, Lainey Feingold maintains a global database of digital accessibility laws and policies.
Where WCAG Fits In
Most accessibility laws don’t specify technical requirements in detail. Instead, they point to (or courts apply) the Web Content Accessibility Guidelines (WCAG) as the standard for measuring compliance.
WCAG translates “accessible” into concrete criteria: sufficient color contrast, keyboard-navigable interfaces, properly labeled form fields, visible focus indicators, logical heading structure, and text alternatives for images. The current benchmark referenced by most laws is WCAG 2.1 Level AA. WCAG 2.2 was published in 2023 and is gradually being adopted, and if you’re undergoing a significant redesign, building to 2.2 AA now is the safer long-term choice.
Does This Apply to My Website?
Legally, the answer depends on context. A large public-facing company faces more scrutiny than a small personal site. Government agencies and regulated industries face stricter requirements.
But most public-facing organizations (businesses that serve customers, nonprofits, agencies, SaaS products) fall somewhere in scope. The only websites clearly outside these obligations are small personal sites and limited private intranets.
If you’re asking the question, the answer is probably yes.
Three Misconceptions Worth Clearing Up
“Only big companies need to worry.” Large organizations get more headlines, but smaller businesses receive demand letters and complaints too. ADA Title III applies to businesses of any size that serve the public, and there’s no small-business exemption.
“Accessibility means perfect compliance.” Websites change constantly: new content, new features, updated components. Accessibility is an ongoing process, not a checkbox you tick once. Courts and regulators generally look for good-faith effort and improvement over time, not perfection.
“An overlay widget fixes it.” Automated overlay tools promise instant compliance with minimal effort. They don’t deliver it. Accessibility requires actual structural improvements: semantic markup, keyboard support, proper labels, clear communication. A floating widget can’t substitute for that.
What to Actually Do
You don’t need to solve everything at once. Start by understanding where your accessibility issues are, especially in the user flows that matter most: navigation, forms, checkout, and core content pages.
Tools like AAArdvark’s automated accessibility scanner can give you a baseline: what’s failing, where, and how to prioritize fixes. Automated scanning catches roughly 30–40% of WCAG issues, including the most common ones, including missing labels, contrast failures, and missing alt text. Manual testing covers the rest.
The most common web accessibility problems repeat across almost every site. Fixing them won’t just reduce legal exposure; it makes your site easier to use for everyone.
Build accessibility into your workflow rather than treating it as a one-time audit. That’s the approach that holds up over time, both legally and in practice.