WCAG Compliant Legal Website Design: The UK & Ireland Guide

Most UK business owners assume legal website design and accessibility compliance are public sector problems. They are not. The Equality Act 2010 applies to every business that offers goods or services online, and courts have consistently interpreted websites as a place of public accommodation under that legislation. Get the design wrong, and you are not just failing users with disabilities – you are exposed to legal claims, losing potential customers, and almost certainly leaving SEO performance on the table.

This guide covers what UK and Irish SMEs actually need to know: the legal frameworks that apply to your site, what WCAG 2.2 requires in plain terms, how accessible design connects to commercial performance, and the practical steps to get from where you are now to a compliant, inclusive website.

What Is WCAG and Why Does It Matter for UK Businesses?

The Web Content Accessibility Guidelines (WCAG), published by the World Wide Web Consortium (W3C), are the internationally accepted technical standard for web accessibility. The guidelines define how to make web content perceivable, operable, understandable, and robust – the four principles that form the POUR framework – for the widest possible range of users, including those who rely on assistive technologies such as screen readers, magnification software, and keyboard-only navigation.

WCAG is structured across three conformance levels. Level A covers the most basic accessibility requirements. Level AA, which sits in the middle, is the level referenced by UK legislation and recommended as the practical target for all commercial websites. Level AAA represents the highest standard and is generally not required in full, as some criteria are difficult to meet across all content types.

WCAG 2.1, published in 2018, added criteria specifically addressing mobile accessibility and users with cognitive and low-vision needs. WCAG 2.2, published by the W3C in October 2023, added nine further success criteria – including clearer rules around focus indicators, target sizes for interactive elements, and consistent help mechanisms. Most existing guidance on UK websites still references 2.1; any web design agency or developer who hasn’t updated their process to 2.2 is already working to an outdated standard.

The Four POUR Principles

Perceivable: Users must be able to perceive all content and interface components. This means providing text alternatives for images, captions for video, and sufficient colour contrast between text and background. The minimum contrast ratio for standard body text under WCAG 2.2 AA is 4.5:1.

Operable: All functionality must be operable without a mouse. Users must be able to navigate by keyboard alone, and interactive elements must have visible focus indicators. WCAG 2.2 introduced stricter requirements here, including a minimum target size of 24×24 pixels for interactive elements such as buttons and form controls.

Understandable: Content must be readable and predictable. Language must be set in the page code so that screen readers pronounce text correctly. Error messages must identify the field in question and explain what the user needs to do.

Robust: Content must be interpretable by current and future assistive technologies. This means using valid, semantic HTML and avoiding practices that break screen reader compatibility.

The UK Legal Website Design Framework: What the Law Actually Requires

Equality Act 2010 (Private Sector)

The Equality Act 2010 is the primary piece of legislation governing website accessibility for UK private companies. Under Section 20, service providers have a legal duty to make “reasonable adjustments” to remove barriers that place disabled users at a substantial disadvantage. Websites have been treated by courts and the Equality and Human Rights Commission (EHRC) as a service under this definition.

The “reasonable adjustments” standard means the duty is not absolute – it is proportionate to the size and resources of the business. A sole trader operating a simple brochure site has different obligations from a national e-commerce retailer. What is consistent is the principle: if your website design is putting disabled users at a substantial disadvantage compared to non-disabled users, you are likely in breach.

For Northern Ireland businesses, Section 75 of the Northern Ireland Act 1998 adds a further dimension. Public authorities in Northern Ireland have a statutory duty to promote equality of opportunity across a range of grounds, including disability. If you supply services to public authorities or operate as a public body, your website accessibility obligations are both more specific and more actively monitored.

Public Sector Bodies Accessibility Regulations 2018

The Public Sector Bodies (Websites and Mobile Applications) Accessibility Regulations 2018 apply to public sector organisations in the UK. These regulations require compliance with WCAG 2.1 AA as a minimum and mandate the publication of an accessibility statement. Monitoring and enforcement are carried out by the Central Digital and Data Office (CDDO).

While these regulations do not directly cover private businesses, they set the practical benchmark against which all commercial websites are increasingly assessed. They also matter if you supply digital services to public sector clients, where contract requirements frequently reference compliance with the 2018 Regulations.

The European Accessibility Act (Relevance to UK Exporters)

The European Accessibility Act (EAA), which comes into force for EU member states from June 2025, applies to businesses selling digital products and services in EU markets. UK businesses that export to Ireland, France, Germany, or any EU country, or that operate in the Irish market, need to be aware of the EAA’s requirements. The EAA draws heavily on EN 301 549, which itself references WCAG 2.1 AA. Businesses building to WCAG 2.2 AA are well-positioned for EAA compliance.

WCAG 2.2: What Has Changed and Why It Matters

WCAG 2.2 was published in October 2023. It added nine new success criteria to the existing 2.1 framework. Understanding what changed matters both for compliance and for the practical experience of real users.

The most commercially significant new criteria are:

Focus Not Obscured (2.4.11, AA): The keyboard focus indicator – the visible outline showing which element is currently selected – must not be fully hidden by sticky headers, cookie banners, or other overlaid components. This is a very common issue on websites with fixed navigation bars.

Focus Not Obscured (Enhanced) (2.4.12, AAA): The component receiving focus must be entirely visible. This is the AAA variant and is not required for AA compliance, but it represents best practice.

Focus Appearance (2.4.13, AA): Focus indicators must meet minimum size and contrast requirements. Many websites use a thin browser-default outline that technically shows focus but is effectively invisible to users with low vision.

Dragging Movements (2.5.7, AA): Any functionality that requires a dragging gesture – such as a carousel or sortable list – must also be operable with a single pointer action. This matters for users with motor impairments who cannot reliably control drag interactions.

Target Size Minimum (2.5.8, AA): Interactive targets must be at least 24×24 CSS pixels, unless spacing between targets is sufficient or an equivalent control is available elsewhere. This is particularly relevant for mobile navigation elements and icon-only buttons.

Consistent Help (3.2.6, A): If a website offers help mechanisms such as a live chat widget, phone number, or contact form, these must appear in a consistent location across pages.

Redundant Entry (3.3.7, A): Users must not be required to re-enter information they have already provided in a single session. This matters for multi-step forms and checkout processes.

Accessible Authentication (3.3.8, AA): Login processes must not rely solely on cognitive function tests – specifically, they must not require users to solve puzzles or transcribe distorted text (such as traditional CAPTCHA) as the only authentication option.

Accessible Authentication (No Exception) (3.3.9, AAA): The AAA version removes exceptions allowed in 3.3.8.

None of these criteria was present in WCAG 2.1. A website that was fully compliant with 2.1 AA in 2022 may fail several 2.2 AA criteria today, particularly around focus visibility, target sizes, and authentication flows.

The Business Case for Accessible Web Design

Accessible websites are not just a compliance obligation – they serve a larger audience and typically perform better in search.

The Office for National Statistics estimates that around 16 million people in the UK have a disability. Spending decisions made by disabled people and their households represent an estimated £274 billion annually (a figure often referred to as the “Purple Pound”). Businesses that design their websites to exclude this audience are not just facing legal risk – they are voluntarily reducing their addressable market.

The connection between web accessibility and search engine performance is substantive. Google’s crawler processes pages in a way that closely mirrors how a screen reader does: it reads text, follows links, interprets heading structure, and checks whether images have text descriptions. A site with proper semantic HTML, descriptive alt text, logical heading hierarchy, and keyboard-navigable structure will index more cleanly and typically rank better. These are not separate disciplines. They share the same technical foundation.

Accessible sites also tend to perform better on Core Web Vitals metrics. Lean, semantic code loads faster than markup-heavy designs built with visual presentation as the only consideration. Improving your site’s accessibility often has a measurable positive effect on page speed scores.

According to Ciaran Connolly, founder of ProfileTree: “When we audit websites for accessibility, we almost always find that the same code issues causing accessibility failures are also affecting SEO crawlability and page performance. Treating accessibility as a separate box to tick misses the point – it is part of building a website properly.”

How to Balance Aesthetics and Accessibility in Web Design

One of the most persistent concerns we hear from SME owners is that accessible design means visually compromised design. That has not been true for some time.

The most common misconception is that accessible websites must use high-contrast black-and-white colour schemes that eliminate all visual character. WCAG’s contrast requirements apply specifically to text and its background, and to user interface components. A brand colour palette can meet contrast requirements while remaining distinctive. The WCAG 2.2 AA threshold of 4.5:1 for normal text and 3:1 for large text (18pt and above, or 14pt bold) is achievable with most well-considered colour systems.

Typography works the same way. WCAG does not mandate a minimum font size – it requires that text can be resized to 200% without loss of content or functionality. Good responsive typography already satisfies this. The constraints are real, but they are design constraints, not design defeats.

Where aesthetics and compliance most frequently clash is in interactive design: animated transitions that cannot be paused, icon-only buttons with no accessible label, modal overlays that trap keyboard focus, and custom form elements built without ARIA markup. These are development decisions, not aesthetic ones, and they are fixable without redesigning the visual language of the site.

ProfileTree’s web design process treats accessibility requirements as part of the brief rather than a post-build remediation task. This is worth asking about when commissioning a new website: at what stage do your designers and developers address WCAG compliance?

Roadmap to WCAG Compliance: A Practical Guide for SMEs

Phase 1: The Accessibility Audit

Before anything is changed, you need to know where you currently stand. An accessibility audit identifies which WCAG criteria your site fails, at what severity, and where. This is not the same as running an automated checker – tools like WAVE or Axe will identify around 30-40% of accessibility issues; the remainder require manual testing, including testing with actual screen readers.

A structured audit covers: automated scanning for code-level errors, manual review of keyboard navigation and focus management, screen reader testing (typically using NVDA on Windows and VoiceOver on macOS/iOS), colour contrast checking across all text and interface elements, review of form labels and error handling, and video/audio accessibility where media is present.

ProfileTree’s web development team carries out accessibility audits as a standalone service and as part of broader website development projects. The output is a prioritised issue log, not just a pass/fail list.

Phase 2: Remediation and Development

Remediation should be prioritised by severity and effort. Level A failures are typically the most critical and should be addressed first. The most common issues we encounter during audits of SME websites include:

• Missing or inadequate alt text on images (particularly decorative images that have been given descriptive alt text, when they should have an empty alt attribute)
• Form inputs without programmatically associated labels
• Colour contrast failures on text over brand colour backgrounds
• Keyboard traps in modal overlays and custom dropdown menus
• Missing skip navigation links on content-heavy pages
• Videos without captions or transcripts

Phase 3: The Accessibility Statement

Under the Public Sector Bodies Accessibility Regulations, public sector bodies in the UK must publish an accessibility statement. For private businesses, publishing one is not a legal requirement – but it is increasingly expected by procurement teams and signals a genuine commitment to compliance.

An accessibility statement covers: the standard your site is tested against, the date of the last audit, any known areas of non-compliance and why they exist, and how users can request accessible alternatives or report issues. Gov.uk publishes a template accessibility statement that private organisations can adapt.

Phase 4: Ongoing Maintenance

Accessibility compliance is not a one-time fix. Content management systems like WordPress allow editors to upload images, add links, and create new pages without any WCAG training. Common ongoing failures include: images uploaded without alt text, PDFs published without accessible tagging, colour contrast broken by theme updates, and new interactive components added without accessibility review.

Building accessibility into your content team’s standard operating procedures – with brief training on what to check before publishing – prevents regressions. ProfileTree’s digital training programmes can be structured to cover web accessibility as a practical module for content editors and marketing teams.

Essential Accessibility Testing Tools

WAVE (Web Accessibility Evaluation Tool): Browser extension from WebAIM that overlays a visual report of accessibility errors directly on the page. Good for identifying structural issues, missing labels, and contrast failures quickly. Free.

Axe DevTools: Browser extension from Deque Systems. More technical output than WAVE, with direct integration into browser developer tools. The free version covers the most common WCAG 2.1/2.2 violations.

NVDA (NonVisual Desktop Access): Free screen reader for Windows. Testing with NVDA gives a realistic picture of how a blind user experiences your site. Using it alongside Chrome or Firefox is standard practice for manual accessibility testing.

VoiceOver: Built into macOS and iOS. Important for testing mobile accessibility, particularly on Safari, which has distinct screen reader behaviour from desktop browsers.

Colour Contrast Analyser: Desktop tool from TPGi (free) that allows you to pick any two colours on screen and check their contrast ratio against WCAG thresholds.

Accessibility Insights for Web: Microsoft’s free Chrome extension, which includes a guided manual testing feature alongside automated checks.

No automated tool alone is sufficient. A combination of automated scanning and manual testing with at least one screen reader is the minimum credible approach.

Legal Risks of Non-Compliant Websites

The question SME owners often ask is: What is the actual enforcement risk?

Under the Equality Act 2010, enforcement is driven by individual complaints rather than proactive regulation. A disabled user who cannot access your service can bring a claim in the county court (England and Wales) or sheriff court (Scotland), or raise a complaint with the EHRC. The EHRC can also conduct formal investigations and issue compliance notices.

Legal actions brought under the Equality Act for digital accessibility failures are less common in the UK than equivalent ADA cases in the United States, but the legal pathway exists and has been used. The more immediate and frequent risk is reputational: public complaints about accessibility failures, particularly from disabled advocacy organisations, can generate significant negative coverage.

For public sector suppliers, the risk profile is different. Many public sector procurement frameworks in the UK and Ireland now include accessibility compliance as a contract requirement. Failure to meet WCAG 2.1 AA can disqualify a supplier from a tender or breach a contract clause during delivery.

The legal implications of not designing accessible websites extend beyond formal enforcement. Insurance policies covering professional indemnity sometimes exclude claims arising from regulatory non-compliance. If accessibility failures form part of a broader claim about fitness for purpose, that exclusion can become relevant.

Accessible Web Design for Specific Industries

Law Firms

The particular irony of a law firm’s website failing accessibility standards is not lost on clients or courts. Legal services websites typically handle complex document downloads, form-based client intake, and account portals – all areas where WCAG failures are common. Keyboard navigation of form fields, accessible error handling, and PDF accessibility (for downloadable precedents and policy documents) are the three areas most commonly failing on law firm sites we have reviewed.

The connection between accessible design and ethics in digital marketing for law firms is also worth noting: a law firm that cannot demonstrate compliance with the Equality Act on its own website faces an obvious credibility problem when advising clients on regulatory compliance.

Healthcare and Public Sector Organisations

Healthcare websites sit within the Public Sector Bodies Accessibility Regulations for the NHS and public health organisations. Accessibility failures on healthcare websites carry additional severity: a patient who cannot access appointment booking, prescription information, or emergency guidance because of an inaccessible design is facing a real-world harm beyond inconvenience.

E-commerce

Checkout flows are a primary failure point for e-commerce accessibility. Custom payment form elements, CAPTCHA during account creation, and complex product selectors are all common sources of WCAG 2.2 failures. For any e-commerce operation targeting UK consumers, the Equality Act 2010 duty to make reasonable adjustments applies directly to the transactional journey.

ProfileTree’s Approach to Accessible Website Design

ProfileTree is a Belfast-based web design and digital marketing agency, and accessibility compliance has been part of our web development process for over a decade. We work with SMEs across Northern Ireland, Ireland, and the UK – from professional services firms in Belfast to e-commerce businesses across Great Britain.

Our web design team builds to WCAG 2.2 AA as a default, not as an optional upgrade. This means accessibility decisions are made at the wireframe and design stage, not retrospectively identified during a pre-launch audit. Development follows semantic HTML practices with ARIA integration where required, and all new projects include screen reader testing as part of the quality assurance process.

We also support businesses that have inherited inaccessible websites and need a clear remediation pathway. An accessibility audit from ProfileTree produces a prioritised fix list with effort estimates, so you can make informed decisions about what to address immediately and what to plan for in a phased development programme.

If you need to understand where your website currently stands against WCAG 2.2, our web development team can carry out a structured audit and advise on the most practical route to compliance.

Frequently Asked Questions