Skip to main content

Need a website fast? Get a custom site live in just 7 days!

Let's Go!
Brambla
Featured image for Website Accessibility: A UK Small Business Guide
Sector5 February 2025· Updated 10 March 2026

Website Accessibility: A UK Small Business Guide

A plain-English guide to website accessibility for UK small businesses — covering legal requirements, WCAG basics, the fixes that make the biggest difference, and why accessible websites rank better on Google.

Key Takeaways

  • Website accessibility is a legal requirement in the UK, not just a best practice. The Equality Act 2010 requires businesses to make reasonable adjustments to ensure disabled people can access services — and that includes your website. The European Accessibility Act 2025 extends these obligations further from June 2025, affecting any business with EU customers.
  • Accessibility affects far more people than most businesses realise. Around 1 in 5 people in the UK has a disability — that's roughly 14.6 million potential customers. Accessibility also helps people in temporary situations: a broken arm, bright sunlight on a screen, or a slow internet connection.
  • The most impactful fixes are simple. Alt text on images, sufficient colour contrast, keyboard-navigable menus, descriptive form labels, and a logical heading structure solve the majority of accessibility problems and take hours, not weeks, to implement.
  • Accessible websites rank better on Google. Many WCAG requirements align directly with SEO best practices — descriptive alt text, logical heading hierarchy, meaningful link text. Google explicitly states that accessibility improvements often improve crawlability and search performance simultaneously.

We build accessibility into every project from the start. Not because we have to — though increasingly that's true — but because the idea that a potential customer can't use your website because of how it was built is a problem worth solving.

Accessibility is one of those topics that gets filed under "we'll do it later" until something forces the conversation. A complaint, a legal notice, or an audit that turns up dozens of failures. We'd rather you read this before any of that happens.

What Website Accessibility Actually Means

Accessibility means your website can be used by the widest possible range of people, including those with disabilities.

That covers a lot of ground. Most people picture screen readers and blind users when accessibility comes up — but the scope is significantly broader:

  • Visual impairments — blindness, low vision, colour blindness
  • Motor impairments — users navigating by keyboard only, or using voice control, because a mouse is difficult or impossible
  • Cognitive and learning disabilities — dyslexia, ADHD, memory difficulties that affect how information is processed
  • Hearing impairments — affecting users of video content
  • Temporary disabilities — a broken arm, a post-surgery recovery, situational limitations like holding a baby while browsing one-handed
  • Age-related changes — reduced dexterity, declining eyesight, slower processing speeds

The World Health Organisation estimates that 1.3 billion people globally live with a significant disability. In the UK alone, the "purple pound" — the spending power of disabled people and their households — is estimated at over £274 billion annually (Purple, 2023).

An inaccessible website is turning that audience away.

The Equality Act 2010

The Equality Act 2010 prohibits discrimination against people with protected characteristics — disability being one of them. It requires businesses to make "reasonable adjustments" to remove barriers that disadvantage disabled customers. This applies to services, which includes your website.

There is no specific clause that says "your website must meet WCAG 2.1 AA" — but courts and tribunals have consistently interpreted the Act to mean that failure to maintain an accessible website can constitute indirect discrimination. The threshold of "reasonable" depends on the size and resources of your business, but for most SMEs the most common accessibility failures are cheap to fix.

Public Sector Bodies Accessibility Regulations 2018

If you're a public sector body — local authority, NHS provider, charity receiving public funding — you're legally required to meet WCAG 2.1 AA standards and publish an accessibility statement. This is not optional.

European Accessibility Act 2025

From June 2025, the European Accessibility Act (EAA) requires businesses selling to EU customers to meet accessibility standards for digital products and services. If any part of your customer base is in the EU, this applies to you. The EAA aligns broadly with WCAG 2.1 AA.

The practical takeaway: the direction of travel is clear. Accessibility standards are tightening, enforcement is increasing, and the cost of retrofitting an inaccessible site grows every year you leave it.

WCAG 2.1 in Plain English

WCAG stands for Web Content Accessibility Guidelines — the internationally recognised standard, published by the W3C. Version 2.1 is the current benchmark, with 2.2 bringing incremental improvements.

The guidelines are organised around four principles:

Perceivable

Users must be able to perceive all information — nothing should be invisible to all senses.

In practice: images need alt text so screen readers can describe them. Videos need captions. Colour should never be the only way to convey information (a red error message also needs an icon or label). Text needs sufficient contrast against its background.

Operable

Users must be able to operate the interface — every function should be keyboard-accessible.

In practice: every link, button, form field, and menu must be reachable and usable without a mouse. Focus states — the visible outline that shows which element is selected — must be visible. Users must have enough time to read and interact with content (so auto-rotating carousels need pause controls).

Understandable

Content and interface behaviour must be understandable.

In practice: language should be set in the page's HTML so screen readers use the right voice. Error messages on forms need to explain what went wrong and how to fix it. Navigation should be consistent across pages. Nothing should behave unexpectedly.

Robust

Content must be robust enough to work across different assistive technologies.

In practice: clean, valid HTML. Proper semantic structure — `<nav>`, `<main>`, `<footer>`, `<h1>` through `<h6>` used correctly. ARIA attributes where needed, but only where genuinely helpful.

WCAG has three compliance levels: A (minimum), AA (standard target), and AAA (enhanced, rarely required in full). AA is the benchmark for most legal contexts and best practice recommendations.

The Fixes That Make the Biggest Difference

You don't need to solve every WCAG criterion in one go. In our experience, a handful of fixes account for the majority of accessibility failures — and the majority of the real-world impact.

Alt Text on Images

Every meaningful image should have an alt attribute describing what it shows. Decorative images should have an empty alt (`alt=""`) so screen readers skip them. This is also one of the simplest SEO improvements you can make — Google uses alt text to understand and index images.

Colour Contrast

Text must have sufficient contrast against its background to be readable by people with low vision or colour blindness. WCAG AA requires a contrast ratio of at least 4.5:1 for normal text and 3:1 for large text. You can check any colour combination with free tools like the WebAIM Contrast Checker.

This is one of the most commonly failed criteria on small business websites — often because a designer has chosen a stylish pale grey body text that looks elegant but fails the contrast test.

Keyboard Navigation

Try using your website without a mouse. Press Tab to move between interactive elements, Enter or Space to activate them. Can you get to every link, button, and form field? Can you see which element is focused at any point?

If focus styles have been removed with `outline: none` in CSS — which happens surprisingly often for aesthetic reasons — keyboard users lose the ability to navigate entirely. Restore them.

Descriptive Form Labels

Every input field needs a visible, associated label — not just placeholder text (which disappears when you start typing and is not reliably read by screen readers). The label should describe what goes in the field and be programmatically linked to the input via `for` and `id` attributes.

Error messages need to be specific. "Invalid input" is not helpful. "Please enter a valid UK postcode in the format SW1A 1AA" is.

Logical Heading Structure

Headings (`h1` through `h6`) should create a logical outline of the page — not be chosen based on how large you want the text to look. Screen reader users navigate pages by jumping between headings, so a heading structure that skips levels or uses headings purely for styling creates a confusing experience.

"Click here" and "read more" are meaningless out of context. Screen reader users often navigate by pulling up a list of all links on a page — so every link should make sense on its own. "Read our Website Accessibility Guide" is helpful. "Click here" is not.

How to Audit Your Current Site

You don't need to hire an accessibility consultant to get started. These free tools give you a useful baseline:

**WAVE Web Accessibility Evaluator** — enter any URL and get a visual overlay showing errors, warnings, and structural elements. Good for a quick visual sweep.

**Google Lighthouse** — built into Chrome DevTools (right-click → Inspect → Lighthouse tab). Runs an accessibility audit alongside performance and SEO checks. Scores 0–100; aim for 90+.

**axe DevTools** — a Chrome/Firefox extension that gives detailed, actionable results with clear pass/fail criteria mapped to WCAG.

Manual keyboard testing — no tool replaces actually trying to use your site without a mouse. Spend ten minutes navigating your homepage, your contact form, and your main navigation with keyboard only.

A professional Website Audit covers accessibility alongside performance, SEO, and technical health — giving you a single report that prioritises what to fix and in what order.

The Business Case for Accessibility

Beyond legal compliance, there are strong commercial reasons to invest in accessibility.

A Larger, More Loyal Audience

1 in 5 UK adults has a disability. Making your site accessible is, at its most basic, making your site usable by 20% more people. Disabled users are also notably loyal to businesses that work hard to accommodate them — and they talk about it.

Better SEO

Accessible websites are better websites. Logical heading structure, descriptive alt text, fast-loading content, mobile responsiveness, and clean code all contribute to both WCAG compliance and search engine rankings. We've seen accessibility fixes produce meaningful SEO improvements on sites where they're applied systematically.

A website redesign that builds in accessibility from the start will outperform one that tries to bolt it on afterwards — structurally and in search results.

While accessibility litigation is more common in the US (the Americans with Disabilities Act is more prescriptive), UK cases under the Equality Act are increasing. The EAA extends exposure further for businesses with EU customers. The cost of a complaint, an investigation, or a legal dispute vastly exceeds the cost of fixing common accessibility issues.

Better Experience for Everyone

Accessible design is just good design. High contrast text is easier to read for everyone. Captions help anyone watching video in a noisy environment. Keyboard navigation benefits power users and people with temporary injuries alike. Clear form labels reduce mistakes. The improvements compound.

How We Approach Accessibility at Brambla

We don't treat accessibility as a checklist to run at the end of a project. It's built into how we work.

When we design and build a custom website, semantic HTML is standard. Heading structure is planned alongside content hierarchy. Form labels and error states are designed before they're built. Colour choices are tested for contrast before any mockup leaves the design phase.

For existing sites, we include accessibility checks in every Website Audit we produce. Clients typically come away with a prioritised list of fixes — some they can implement themselves, some that need a developer. We're clear about which is which and what the impact of each will be.

If your site was last built more than three years ago and has never been reviewed for accessibility, there's a good chance it has significant failures. That's not a criticism — it's just where the industry was. Standards have moved, expectations have moved, and the legal framework has moved with them.

See our pricing page for a breakdown of audit and build options, or get in touch to discuss where your site currently stands.


Frequently Asked Questions

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

If you serve customers — online or offline — the Equality Act 2010 applies to you. This includes your website. You're required to make "reasonable adjustments" to avoid putting disabled people at a substantial disadvantage. The threshold of what's "reasonable" scales with your business size and resources, but the most common accessibility failures (missing alt text, poor contrast, broken keyboard navigation) are inexpensive to fix and offer no defensible reason to leave unaddressed. From June 2025, the European Accessibility Act adds further obligations if you sell to EU customers.

What WCAG level should I aim for?

WCAG 2.1 AA is the standard benchmark for most business websites and the level referenced in most legal contexts, including the UK's Public Sector Bodies Accessibility Regulations and the European Accessibility Act. Level A is the minimum — there are AA criteria that have meaningful real-world impact and should not be skipped. Level AAA is aspirational and rarely required in full, though individual AAA criteria are worth meeting where feasible. The W3C's full WCAG 2.1 quick reference lists all criteria with explanations and techniques.

Will fixing accessibility actually help my SEO?

Yes, meaningfully so in many cases. Google's crawlers are, in some ways, the ultimate accessibility user — they can't see images, rely on HTML structure to understand page hierarchy, and depend on meaningful link and heading text to interpret content. Alt text, logical heading structure, descriptive link text, and clean semantic HTML all contribute to both accessibility compliance and search performance. Google's own documentation acknowledges that accessibility improvements regularly have positive SEO side effects.



For a comprehensive deep dive into all aspects of web accessibility, read our Complete Web Accessibility Guide.

If you'd like an honest view of where your current website stands on accessibility — alongside performance and SEO — our Website Audit is a good starting point. Or get in touch and we'll have a conversation first.

Tags

accessibilityweb-designcompliancewcag
SB

Sam Butcher

Founder, Brambla

Sam is the founder of Brambla (SDB Digital Ltd), a creative digital agency based in Devon. He works directly with tradespeople, professional services and local businesses across Devon, Cornwall, Kent and London to build websites that generate real enquiries.

READY TO GROW YOUR BUSINESS?

Whether you need a new website, SEO, or a full digital marketing strategy — we're here to help.

START A PROJECT