Probably not yet. According to WebAIM’s annual analysis of the top one million home pages, around 95% have detectable WCAG failures. The safest target for any business is WCAG 2.2 Level AA, reached through real design and code fixes plus manual testing, not overlay widgets.
Website accessibility used to be treated as a nice-to-have. Today it is a legal, commercial and ethical requirement. Around one in four adults in the US reports some form of disability, according to the CDC. That is a large share of every market, and many people with disabilities use screen readers, keyboard navigation, magnification or voice control to browse.
When a website blocks them, businesses lose customers. Increasingly, they also face demand letters, lawsuits and regulatory action. This guide explains the rules in the US, UK, Canada and EU, the most common failures, and a practical plan to make your website genuinely accessible.
This article is general information, not legal advice. If you have received a demand letter or lawsuit, contact a lawyer experienced in accessibility law promptly.
What Is WCAG, and Which Level Do You Need?
The Web Content Accessibility Guidelines (WCAG), published by the W3C, are the global benchmark for web accessibility. They are organised around four principles: content must be Perceivable, Operable, Understandable and Robust (POUR).
- WCAG 2.1 (2018) added mobile, low-vision and cognitive criteria.
- WCAG 2.2 (October 2023) added criteria such as focus not obscured, minimum target size, dragging alternatives, accessible authentication and consistent help.
- Level AA is the level referenced by most laws and settlements. Level AAA is aspirational for most sites.
Aim for WCAG 2.2 AA. It satisfies WCAG 2.1 AA and 2.0 AA requirements as well, so one target covers most legal frameworks.
What Are the Accessibility Laws by Country?
| Jurisdiction | Key law or rule | What it means for websites |
|---|---|---|
| United States: private businesses | Americans with Disabilities Act (ADA), Title III | Courts have often applied it to websites of public-facing businesses; plaintiffs typically cite WCAG AA. State laws such as California’s Unruh Act can add damages. |
| United States: state and local government | DOJ ADA Title II rule (2024) | WCAG 2.1 AA required, with compliance dates in April 2026 for larger entities and April 2027 for smaller ones and special districts. |
| United States: federal agencies | Section 508 | Federal websites and procured technology must be accessible. |
| United Kingdom | Equality Act 2010; Public Sector Bodies Accessibility Regulations 2018 | Service providers must make reasonable adjustments. Public sector sites must meet WCAG AA and publish accessibility statements. |
| Canada: Ontario | AODA, Integrated Accessibility Standards | Public sector and organisations with 50+ employees must meet WCAG 2.0 AA for public websites (with limited exceptions). |
| Canada: federal | Accessible Canada Act | Applies to federally regulated sectors such as banking, telecoms and transport, with planning and reporting duties. |
| European Union | European Accessibility Act, applying from 28 June 2025 | Many consumer products and services, including ecommerce and banking, must be accessible. This affects US, UK and Canadian companies selling into the EU. |
What Are the Most Common Accessibility Failures?
- Low colour contrast between text and background.
- Missing alternative text on meaningful images.
- Empty or vague links and buttons, such as icon buttons without labels or repeated “Click here”.
- Form fields without labels and unclear error messages.
- Keyboard traps and invisible focus indicators.
- Missing document language and poor heading structure.
- Inaccessible menus, modals and carousels built without proper ARIA and focus management.
- Videos without captions and audio without transcripts.
- PDFs that are scanned images rather than tagged documents.
Most accessibility failures are not exotic. They are the same ten mistakes repeated on millions of websites, which means most of them are fixable.
Do Accessibility Overlays Make You Compliant?
Overlay widgets promise one-line-of-code compliance. They do not fix the underlying code. Many disability advocates and accessibility professionals oppose them, and businesses using overlays continue to be sued. In 2025, the US Federal Trade Commission finalised an order requiring overlay provider accessiBe to pay $1 million over claims that its product could make any website compliant.
Instead of an overlay, invest in fixing your templates. Because most websites reuse a header, footer, navigation and a handful of page templates, fixing those components often resolves a large share of issues across every page at once.
How Do You Make Your Website Accessible?
1. Audit
- Run automated scans (such as WAVE, axe or Lighthouse) to catch obvious issues quickly. Automated tools find only part of WCAG failures.
- Test manually with a keyboard only: can you reach and use everything?
- Test with screen readers such as NVDA, JAWS, VoiceOver and TalkBack.
- Prioritise key user journeys: navigation, search, contact forms, booking and checkout.
2. Fix by impact
- Blockers in checkout, forms and navigation.
- Global components: header, menus, footer, buttons and modals.
- Content issues: alt text, headings, link text and contrast.
- Media and documents: captions, transcripts and tagged PDFs.
3. Prevent regressions
- Add accessibility checks to design reviews and development pipelines.
- Train content editors on alt text, headings and links.
- Choose accessible themes, plugins and third-party widgets.
4. Publish an accessibility statement
Explain your conformance target, known limitations and how users can request help or report problems. In the UK public sector, a statement is mandatory, and it is good practice everywhere.
A regional dental group receives a demand letter citing a contact form without labels, low-contrast buttons and a booking widget that keyboard users cannot operate. The group’s developer fixes the form labels and button styles in the shared template, replaces the booking widget with an accessible alternative, adds captions to its videos, and publishes an accessibility statement with a phone alternative. The remediation is documented with before-and-after test results, which supports the legal response and, more importantly, lets patients book on their own.
What Are the Business Benefits of Accessibility?
- A larger market, including older customers with changing vision and dexterity.
- Better SEO: headings, alt text, captions and clean HTML help search engines and AI systems understand content.
- Higher conversions: clearer forms and buttons help everyone.
- Lower legal risk and stronger procurement eligibility for government and enterprise contracts.
- Brand trust and alignment with ESG and inclusion commitments.
Use Cases
- Ecommerce stores selling to the US and EU under ADA risk and the European Accessibility Act.
- Healthcare providers whose patients include many people with disabilities.
- Local governments and contractors facing the DOJ Title II deadlines.
- Ontario businesses with 50+ employees under AODA.
- Universities and training providers with documents, video and portals.
Accessibility Approaches Compared
| Approach | Effectiveness | Legal protection | Cost over time |
|---|---|---|---|
| Overlay widget only | Low | Weak | Recurring fees, unresolved issues |
| Automated scanning only | Partial | Limited | Low, but misses many issues |
| Audit plus remediation | High | Strong | Upfront investment |
| Accessible-by-design rebuild plus monitoring | Highest | Strongest | Best long-term value |
Future Trends in Digital Accessibility
- WCAG 3.0 is in development with a new conformance model. WCAG 2.2 remains the practical standard for now.
- More enforcement under the European Accessibility Act and the DOJ Title II rule.
- AI-assisted testing and alt text, useful with human review.
- Accessibility in procurement becoming standard for enterprise and government contracts.
- Global momentum: Saudi Vision 2030 includes digital government and quality-of-life goals that drive accessible public services, and multinational brands increasingly apply one accessibility standard worldwide.
Accessibility Myths vs Facts
| Myth | Fact |
|---|---|
| “Our site is small, so nobody will sue.” | Small and mid-sized businesses receive many ADA demand letters, often through automated scanning. |
| “An automated scan score of 100 means compliant.” | Automated tools catch only part of WCAG failures. Manual and assistive technology testing are essential. |
| “Accessibility makes design ugly.” | Accessible design is clean, readable and modern. Many of the best-designed brands are highly accessible. |
| “It’s a one-time project.” | New content, features and plugins can break accessibility, so ongoing checks are required. |
| “Only blind users benefit.” | Captions, clear forms, contrast and keyboard support help older users, mobile users and people with temporary injuries too. |
A Ten-Minute Accessibility Self-Check
- Press Tab from the top of your homepage. Can you see where focus is at every step?
- Open the main menu and a popup using only the keyboard. Can you close them with Escape?
- Zoom the browser to 200%. Is all content still readable without horizontal scrolling?
- Submit your contact form empty. Are errors announced clearly and linked to the fields?
- Check that every meaningful image has descriptive alt text.
- Play a video. Are there accurate captions?
- Check the contrast of light grey text and buttons with a contrast checker.
If any step fails, you have found a real barrier, and probably a pattern that repeats across your site.
Key Terms Explained
- Screen reader: software that reads screen content aloud for blind and low-vision users.
- ARIA: attributes that describe roles and states of interface elements to assistive technology.
- Focus indicator: the visible outline showing which element is selected when using a keyboard.
- Accessibility statement: a public page describing your conformance level, known issues and contact options.
- VPAT/ACR: a standard report documenting a product’s accessibility, often required in procurement.
What Can You Do This Week?
- Run an automated scan of your homepage, contact page and checkout.
- Complete the ten-minute keyboard self-check above.
- List third-party widgets, such as chat, booking and reviews, and check their accessibility.
- Draft an accessibility statement with a contact route for help.
Small, specific steps taken this week create momentum, and they give you real data to plan the next phase with confidence.
Conclusion: Accessibility Is Good Business
Whether your website is accessible enough to avoid a lawsuit depends on real conformance, not a widget. Target WCAG 2.2 AA, audit your key journeys with automated and manual testing, fix shared templates first, train your content team, publish an accessibility statement and keep monitoring. You will reduce legal risk in the US, UK, Canada and EU while serving more customers, improving SEO and building a brand people trust.
Which Sources Back This Guide?
We checked the rules, rates and figures in this guide against the official and primary sources below. Fees, thresholds and platform features change, so confirm current details at the source before you act.
- W3C WCAG 2.2: the accessibility standard to target.
- ADA.gov: guidance on web accessibility: US Department of Justice guidance.
- Ontario: how to make websites accessible: AODA website requirements.
- WebAIM Million report: annual data on home page accessibility failures.
- GOV.UK: accessibility requirements for public sector websites: UK public sector rules.
Related guides on this site
How can we help with this?
Get a WCAG 2.2 accessibility audit and fix plan
We test your key journeys with automated tools, keyboard and screen readers, then fix the code and templates so your site works for everyone.
Want this handled for you?
We build and optimise sites like this every week. Book a free 30-minute call and we will tell you exactly what we would change on yours.
Get a free site review
English