Web Accessibility: The Complete 2026 Guide for UK Business Websites

• Over 16 million people in the UK have a disability, roughly 24% of the population. An inaccessible website doesn't just fail a compliance check; it locks out nearly a quarter of your potential customers. (Family Resources Survey, DWP 2022/23)
• The European Accessibility Act (EAA) took effect in June 2025, extending accessibility requirements to a wide range of digital products and services. The EAA is not part of UK law, but UK businesses that provide goods and services to consumers in the EU must comply with it. (AbilityNet)
• 69% of disabled people with access needs say they click away from a website with barriers, according to the 2019 Click-Away Pound survey. Accessibility failures don't just affect disabled users; they frustrate everyone. Slow-loading pages, confusing navigation, and poor mobile design are accessibility issues that affect all users. (Click-Away Pound Survey 2019)
• Accessibility improvements can help SEO and conversion — because the same principles that make a website accessible (clear structure, fast loading, readable text, descriptive links) also make it easier for search engines to understand and for all users to navigate.

Web accessibility means designing and building websites that everyone can use, regardless of their abilities or the technology they use to access the web. This includes people who:

• Have visual impairments — from colour blindness to complete blindness, using screen readers like JAWS, NVDA, or VoiceOver
• Have hearing impairments — relying on captions, transcripts, and visual indicators instead of audio
• Have motor impairments — navigating by keyboard, voice control, switch devices, or eye tracking instead of a mouse
• Have cognitive impairments — benefiting from clear language, consistent navigation, and distraction-free design
• Use assistive technology — screen readers, magnifiers, alternative input devices, and browser extensions
• Have temporary or situational limitations — a broken arm, bright sunlight on a screen, slow internet, or holding a baby

Accessibility isn't just about permanent disability. A user on a slow mobile connection in rural Devon, a manager trying to read your website on a phone while walking between meetings, and a warehouse worker wearing gloves who can't use a touchscreen precisely — all of these people benefit from accessible design.

The Commercial Case

Beyond the moral imperative, accessibility makes commercial sense:

• Scope estimates the UK disabled market, known as the "Purple Pound", is worth about £274 billion a year. (Scope, 2023)
• Accessible sites are easier for search engines to read — semantic HTML, descriptive alt text and clear heading structures help both screen readers and search engines make sense of a page.
• Accessible design makes your site easier to use — when everyone can navigate and interact with it, more people can finish an enquiry, booking or purchase.
• It helps you meet your legal duty — all UK service providers must make reasonable adjustments under the Equality Act 2010 (see below).

Understanding the legal landscape helps you assess your obligations and prioritise your accessibility investment.

The Equality Act 2010

The Equality Act 2010 is the UK's main disability discrimination law. GOV.UK says all UK service providers "have a legal obligation to make reasonable adjustments under the Equality Act 2010" (or the Disability Discrimination Act 1995 in Northern Ireland). The Act's duty doesn't mention websites, but your website is one way you provide your service, so plan for it to be accessible.

The Act doesn't name a technical standard, so for a private business there is no rule that says WCAG 2.2 Level AA is mandatory. WCAG 2.2 Level AA is the standard UK public sector bodies must meet, unless they are exempt, under the Public Sector Bodies Accessibility Regulations 2018, and it is a sensible target for any business.

The European Accessibility Act (EAA)

The EAA, which took effect on 28 June 2025, requires digital products and services sold in EU member states to meet accessibility standards. This affects UK businesses if you:

• Sell products or services to EU customers online
• Run e-commerce websites that serve consumers in the EU
• Provide digital services (banking, transport, e-commerce) to EU residents

The European standard EN 301 549 sets out accessibility requirements for web content, and version 3.2.1 reflects the content of WCAG 2.1.

For more on the EAA's specific implications, read The European Accessibility Act: What UK Businesses Need to Know.

What "Compliance" Actually Means

There's no accessibility police force inspecting every website. But there is increasing awareness, legal precedent, and — most importantly — customer expectation. The practical approach for UK small businesses is:

1. Aim for WCAG 2.2 Level AA — this is the current best-practice standard
2. Document your efforts — having an accessibility statement shows good faith
3. Prioritise the most impactful fixes — not every issue carries equal weight
4. Make continuous improvement — accessibility is a journey, not a destination

The Web Content Accessibility Guidelines (WCAG) are the international standard for web accessibility, published by the W3C. Version 2.2, released in October 2023, is the current standard.

WCAG is built on four principles, known by the acronym POUR:

1. Perceivable

Users must be able to perceive the information on your website. This means:

• Text alternatives for images — every meaningful image has descriptive alt text
• Captions for video — audio content has text alternatives
• Adaptable content — information isn't conveyed by colour, shape, or position alone
• Sufficient contrast — text is readable against its background

2. Operable

Users must be able to operate your website's interface. This means:

• Keyboard accessible — everything works without a mouse
• Enough time — users can pause, stop, or extend time limits
• No seizure triggers — nothing flashes more than three times per second
• Navigable — users can find content and know where they are
• Input modalities — content can be operated through various inputs beyond keyboard

3. Understandable

Users must be able to understand your content and interface. This means:

• Readable text — language is identified, unusual words are defined
• Predictable behaviour — navigation is consistent, context doesn't change unexpectedly
• Error prevention — forms help users avoid and correct mistakes

4. Robust

Content must work with current and future technologies. This means:

• Valid HTML — proper semantic markup
• Name, role, value — custom components communicate their purpose to assistive technology
• Status messages — important updates are announced to screen readers

The Three Conformance Levels

Target Level AA. It's the level most UK public sector bodies must meet, a practical target for most business sites, and the level that makes the biggest practical difference for the most users.

The WebAIM Million study analyses the top one million websites annually for accessibility. In the 2026 report, 95.9% of homepages had detected WCAG 2 failures. The same issues appear year after year.

We audited twelve client sites last year. Every single one had contrast failures. Three had no keyboard navigation on their main menu. These are not edge cases.

1. Low Colour Contrast (83.9% of homepages)

The problem: Text colour doesn't contrast enough with the background, making it hard to read for users with low vision or in bright conditions.

Use a tool like WebAIM's Contrast Checker to test your colour combinations. Pay special attention to light grey text on white backgrounds — the most common offender.

2. Missing Alt Text (53.1% of homepages)

The problem: Images lack alternative text, so screen reader users have no idea what the image shows or why it's there.

3. Missing Form Labels (51% of homepages)

The problem: Form inputs (name, email, phone fields) don't have associated text labels, so screen reader users don't know what information to enter.

The fix: Every form input needs a <label> element with a for attribute matching the input's id. Placeholder text is NOT a substitute for labels — it disappears when users start typing and isn't reliably announced by screen readers.

4. Empty Links (46.3%) and Empty Buttons (30.6%)

The problem: Links or buttons have no accessible text. Common with icon-only buttons (hamburger menus, social media icons, close buttons).

The fix: Add text content to every interactive element. If the button only contains an icon, add aria-label="Menu" or visually hidden text that screen readers can announce.

5. Missing Document Language (13.5% of homepages)

The problem: The page doesn't declare its language, so screen readers don't know which pronunciation rules to use.

The fix: Add lang="en" (or appropriate language code) to your <html> element. This is a one-line fix that takes 10 seconds.

6. Empty Heading Tags (heading hierarchy issues)

The problem: Headings are skipped (H1 → H3 with no H2), used decoratively rather than structurally, or left empty.

The fix: Use headings in logical order (H1 → H2 → H3). Don't skip levels. Only use heading tags for actual headings, not for styling. Every page should have exactly one H1.

You don't need to be an expert to start testing. Here are free tools that catch the most common issues.

Automated Testing Tools

Automated tools only catch the easy, detectable issues. As W3C puts it, "no tool alone can determine if a site meets accessibility standards" (W3C). They're a great starting point, not the finish.

Manual Testing (Essential)

Automated tools can't test everything. These manual checks catch the issues that matter most:

1. Keyboard navigation — Unplug your mouse and try to use your entire website with just the keyboard. Can you reach every link, button, and form field? Can you see where the focus is? Can you operate dropdown menus?
2. Screen reader testing — Try VoiceOver (Mac, built-in), NVDA (Windows, free), or the screen reader in your phone's accessibility settings. Navigate your homepage. Does the content make sense when read aloud? Are images described? Are form fields labelled?
3. Zoom to 200% — Does your layout break? Is all content still visible and readable? This tests whether your design accommodates users who enlarge text.
4. Colour-only information — Is any information conveyed only by colour? (e.g., red text for errors without any icon or text label). If so, users who can't distinguish colours will miss it.

A 10-Minute Check You Can Do Today

Open your homepage and work through this list. Write down anything that fails.

1. Tab through the page. Can you reach the menu, every button and the contact form, and always see where you are?
2. Zoom to 200%. Does anything overlap, get cut off or need sideways scrolling?
3. Click each form label. The cursor should jump into the matching field. If it doesn't, the label isn't linked to it.
4. Check your button and body text in WebAIM's Contrast Checker against 4.5:1 for normal text.
5. View the page source and check the html tag at the top has a lang attribute, such as lang="en-GB".
6. Run WAVE on the page and note any red errors.

Fix the quick wins first. Keep the list: it tells an accessibility professional exactly where to start.

When to Bring in Professionals

An automated scan plus basic manual testing covers the fundamentals. For a thorough assessment, consider a professional accessibility audit, which typically includes:

• Full WCAG 2.2 conformance testing
• Assistive technology testing (multiple screen readers and input devices)
• User testing with people who have disabilities
• Prioritised remediation plan
• Accessibility statement drafting

This is where a website audit adds real value — combining accessibility testing with SEO, performance, and usability analysis.

Building accessibility in from the start is far cheaper and more effective than retrofitting it. These principles apply whether you're designing a new website or improving an existing one.

Colour and Contrast

• Meet minimum contrast ratios (4.5:1 for body text, 3:1 for large text)
• Never rely on colour alone to convey information — always pair with text, icons, or patterns
• Test your colour palette with a colour blindness simulator (try Coblis)
• Ensure interactive elements (links, buttons, form fields) have visible focus indicators

Typography and Readability

• Use a minimum body text size of 16px (browsers default to this for a reason)
• Set line height to at least 1.5× the font size for body text
• Keep line length between 50-75 characters for optimal readability
• Ensure text can be resized to 200% without loss of content or function
• Use left-aligned text (centred body text is harder to read for everyone, especially users with dyslexia)

Navigation and Wayfinding

• Provide a clear, consistent navigation structure across all pages
• Include a "skip to main content" link at the top of every page
• Use breadcrumbs to show users where they are in your site hierarchy
• Ensure the current page is visually indicated in navigation
• Provide a search function for sites with more than 20 pages

Layout and Spacing

• Use generous white space — cramped layouts are harder for everyone
• Ensure touch targets are at least 24×24 pixels (the WCAG 2.2 AA minimum), and aim for 44×44 pixels on mobile
• Don't make content available only on hover — hover states are inaccessible to touch and keyboard users
• Ensure your layout works in both portrait and landscape orientations

For broader design considerations, see Web Design Trends 2026: What Actually Matters for Small Businesses.

Images and media are where many websites fail accessibility requirements. Here's how to handle them properly.

Writing Good Alt Text

Alt text should convey the purpose of the image, not just describe it literally.

Video Accessibility

• Provide captions for all video content (auto-generated captions are a start but need editing for accuracy)
• Provide transcripts for audio-only content (podcasts, audio messages)
• Avoid autoplay — let users choose when to play media
• Provide audio descriptions for video content where important visual information isn't described in the dialogue

SVGs and Icons

• Inline SVGs need role="img" and an aria-label or <title> element
• Icon fonts (like Font Awesome) need aria-label or aria-hidden="true" if decorative
• Ensure icon-only buttons always have accessible text alternatives

Forms are where accessibility failures have the most direct business impact — if users can't complete your contact form or checkout process, you lose revenue.

Form Accessibility Checklist

• Every input has a visible <label> (not just placeholder text)
• Required fields are indicated by more than just colour (add "required" text or an asterisk with explanation)
• Error messages are specific ("Please enter a valid email address" not "Invalid input")
• Error messages are associated with their input using aria-describedby
• Users can review and confirm before final submission (especially for financial transactions)
• Form validation doesn't rely solely on colour (a red border isn't enough — add an icon and text)

Keyboard-Accessible Interactive Components

Custom components (dropdowns, modals, tabs, carousels) need careful attention:

• Focus management — when a modal opens, focus moves to the modal. When it closes, focus returns to the trigger.
• Keyboard operation — dropdowns respond to arrow keys, modals close with Escape, tabs switch with arrow keys.
• ARIA roles and properties — custom components need appropriate ARIA attributes so assistive technology understands their purpose and state.

Mobile accessibility is increasingly important because many of your visitors will be on a phone. Check your own analytics to see how many.

Key Mobile Accessibility Considerations

• Touch targets — buttons and links need at least 24×24 CSS pixels of tappable area (WCAG 2.2 Success Criterion 2.5.8, Level AA). 44×44 pixels is the stricter Level AAA target (Success Criterion 2.5.5).
• Orientation — don't lock your site to portrait or landscape. Users with devices mounted to wheelchairs may only be able to use one orientation.
• Pinch-to-zoom — never disable it. Users who need to enlarge content rely on this. Remove any maximum-scale=1 or user-scalable=no from your viewport meta tag.
• Reflow — at 400% zoom, content should reflow into a single column without horizontal scrolling. This is how many users with low vision browse on mobile.
• Motion — respect the prefers-reduced-motion setting. Users who experience motion sickness or vestibular disorders should be able to use your site without triggering symptoms.

Testing Mobile Accessibility

• Use your phone's built-in screen reader (VoiceOver on iOS, TalkBack on Android) to navigate your website
• Try using your phone with voice control enabled
• Test with the largest text size setting your phone offers
• Check that nothing breaks when you rotate your device

If your website has significant accessibility issues or you're building a new site, professional support ensures you meet standards without guesswork.

What an Accessibility Audit Includes

A professional accessibility audit typically covers:

• Automated scanning of all key pages
• Manual testing with screen readers and keyboard navigation
• WCAG 2.2 conformance assessment against Level AA criteria
• Prioritised remediation plan (critical → high → medium → low)
• Accessibility statement drafting or review
• Developer guidance for fixing identified issues

What an Accessible Website Build Includes

When commissioning a custom website with accessibility in mind, look for:

• Semantic HTML structure (proper heading hierarchy, landmarks, form labels)
• WCAG 2.2 Level AA colour contrast compliance
• Keyboard navigation testing on all interactive components
• Screen reader testing during development (not just at the end)
• An accessibility statement page
• Alt text guidance for content the client will manage

Writing an Accessibility Statement

An accessibility statement is a page on your website that:

1. States your commitment to accessibility
2. Names the standard you're targeting (e.g., WCAG 2.2 Level AA)
3. Lists any known limitations and what you're doing about them
4. Provides a contact method for users who encounter barriers
5. Explains your process for maintaining accessibility

This demonstrates good faith and gives users a way to report issues — which is valuable feedback for continuous improvement.

Interested in a sustainability-first approach to web design? Read Sustainable Web Design: How to Reduce Your Website's Carbon Footprint — many sustainability and accessibility principles overlap.

Is my website legally required to be accessible in the UK?

The Equality Act 2010 requires all UK service providers to make reasonable adjustments for disabled people. It doesn't name a website standard, so for private businesses there is no UK law that makes WCAG 2.2 Level AA mandatory. UK public sector bodies are different: unless they are exempt, they must meet WCAG 2.2 AA under the Public Sector Bodies Accessibility Regulations 2018. The European Accessibility Act applies from 28 June 2025 and affects UK businesses that provide goods and services to consumers in the EU. The practical answer: treat WCAG 2.2 Level AA as your baseline, document your efforts with an accessibility statement, and prioritise the fixes that affect the most users. Even without a strict legal mandate, accessible websites are easier for search engines to read, easier for visitors to use, and reach a wider audience.

How much does it cost to make a website accessible?

It depends on the size and complexity of the site, so we won't quote one figure here. The basics in this guide (contrast, alt text, form labels, page language) are often quick fixes on a simple site. Building accessibility in from the start is generally cheaper than retrofitting later. Custom interactive components (carousels, mega menus, custom form controls) are usually the hardest to fix.

Does accessibility hurt my website's design?

No. Accessibility constraints (contrast ratios, text sizing, clear navigation) actually improve design by enforcing clarity and usability.

What's the difference between WCAG 2.1 and 2.2?

WCAG 2.2, released in October 2023, builds on 2.1 by adding nine new success criteria. The most significant additions are requirements for consistent help mechanisms, minimum touch target sizes (24×24px), and better support for cognitive accessibility. If you're already meeting 2.1 Level AA, the step to 2.2 is manageable. If you're starting from scratch, target 2.2 directly.

Can I use overlays or widgets to make my site accessible?

Accessibility overlay tools (like AccessiBe, UserWay, or AudioEye) claim to fix accessibility automatically with a single line of code. We do not recommend them. The Overlay Fact Sheet, signed by accessibility professionals, says "full compliance cannot be achieved with an overlay". Overlays don't fix underlying code issues, and they can cause "unexpected page changes for assistive technology users". There are no shortcuts to genuine accessibility.

How do I maintain accessibility over time?

Accessibility isn't a one-time fix. Content updates (new images without alt text, new forms without labels) can introduce issues. Build accessibility into your content workflow: train anyone who updates your website to add alt text, use proper heading structure, and test new content with keyboard navigation. Schedule a quarterly automated scan to catch regression, and consider an annual professional audit.

Want to know how accessible your website is? Request a free mini audit or talk to us about building an accessible website that works for every user.