US web accessibility lawsuits continue to climb. According to recent analysis from Level Access, for every lawsuit that reaches federal court, defence attorneys report handling many more demand letters that settle privately. The published numbers are just the visible portion.
You might think this is purely an American problem. It isn't. UK developers and agencies can learn from what's happening across the Atlantic—and there are practical reasons to pay attention now.
The Numbers Behind US Litigation
ADA Title III lawsuits targeting websites have become a reliable revenue stream for plaintiff law firms. The Level Access analysis highlights a key driver: there's no clear technical standard mandated under Title III for private businesses. Unlike US state and local governments—who must meet WCAG 2.1 AA by April 2026—private companies face ambiguity.
That ambiguity creates opportunity for litigation. When there's no defined benchmark, every accessibility gap becomes potential grounds for a lawsuit. Companies settle because fighting costs more than fixing.
The sectors getting hit hardest include e-commerce, hospitality, and increasingly healthcare. Patient portals, booking systems, and any transactional interface that excludes users with disabilities becomes a target.
Why This Matters in the UK
The UK has clearer legal requirements. The Equality Act 2010 requires service providers to make reasonable adjustments for disabled people. Public sector bodies must meet WCAG 2.1 AA under the Public Sector Bodies Accessibility Regulations 2018.
But the private sector often assumes they're exempt from scrutiny. They're not.
The Equality and Human Rights Commission can investigate complaints. More practically, organisations like the Royal National Institute of Blind People (RNIB) actively monitor and challenge inaccessible websites. The threat isn't mass litigation American-style—it's reputational damage, regulatory action, and losing customers who simply can't use your site.
There's another angle: UK agencies building sites for US clients. If you're delivering work that will serve American users, you're potentially exposing your client to litigation. That's a conversation worth having before the project starts, not after a demand letter arrives.
What Gets Companies Sued
Looking at the US cases, the same issues appear repeatedly:
Missing or inadequate alt text. Screen reader users can't understand images without descriptions. This is WCAG 1.1.1, and it's the most common failure.
Keyboard inaccessibility. If users can't navigate and operate your site without a mouse, you've excluded people with motor impairments. Check WCAG 2.1.1 and 2.1.2.
Poor colour contrast. Text that doesn't meet the 4.5:1 ratio for normal text (WCAG 1.4.3) excludes users with low vision. This is measurable and fixable.
Unlabelled form fields. If a screen reader can't identify what information a field requires, users can't complete forms. That's WCAG 1.3.1 and 3.3.2.
Missing focus indicators. Keyboard users need to see where they are on the page. Remove the focus outline and you've made navigation impossible. See WCAG 2.4.7.
Inaccessible PDFs. That menu, application form, or policy document you uploaded as a scanned image? Completely unusable for screen reader users.
None of these are exotic edge cases. They're basic implementation failures that automated testing can catch.
Practical Steps for UK Developers
Test early and test often. Don't wait until launch to check accessibility. Build testing into your development workflow. Automated tools catch around 30-40% of WCAG issues—use them as a first pass, then test manually.
Learn to use a screen reader. Spend an hour navigating your own site with VoiceOver (Mac) or NVDA (Windows, free). You'll find problems you never knew existed.
Make accessibility part of your contracts. If you're an agency, specify the WCAG conformance level you're delivering. Document what's in scope and what isn't. This protects both you and your client.
Prioritise by impact. Not all WCAG failures are equal. A missing skip link is less severe than a checkout form that can't be completed with a keyboard. Fix the blockers first.
Document your efforts. Keep records of accessibility testing, fixes implemented, and known issues with remediation plans. If questions arise later, you want evidence of good faith effort.
The Business Case Beyond Compliance
Accessibility litigation makes headlines, but the real cost of inaccessible websites is quieter: lost customers. In the UK, disabled people and their households have spending power exceeding £274 billion annually (the "Purple Pound"). If your checkout doesn't work with a screen reader, that money goes elsewhere.
Accessibility also improves usability for everyone. Captions help users in noisy environments. Good colour contrast helps users in bright sunlight. Keyboard navigation helps power users who prefer it. Building accessible sites means building better sites.
The US litigation wave is a symptom of websites that weren't built properly in the first place. UK developers have the opportunity to do better—not because of lawsuit fear, but because it's the professional standard.
WCAGCheck scans your website for WCAG compliance issues and tells you exactly what to fix. Try it free at wcagcheck.co.uk