Making sense of accessibility and the law

The reason to make things accessible to as many people as possible is because it’s the right thing to do, but the sad fact is that that’s rarely how it works.

Where other constraints in product design, like security, are seen as non-negotiables, accessibility is often overlooked as an inconvenient nice-to-have. It often comes as a shock to product managers when the penny drops that accessibility is a legal requirement. Not only have they been exposing their product to huge risk, but they now have to re-do a lot of work, sometimes having to put feature development on hold.

The legal landscape is difficult to wrap your head around so, like my deliberately over-simplified breakdown of the Web Content Accessibility Guidelines (WCAG), here’s how accessibility is covered by the law.

Note: I’m not a lawyer, and this is surface-level stuff intended to give you a feel for how it all slots together.

Lots of laws

There are countless laws that govern private sector digital accessibility across the world. Here are the heavy-hitters that I encounter regularly in my day-to-day work:

European Accessibility Act (EAA)

Individual EU state employment law

Equality Act 2010 (United Kingdom)

Americans with Disabilities Act (ADA)

European Accessibility Act (EAA)

The EAA is the new kid on the block, having taken effect on the 28th of June 2025. Some key points:

Products already on the market on that date have until 2030 to comply

It applies to any business that sells into the EU, whether they’re in an EU state or not

It only applies to websites and apps that are for ‘consumers’, not those intended for business use

‘Microenterprises’, defined in Article 3 (23), are exempt

Individual EU state employment law

That last point in the EAA isn’t quite the get-out-of-jail-free card it seems, as business to business (B2B) software is usually covered in legislation on equal opportunity employment in individual EU states, for example:

Germany’s Sozialgesetzbuch IX, §164

France’s Code du travail, Article L5213-6

Spain’s Real Decreto Legislativo 1/2013, Artículo 7

Italy’s Decreto Legislativo 151/2015, Legge 68

Equality Act 2010 (United Kingdom)

I live in the UK where we’ve had the Equality Act since 2010. It requires organisations to make sure that their services, including websites, mobile apps, and other digital platforms, are accessible to people with disabilities. Section 20 (3) says:

Where a provision, criterion or practice … puts a disabled person at a substantial disadvantage … in comparison with persons who are not disabled, [the duty is] to take such steps as it is reasonable to have to take to avoid the disadvantage.

It doesn’t make a distinction between B2B and direct to consumer (D2C), so if you’re getting in the way of disabled people doing what they need to do using the software you produce, you’re liable.

Americans with Disabilities Act (ADA)

Like the UK’s Equality Act, the ADA covers both D2C and B2B. It has been around since 1990, which pre-dates the internet, but there have been lots of lawsuits relating to websites and apps in the intervening decades.

Here’s what it says about D2C products in Title III, 42 U.S. Code § 12182(a):

No individual shall be discriminated against on the basis of disability in the full and equal enjoyment of the goods, services, facilities, privileges, advantages, or accommodations of any place of public accommodation.

And in Title I, 42 U.S.C. § 12112(a) the ADA covers employee discrimination. This means that digital products people use at work must be accessible:

No covered entity shall discriminate against a qualified individual on the basis of disability in regard … terms, conditions, and privileges of employment.

The public sector

An honourable mention for the public sector, which tends to have separate laws to govern its accessibility, as you’ll definitely have heard of some of these:

Section 508 in the US

The Public Sector Bodies Accessibility Regulations 2018 in the UK

Directive (EU) 2016/2102

But if you’re not a government organisation, you’ll be more interested in complying with the EAA, ADA, etc.

You can be sued!

So accessibility is the law, but who has actually been sued!? Well, it turns out, lots of companies; here are some high profile examples from the United States where thousands of accessibility lawsuits are filed every year:

Target (2006); this was the first major web accessibility lawsuit and defined a website as a “place of public accommodation”

Domino’s Pizza (2019); the Supreme Court denied review, which reinforced the 2006 application of the ADA to digital services

Netflix (2012); the first online-only product to be held accountable

In the UK and Europe, court cases are culturally much less common; the very real threat of legal action is usually avoided as companies are put under pressure by bodies like the RNIB and usually fix issues before being dragged through the courts in a case they are likely to lose.

How to comply

If your product is in a tricky spot, accessibility-wise, you could well be in for a lot of bad PR and legal action; how do you put things right?

Meeting WCAG version 2.2 level AA is a solid baseline for accessibility in the UK and US. In Europe, EN 301 549 has long been the standard, and the good news is that it’s pretty much just WCAG with a few extras, such as ensuring operating systems (like Dark Mode, and Reduce Motion) are respected.

But meeting WCAG/EN 301 549 may still not be enough to avoid legal trouble. WCAG is notoriously open to interpretation and even an objectively conformant website or app can still create barriers; for example, through confusing user journeys.

WCAG is a great first milestone on the way towards accessibility, but a culture of accessible product design and development is the best way to avoid legal issues.