Website accessibility in the UK: a practical guide to WCAG 2.2

What website accessibility means, the standard UK organisations aim for, your legal duties, and practical steps to make your site usable by everyone.

By the UK Technology Hub teamPublished 4 minute read

The short answer

An accessible website works for people with visual, hearing, motor and cognitive impairments, including those using screen readers, keyboards or zoom. The standard most UK organisations aim for is WCAG 2.2 at level AA. Businesses providing services to the public have duties under the Equality Act 2010 not to discriminate against disabled people, which includes their websites.

Millions of people in the UK have a disability, and many more have temporary or situational limitations, such as a broken wrist, bright sunlight on a screen or a slow connection. An accessible website serves all of them and is usually easier for everyone else to use too.

What is WCAG?

The Web Content Accessibility Guidelines (WCAG) are the international standard for digital accessibility, published by the World Wide Web Consortium. The current version, WCAG 2.2, was published in October 2023. It's organised around four principles: content must be perceivable, operable, understandable and robust.

Each guideline has success criteria at three levels: A, AA and AAA. Level AA is the usual target for businesses and is the level required of UK public sector websites under the Public Sector Bodies Accessibility Regulations 2018.

What does the law say for businesses?

The Equality Act 2010 requires service providers to make reasonable adjustments so disabled people aren't put at a substantial disadvantage. This applies to services provided online. The Act doesn't name a technical standard for private businesses, but WCAG 2.2 AA is the widely accepted benchmark for showing you've taken accessibility seriously. If you're unsure about your obligations, take legal advice.

The most common accessibility problems

  • Low colour contrast, such as light grey text on white. WCAG AA asks for a contrast ratio of at least 4.5:1 for normal text. Our guide to choosing brand colours explains how to check this.
  • Missing image descriptions, so screen reader users don't know what an image shows.
  • Forms without proper labels, or errors explained only by colour.
  • Things that can't be used with a keyboard, such as menus, sliders and pop-ups.
  • No visible focus outline, so keyboard users can't see where they are.
  • Unclear link text like "click here" repeated across a page.
  • Videos without captions.
  • Headings used for styling rather than structure, which confuses screen reader navigation.

WCAG 2.2 additions worth knowing

WCAG 2.2 added criteria that matter for everyday sites, including:

  • Focus not obscured: sticky headers and cookie banners mustn't hide the element that has keyboard focus.
  • Target size: buttons and links should be large enough to tap, at least 24 by 24 pixels in most cases.
  • Accessible authentication: logins shouldn't rely on memory puzzles without alternatives, such as allowing password managers to paste.
  • Redundant entry: don't make people re-enter information they've already given in the same process.

How to test your site

  1. Use only a keyboard. Press Tab through each page. Can you reach and use everything, and can you always see where you are?
  2. Zoom to 200%. Does content still fit without sideways scrolling or overlapping?
  3. Run an automated checker, such as WAVE or axe. These catch roughly a third of issues, so they're a starting point.
  4. Try a screen reader, such as NVDA on Windows or VoiceOver on Mac and iPhone.
  5. Ask real users with disabilities for feedback where you can.

Quick wins you can make this week

  • Add meaningful alt text to important images, and leave it empty for purely decorative ones.
  • Replace "click here" and "read more" links with text that describes the destination.
  • Check every form field has a visible label, not just placeholder text.
  • Add captions to videos, and transcripts to podcasts.
  • Make sure headings follow a logical order, with one main heading per page.

Build it in from the start

Fixing accessibility after launch is far more expensive than designing for it. When we design and build sites through our web development and UI/UX design services, we choose accessible colours, write proper markup, label forms and test with keyboards and automated tools before launch. Good accessibility overlaps heavily with good UX design and with search optimisation, since clear structure helps search engines too.

Publish an accessibility statement

An accessibility statement explains the standard you aim for, any known issues and how people can contact you if something doesn't work for them. It shows good faith and gives users a route to help.

Frequently asked questions

Are accessibility overlays a quick fix?

Generally no. Overlay widgets don't fix the underlying code and can interfere with assistive technology. Fixing the site itself is the reliable approach.

Does accessibility help SEO?

Often, yes. Clear headings, descriptive links, alt text and fast, well-structured pages help both people and search engines.

How often should we test accessibility?

Test before launch, then whenever you add new templates or features, and review the whole site at least once a year.

This guide is general information, not legal, tax or financial advice, and details such as prices, features and rules can change. Product and company names mentioned are trademarks of their respective owners and are used only to identify those products; UK Technology Hub is not affiliated with or endorsed by them.

Related guides

How much does a website cost in the UK?

What drives the price of a business website, typical UK market ranges, the ongoing costs people forget, and how to get a quote you can rely on.

All websites & web design guides