Guide
Equality Act 2010: The UK's Accessibility Law
)
On this page
The Equality Act 2010 is the cornerstone of disability rights and digital accessibility law in the United Kingdom. It requires every organisation that offers goods, services, or facilities to the public — whether in person or online — to make reasonable adjustments so that disabled people are not put at a substantial disadvantage. For digital teams, that means your websites, apps, and online services must be designed and maintained to be accessible to everyone. Unlike the EU's European Accessibility Act, the Equality Act is not a future deadline — it has been enforceable law for over a decade. If your organisation serves UK users and hasn't addressed accessibility, you're already exposed.
Below, we’ll review what the Equality Act 2010 is, who it applies to, and why compliance is worth prioritising.
What Is the Equality Act 2010? The UK Accessibility Law
The Equality Act 2010 is the UK's primary anti-discrimination legislation. It consolidated and replaced a patchwork of earlier laws — including the Disability Discrimination Act 1995 — into a single, unified framework that prohibits discrimination across nine protected characteristics: age, disability, gender reassignment, marriage and civil partnership, pregnancy and maternity, race, religion or belief, sex, and sexual orientation.
For digital accessibility, the disability provisions are most directly relevant. Under the Act, any organisation that provides goods, services, or facilities to the public has a legal duty to make reasonable adjustments to remove barriers that disabled people face. This duty is anticipatory — meaning organisations cannot wait for a disabled person to complain before acting. Accessibility must be built in proactively.
In practical terms, this covers:
Ensuring websites and apps can be navigated by keyboard, screen reader, and other assistive technologies
Providing text alternatives for non-text content such as images, video, and audio
Maintaining sufficient colour contrast and scalable text
Designing user flows that do not rely solely on colour, sound, or motion to convey meaning
Making digital documents (PDFs, forms, reports) accessible
The Act does not prescribe a specific technical standard, but WCAG 2.2 Level AA has been widely adopted as the benchmark for demonstrating that reasonable adjustments have been made. Courts and enforcement bodies treat WCAG compliance as strong evidence that an organisation has met its legal obligations.
How the Equality Act 2010 Differs from the EAA
The European Accessibility Act (EAA) and the Equality Act 2010 share a common goal — ensuring disabled people can access goods and services on equal terms — but they differ significantly in scope, mechanism, and who they apply to.
The critical point for UK organisations: compliance with one law does not mean compliance with the other.
If your business serves customers in both the UK and EU markets — which most mid-to-large UK organisations do — you are subject to both frameworks simultaneously. The EAA imposes hard technical requirements and product-specific timelines. The Equality Act imposes a broader, ongoing duty that applies to your entire digital estate. The safest and most efficient approach is to treat WCAG 2.2 Level AA as your shared baseline and build compliance processes that satisfy both frameworks at once.
AudioEye helps organisations navigate both laws with a single, unified platform — so you're not running parallel programmes for UK and EU compliance.
)
Who Needs to Comply with the Equality Act 2010?
The short answer: almost every organisation in the UK.
The Equality Act applies to any organisation that provides goods, facilities, or services to the public. This is an intentionally wide definition. It covers:
Retailers and e-commerce businesses — including online-only stores
Financial services providers — banks, insurers, lenders, and fintech platforms
Healthcare organisations — NHS trusts, private clinics, health information services
Educational institutions — universities, colleges, schools, and e-learning providers
Media and entertainment platforms — streaming services, news publishers, ticketing sites
Hospitality and travel — hotels, airlines, booking platforms
Professional services firms — law firms, accountancies, consultancies
Public sector bodies — government departments, local authorities, NHS organisations, and publicly funded charities
There is no size threshold. A sole trader running an e-commerce website is subject to the same duty to make reasonable adjustments as a FTSE 100 company. The scale and cost of what counts as "reasonable" will vary — but the obligation itself does not.
Additionally, employers have separate duties under the Act to make reasonable adjustments for employees with disabilities — including ensuring internal systems, intranets, and HR tools are accessible.
Does the Equality Act 2010 Apply to Non-UK Companies?
Yes — if you are targeting UK consumers or operating in the UK market, the Equality Act applies to you regardless of where your business is headquartered.
The Act's scope is determined by where the service is provided and received, not where the company is incorporated. A US-based SaaS platform with UK customers, a European retailer shipping to UK addresses, or a Canadian media company with a significant UK subscriber base can all be subject to the Act's provisions.
The key question is whether you are offering goods or services to the public in the UK. If the answer is yes, disabled people in the UK have the right to access those services without unjustifiable barriers — and your organisation has a duty to remove them.
This is especially relevant post-Brexit. UK organisations that previously relied on EU-wide compliance frameworks now need to ensure their accessibility programmes explicitly address UK legal requirements. And international organisations entering or growing in the UK market should treat Equality Act compliance as part of standard market entry planning.
Exemptions
The Equality Act does include some limited exemptions and qualifications:
Disproportionate burden: Organisations may be able to justify not making a specific adjustment if the cost or practicality is genuinely disproportionate relative to the organisation's size, resources, and the likely benefit. However, this is a narrow exemption — organisations cannot claim disproportionate burden simply because accessibility is inconvenient or expensive. A formal assessment is required, and organisations must still make whatever adjustments are reasonable.
Private clubs and associations: Organisations that restrict membership on the basis of a protected characteristic (e.g., a private members' club) have limited exemptions, but these do not extend to their public-facing digital presence.
Small charities: Some very small voluntary organisations may have more flexibility in what counts as reasonable, but they are not exempt from the Act's core obligations.
Content that is not directly under your control: Organisations are generally not responsible for the accessibility of third-party content embedded in their services, provided they have not endorsed or adopted that content — though this area involves nuance and legal interpretation.
What Products and Services Does the Equality Act Cover?
The Equality Act's digital accessibility obligations extend across your entire public-facing digital estate. There is no carve-out for "older" websites, legacy systems, or content that predates the Act. If it's live and accessible to the public, it's in scope.
In scope:
Websites — all public-facing pages, including marketing sites, product pages, and support content
Mobile applications — iOS and Android apps used by customers or the general public
Web-based portals and self-service tools — account dashboards, booking systems, claims portals
Digital documents — PDFs, Word documents, and forms published for public use
Video and audio content — must include captions, transcripts, and audio descriptions where relevant
Chatbots and virtual assistants — must be operable with assistive technologies
Social media presences — best practice accessibility applies, particularly for published content
Third-party platforms — where your organisation directs users to a third-party service as part of your offering, you have a duty to ensure that pathway is accessible
For public sector bodies, additional obligations apply under the Public Sector Bodies (Websites and Mobile Applications) Accessibility Regulations 2018, which require explicit WCAG 2.2 Level AA compliance, published accessibility statements, and regular review cycles.
Equality Act 2010 UK Accessibility Compliance Timeline and Enforcement Milestones
Unlike the EAA, the Equality Act does not operate on a phased implementation timeline — it has been fully in force since October 2010. However, the enforcement landscape for digital accessibility has evolved significantly over the years.
Ongoing Compliance
Accessibility is not a one-time fix. The Equality Act's duty to make reasonable adjustments is continuous — it applies to new content, new features, and new technologies as they are deployed. A website that passed an audit two years ago may no longer meet the standard if it has been updated, redesigned, or expanded since.
Ongoing compliance means:
Regular automated monitoring to catch regressions before they become legal exposures
Manual testing with assistive technologies — screen readers, voice control, keyboard-only navigation
Accessibility testing integrated into development workflows — not bolted on after launch
Published and maintained accessibility statements (required for public sector; best practice for private sector)
A documented process for handling user accessibility complaints — and acting on them promptly
Training for content editors, designers, and developers so that accessibility is embedded in day-to-day decisions
AudioEye's platform combines automated detection and fixing with expert human review — giving you continuous visibility into your accessibility posture and the tools to maintain it over time.
)
What Happens If You Don't Comply With the Equality Act 2010?
Non-compliance with the Equality Act 2010 creates real legal, financial, and reputational risk. Unlike some regulatory frameworks where enforcement is centralised, the Equality Act creates individual rights — meaning any disabled person who experiences discrimination can bring a claim.
Financial Penalties
There is no statutory fine for Equality Act non-compliance in the way that GDPR has its penalty structure. Instead, financial exposure comes through civil litigation. If a disabled person brings a successful claim against your organisation for failing to make reasonable adjustments, a court can award:
Compensation for injury to feelings — typically ranging from £1,000 to £45,000 depending on severity, under the Vento Guidelines
Compensation for financial loss — if the claimant suffered actual economic harm as a result of the inaccessible service
Legal costs — which can significantly exceed the damages themselves in contested cases
Market Access Restrictions
For organisations subject to procurement requirements — particularly those bidding for public sector contracts — accessibility compliance is increasingly a mandatory requirement. UK government procurement frameworks and many large enterprise supplier agreements now include accessibility obligations. Failure to demonstrate compliance can disqualify your organisation from significant contract opportunities.
Enforcement Actions
The Equality and Human Rights Commission (EHRC) has broad investigatory and enforcement powers. The EHRC can:
Conduct formal investigations into organisations it suspects of systemic non-compliance
Issue unlawful act notices requiring organisations to produce and implement an action plan
Apply to court for an injunction to prevent continued discriminatory practices
Enter into legally binding agreements with organisations setting out required remediation steps
While the EHRC has historically focused more on systemic issues than individual website complaints, the increasing prominence of digital accessibility in public discourse is shifting this dynamic.
Reputational Risk
Accessibility failures are increasingly visible. Disability advocacy organisations, the media, and social networks regularly highlight inaccessible digital experiences. A high-profile accessibility complaint — or a published EHRC investigation — can generate significant negative coverage that persists long after the technical issue is resolved.
Organisations that demonstrate genuine commitment to accessibility, by contrast, build trust with disabled users, their families and networks, and the broader public.
Procurement Exclusion
UK public sector procurement increasingly requires suppliers to demonstrate WCAG compliance as a condition of contract award. Central government frameworks, NHS procurement, and local authority supplier panels all include accessibility requirements that are becoming more rigorously enforced. Private sector organisations with large enterprise clients are also seeing accessibility become a standard component of vendor due diligence
The Purple Pound
Beyond compliance risk, inaccessibility is a commercial loss. Disabled people and their households represent an estimated £249 billion in annual spending power in the UK — the so-called Purple Pound. Research shows that UK businesses lose approximately £17.1 billion each year because disabled users abandon websites they cannot use. Non-compliance isn't just a legal risk — it's revenue you're leaving on the table.
The bottom line: The Equality Act sets the obligation. WCAG 2.2 Level AA defines what meeting that obligation looks like in practice for your web and mobile content. EN 301 549 extends that framework to cover your broader digital estate — documents, software, internal tools — and is the standard you need if you're also managing EAA compliance for EU markets.
For most organisations, a single programme built around WCAG 2.2 Level AA — with EN 301 549 coverage for non-web content — will satisfy the Equality Act's reasonable adjustments duty, the Public Sector Bodies Regulations, and the EAA simultaneously. That's the most efficient path to compliance across all three frameworks.
AudioEye's platform is built to that combined standard — helping you achieve and maintain conformance across your entire digital estate without running separate programmes for each legal framework.
How EN 301 549 Differs from WCAG
WCAG was originally designed for web content. EN 301 549 goes further — it extends accessibility requirements to non-web ICT products and services, including software, hardware, self-service terminals, ATMs, and other electronic systems. This broader scope reflects the EAA’s wider reach beyond websites and apps, and is one of the key reasons EAA compliance involves more than aligning with web content standards alone.
How This Connects Back to the EAA
Bringing it all together: The EAA does not have its own technical checklist; instead, it mandates compliance with EN 301 549 to meet its accessibility requirements. More simply, organisations wanting to meet EAA compliance standards should use EN 301 549 as the operative standard. The POUR principles are the criteria that must be met in practice, and WCAG 2.2 Level AA serves as the underlying reference that shapes those criteria for web and digital content.
How to Comply with the Equality Act 2010
Equality act 2010 compliance starts with building accessibility into digital products and content from the ground up. The POUR principles provide the framework for identifying and fixing accessibility issues and form the foundation for what the Equality Act 2010 requires organisations to meet.
Here’s how to get started.
1. Test Content Against POUR Principles
The first step in your journey to compliance is testing your existing content for alignment with POUR standards (which follow many of the success criteria included in WCAG 2.1 Level AA). You can use accessibility tools to help you meet POUR principles.
For example, common accessibility issues can be identified through automated testing. However, some accessibility issues — such as non-descriptive links or unhelpful alt text — cannot be detected solely by automation. To find more complex issues, you may need to use a team of human testers.
Free accessibility checkers (like this one from AudioEye) are a great starting point.
Once the audit results are in hand, the next step is to prioritise fixes. Starting with quick wins and straightforward issues before moving on to more complex remediation is generally the most efficient approach. For larger issues, a structured remediation plan helps minimise disruption to existing content and development workflows. For organisations navigating multiple issues across a large site or application, working with an accessibility expert can help sequence fixes effectively and maintain alignment with evolving requirements.
Accessibility compliance isn't a one-time project. New content, product updates, and technology changes can introduce barriers even after an initial remediation effort — which is why ongoing testing is essential for sustained compliance.
An accessibility statement demonstrates an organisation's commitment to accessibility and gives users information about the site's current state, testing tools, known barriers, and remediation goals. Accessibility statements should follow a standard format and are a requirement under both the Web Accessibility Directive and the Equality Act 2010
Start Building for Equality Act 2010 Compliance
Ready to see where existing digital content stands? Start with AudioEye's free Website Accessibility Checker — or schedule a demo to see how AudioEye can support a longer-term path to EAA compliance.
Frequently Asked Questions
AudioEye Demo
Accessibility is a journey, and we're here to help guide you down that path.
Get in touch to see a customised approach to compliance for your organisation.