Inclusive web wins

Using this resource

Accessibility is about making sure everyone can access, enjoy and act on your content. This guide shows how the Web Content Accessibility Guidelines (WCAG 2.2) translate into real-life impact — and gives you simple steps you can take today, no coding required.

Each section builds on the last, guiding you from a tech-jargon-free understanding of WCAG 2.2 to simple ways you can begin making a difference.

We’ll explore:

why WCAG 2.2 matters
how common “checkbox” requirements show up in real life
answers to FAQs you might have
and quick wins you can put into action straight away

By the end, you’ll have a clear picture of what WCAG 2.2 means in practice — plus some steps to make your website more inclusive today.

Before you start… clear some time in your calendar, find a focussed space, get a fresh glass of water and take a few grounding breaths 🍃

Understanding

Beyond the checklist

Accessibility isn’t an optional extra - it’s a real-world necessity. When we design and build to the Web Content Accessibility Guidelines (WCAG) 2.2, we’re not just “ticking boxes”; we’re making everyday life easier for us all. 🌱

Here’s how the principles behind WCAG 2.2 show up in real people’s lives, plus practical steps you can take today.

Why WCAG 2.2 matters (in plain English)

Standards give your team a shared, testable way to deliver an inclusive website. Meeting WCAG 2.2 helps you:

Reach more people (including those using assistive tech)
Improve usability for all visitors on any device and in any light
Reduce legal and reputational risk
Boost SEO and conversion through clearer structure and content

In short: accessible websites are better websites.

Everyday examples

How common ‘checkbox’ requirements show up in real life. Expand each box below and tick it off after you’ve read through.

Skip the repetition for screen-reader users

No one should have to listen to every navigation menu on every page, yet this can be the reality for screen-reader users without the correct elements in place.

Don’t rely on colour alone

If a link changes only colour on hover, low-vision and colour-blind users might miss it.

Make contrast a given, not a gamble

Pale grey text on off-white isn’t “elegant”; it’s unreadable for people with visual impairments or anyone checking their screen in bright daylight. Insufficient contrast isn't just a design flaw - it's a user barrier.

Caption video and provide transcripts

Videos that rely on sound are inaccessible for deaf and hard-of-hearing users - and even those on a noisy train, in a quiet office, or who simply prefer reading.

Design for keyboards, not just mice

Not everyone uses a mouse to get around the web so creating keyboard-friendly websites is…key! Or rather, tab key.

Keep layouts calm

Busy screens, intricate type and flashing animations can overload neurodivergent users (and anyone who’s tired or multitasking).

Be consistent with help

Visitors naturally look for help or contact details in the same place on every page. If these links move around, people waste time and energy searching instead of getting the support they need. This is especially important if your website is a lifeline for accessing critical services.

Make it work for mobile

On mobile, small buttons and crowded layouts are hard for anyone to use — and especially tricky for people with limited dexterity or conditions that cause shaking. With limited space to tap, users can end up zooming in, re-tapping, and feeling pretty irritated.

Accessible choices respect visitors’ time, needs and attention - and they show you care. By building with accessibility in mind, every click, scroll and tap becomes an opportunity for inclusion.

Facts

Get the facts

Now, let’s answer the common questions of what the WCAG 2.2 requirements are and where you stand.

What is WCAG 2.2?

It’s the current version of the Web Content Accessibility Guidelines - an international standard for making digital content more accessible.

Do all UK organisations need to comply?

Public sector bodies must meet accessibility regulations; all organisations have responsibilities under the Equality Act to make reasonable adjustments. Even where it’s not mandated, meeting WCAG makes your site easier to use and that benefits everyone.

How do I know if we meet WCAG 2.2?

Google Lighthouse, built into Chrome DevTools, lets you run a quick automated check — though it won’t catch everything (like keyboard focus or captions). Automated tools are a good starting point, but they typically only cover around 30–40% of issues. To get the full picture, you’ll need a proper audit that combines automated testing with manual checks (including screen readers and keyboard navigation).

The W3C WCAG 2.2 Quick Reference also provides a full breakdown of the requirements if you’d like to self-check — though it can feel overwhelming. That’s why many organisations choose a professional audit. And remember: even by starting with the quick edits in this guide, you’re already making a difference.

Action

Quick wins you can action now

Now’s the part you’ve been waiting for—time to roll up your sleeves and dive into inclusive web wins! We’ve outlined some practical steps you can take in most website editors, along with a few structural changes that might require a bit more planning.

Let’s start with some quick wins to give your site an instant breath of fresh air.

Five quick wins:

Make links visibly distinct in multiple ways

On hover, pair colour changes with an underline, outline, heavier weight or icon so interactive elements are unmistakable.

Check colour contrast

Use a free colour contrast checker to make sure your text and buttons are legible in all conditions.

Caption your videos and share transcripts

Enable captions on your video's and include a transcript - this helps boost SEO too.

Keep content clear and calm

Favour clear hierarchy, consistent patterns and gentle motion to create a calm, easy-to-navigate website.

Be consistent with help and contact details

Keep help and contact options in a predictable place across pages (ideally in the header and footer).

Go deeper

Depending on how much control you have over your website's structure, here are a couple more in-depth steps you can take:

Skip the repetition for screen-reader users

Add clear landmarks (header, nav, main, footer) and a visible “Skip to content” link so people can jump straight to what matters.

Make it work for mobile

Create bigger tap targets and increased spacing on mobile to give fingers (and thumbs) more room for error.

Well done

We really hope that through this process you've gained a deeper understanding of the impact of following WCAG 2.2 and have begun making changes to the online experience you provide.

We'd love to hear how you've got on! Send us an email – we read all our feedback and are always looking to improve our resources 🙏

hello@designimpact.studio

Next steps

You’ve just made a great start. Most organisations stop at “good intentions” — but you’re making a difference.

The next step is to conduct an audit of your site against the WCAG 2.2 guidelines and continue to make the relevant fixes.

How we can help

If you’d like to know exactly how your site measures up, we offer a £200 Accessibility Audit. You’ll get:

A prioritised list of fixes
Screenshots and plain-English explanations
A clear roadmap you can hand to your team or developer

If you’d like to explore what that could look like for your organisation, you can drop us an email or book a call here.

If you’d rather keep going solo, that’s brilliant too — we hope this resource has set you on the path to continue to make inclusive website wins.

🎉

Reset checklist

Accessibility Audit

We’re offering discounted website accessibility audits for a limited time. Book a free, no-obligation consultation with Design Impact.

Book a consultation