Accessibility

Website accessibility for UK charities and small businesses: where to start

Around one in four people in the UK report a disability. Here's a practical starting point for making your website work for them, including ten checks you can do this afternoon.

Around one in four people in the UK report a disability, according to the government's Family Resources Survey. Some are blind or partially sighted. Some are deaf. Many have conditions you can't see, such as dyslexia, arthritis, migraines or anxiety. And almost everyone needs some kind of accessibility help at some point, even if it's only reading a screen in bright sunlight or watching a video on a noisy train.

If your website doesn't work for these visitors, you're turning away a quarter of your audience. For a charity or a community organisation, that can mean turning away the very people you were set up to help.

The good news is that you don't need to be an expert to make a real start.

We're web people, not lawyers, so treat this as orientation rather than legal advice.

  • The Equality Act 2010 requires service providers in Great Britain to make reasonable adjustments so disabled people aren't put at a substantial disadvantage. Your website is widely treated as part of the service you provide.
  • Public sector bodies have specific duties under the Public Sector Bodies (Websites and Mobile Applications) Accessibility Regulations 2018, including meeting the WCAG standard and publishing an accessibility statement.
  • The European Accessibility Act has applied since 28 June 2025 to certain products and services sold to consumers in the EU, including ecommerce. If you sell into the EU, check whether it affects you.

Whatever your legal position, the standard everyone measures against is the same.

WCAG 2.2 in plain English

The Web Content Accessibility Guidelines, published by the W3C, are the international standard. Version 2.2 became a W3C Recommendation in October 2023, and most organisations aim for level AA.

The guidelines are built on four principles. Your content must be:

  • Perceivable: people can see or hear it, whatever their senses. Think alt text, captions and contrast.
  • Operable: people can use it, however they move. Think keyboard access, enough time and nothing that flashes.
  • Understandable: people can make sense of it. Think plain language, predictable navigation and clear error messages.
  • Robust: it works with assistive technology, now and in future. Think valid, well-structured code.

WCAG 2.2 added several criteria that are especially relevant to small sites, including minimum sizes for click targets, making sure focused elements aren't hidden behind sticky headers, and not forcing people to solve puzzles or remember passwords to log in.

Ten checks you can do this afternoon

You don't need special software for most of these. Set aside an hour and work through your home page and your most important form.

1. Put the mouse away

Use only the Tab, Shift and Tab, Enter and arrow keys. Can you reach every link, button and form field? Can you always see where you are?

2. Zoom to 200%, then 400%

Text should grow without being cut off, and at 400% the page should reflow into a single column without sideways scrolling.

3. Check your contrast

Normal text needs a contrast ratio of at least 4.5:1 against its background. Pale grey on white is the usual culprit, and free contrast checkers will give you the number in seconds.

4. Read your alt text

Every image that carries meaning needs a short description. Decorative images should have empty alt text so screen readers skip them.

5. Look at your headings

Headings should form a sensible outline: one main heading, then sections and subsections in order. Don't choose heading levels for their size.

Screen reader users often skim a list of links. "Click here" and "read more" tell them nothing. "Read our refund policy" does.

7. Break your forms

Leave a required field empty and submit. Is the error clear, close to the field and announced to assistive technology? Does every field have a visible label, not just placeholder text?

8. Watch a video with the sound off

Are there accurate captions? Does anything start playing on its own?

9. Try a screen reader

VoiceOver is built into Macs and iPhones, TalkBack into Android, and NVDA is free for Windows. Ten minutes listening to your own home page is an eye-opener.

10. Check your click targets

Small links packed close together are hard to hit with a finger or an unsteady hand. WCAG 2.2 sets a minimum target size, and bigger is usually better.

Automated tools help, but they're not enough

Tools such as WAVE, axe and Google Lighthouse are excellent at finding missing alt text, low contrast and code errors. But many barriers, such as confusing wording, an illogical focus order or unhelpful alt text, need a person to spot them. Use the tools to find the easy wins, then test by hand.

Publish an accessibility statement

An accessibility statement explains how accessible your site is, what you know isn't working yet and how people can get help or report a problem. It's required for public sector sites and good practice for everyone else. It also shows visitors you take the issue seriously.

Make it a habit, not a project

Accessibility isn't a one-off fix. Every new page, form and campaign can introduce new barriers. Build a quick check into how you publish, include accessibility in every brief to designers and developers, and, when you can, pay disabled people to test your site. They will find things no checklist will.

If you'd like help, Liberty Web Support can review your site and help you put things right, starting with the fixes that will make the biggest difference.

Written by Liberty Web

Liberty Web Ltd is a British web agency building technology for good: websites, AI agents and automation, ecommerce and website support.

Want an accessibility review?

Liberty Web Support can check your site, explain what we find in plain English and help you fix what matters most.