Skip to main content
HTREASURE LTD

Technology guides

Website Accessibility: A WCAG 2.2 Guide for Small Businesses

Make your website usable for everyone. Learn the WCAG 2.2 basics, from colour contrast and alt text to keyboard access, and why accessibility is good business.

Published

Around one in four people in the UK has a disability, and many more have temporary or situational limitations, such as a broken arm or bright sunlight on a phone screen. An accessible website works for all of them, and it is usually easier to use for everyone else too.

What is WCAG 2.2?

The Web Content Accessibility Guidelines (WCAG) are the international standard for web accessibility. Version 2.2 was published in October 2023. Most organisations aim for level AA.

Public sector websites in the UK must meet accessibility regulations. For businesses, the Equality Act 2010 requires service providers to make reasonable adjustments for disabled people, and an accessible website is a practical way to do that.

Quick wins

Text and colour

  • Colour contrast of at least 4.5:1 for normal text and 3:1 for large text.
  • Do not rely on colour alone, for example red text for errors. Add an icon or a message.
  • Let text resize to 200% without breaking the layout.

Images

  • Add alt text to meaningful images that describes what matters about them.
  • Use empty alt text for purely decorative images so screen readers skip them.

Keyboard access

  • Everything must work with a keyboard alone: menus, forms, pop-ups and cookie banners.
  • Keep a clearly visible focus outline.
  • WCAG 2.2 adds that the focused item must not be hidden behind sticky headers or banners.

Forms

  • Every field needs a visible label.
  • Explain errors clearly and say how to fix them.
  • WCAG 2.2: do not make people re-enter information they already gave in the same process, and avoid memory puzzles at login.

Touch targets

WCAG 2.2 sets a minimum target size of 24 by 24 pixels for buttons and links, or enough space around them.

Structure

  • Use proper headings (H1, H2, H3) in order.
  • Write descriptive link text, not "click here".
  • Caption videos and provide transcripts for audio.

How to test your website

  • Navigate a page using only the Tab, Enter and arrow keys.
  • Zoom the browser to 200%.
  • Run a free automated checker such as WAVE or Lighthouse. These catch some issues, not all.
  • Try a screen reader: NVDA is free for Windows, and Narrator is built in.

Publish an accessibility statement

Explain the standard you aim for, any known issues and how people can contact you for help or another format. See our own [accessibility statement](https://htreasure.com/legal-accessibility).

Frequently asked questions

Does an accessibility overlay make my site compliant?

No. Overlays cannot fix underlying problems in your code and content, and can get in the way of assistive technology.

How we can help

Our [website development](https://htreasure.com/services/website-development) team builds websites with accessibility designed in from the start.