WCAG 2.2 Quick Wins for UK Small Business Websites

Why WCAG 2.2 matters for your UK small business

One in four UK adults has a disability. That is over 14 million potential customers who may struggle to use your website right now — and most will leave without telling you why. But accessibility is not just about doing the right thing. It is a legal requirement under the Equality Act 2010, and if you sell to EU customers, the European Accessibility Act (EAA) added a second enforcement layer from 28 June 2025.

The good news? You do not need a £10,000 audit to start. Research from the WebAIM Million shows that 96% of all detected accessibility errors come from just 6 issue types. Fix these six things and you have eliminated the vast majority of what automated scanners catch. Most can be resolved in a weekend sprint.

This guide gives you the practical, no-nonsense steps to fix each one — with time estimates, free tools, and the UK legal context you need to understand what is at stake.

The 6 failures that account for 96% of all errors

The WebAIM Million report scans the top million home pages annually. Year after year, the same six failures dominate. Here they are, ranked by prevalence, along with how to fix each one.

Quick Win #1 — Fix colour contrast (1–2 hours)

Found on 79.1% of home pages — the single most common failure. Light grey text on white. White text on light blue backgrounds. Yellow text on white. These all fail WCAG's minimum contrast requirement of 4.5:1 for normal text and 3:1 for large text.

The fix is usually a handful of colour values in your CSS. Use the free WebAIM Contrast Checker to test your current colours against WCAG AA requirements. Aim for 7:1 if you can — it is easier to read for everyone, not just people with low vision. Better contrast also reduces bounce rates; readability is an SEO signal.

Impact: Benefits users reading in bright sunlight, older users, people with low vision, and anyone squinting at their phone on a train.

Quick Win #2 — Add alt text to meaningful images (30 min — 2 hours)

Found on 55.5% of home pages. When a screen reader encounters an image with no alt attribute, it either skips it entirely or reads out the file name — usually something like "IMG_4392.png". Neither is helpful.

Every <img> tag needs an alt attribute that describes what the image conveys. Decorative images (pure dividers, visual flourishes) should have alt="" so screen readers skip them. Your logo's alt text should be your business name. A product photo should describe the product.

SEO bonus: Alt text helps Google understand image content and improves visibility in image search. Start with your top 20 most-visited pages.

Quick Win #3 — Label every form field (1–2 hours)

Found on 48.2% of home pages. Placeholder text ("Enter your name") is not a label. It vanishes when the user starts typing and is ignored by many screen readers. Every input needs an associated <label> element with a for attribute matching the input's id.

Error messages matter too. "Please enter a valid email address" passes. A red border with no explanation fails. The fix here is straightforward HTML — no design changes required.

Impact: Screen reader users, voice-control users, mobile users, and your conversion rates all benefit. One study found a 22% increase in form success rates with proper inline validation.

Quick Win #4 — Restore visible keyboard focus indicators (30 min — 1 hour)

Many sites remove focus outlines (outline: none in CSS) for aesthetic reasons. This breaks keyboard navigation entirely. If you cannot see where you are when tabbing through a site with your keyboard, neither can someone who cannot use a mouse.

WCAG 2.2 added a new criterion — Focus Not Obscured (2.4.11) — which means sticky headers and cookie banners must not hide focused elements. Restore the outline or add custom :focus-visible styles with at least 3:1 contrast. Use scroll-margin-top to prevent sticky header overlap.

Test it now: Unplug your mouse. Tab through your site. Can you see where you are on every element? If not, this is your first fix.

Quick Win #5 — Replace vague link text (30 min)

Found on 45.4% of home pages (empty links) / 29.6% (empty buttons). "Click here", "Read more", and "Learn more" are meaningless out of context. A screen reader user tabbing through a list of "click here" links has no idea where any of them go.

Replace vague text with descriptive alternatives: "View our accessibility audit pricing" instead of "Learn more". For icon-only links (social media icons, hamburger menus), add an aria-label attribute.

Quick Win #6 — Add document language and logical heading structure (30 min)

Found on 15.8% of home pages (missing language). If your <html> tag has no lang attribute, screen readers do not know what language to use for pronunciation. Fix: change <html> to <html lang="en"> (or "en-GB" for British English).

Headings should follow a logical hierarchy: one <h1> per page, followed by <h2> sections, then <h3> subsections. Do not skip levels. Screen reader users navigate by headings — this structure is essential.

WCAG 2.2 — The 6 new criteria that matter for AA compliance

WCAG 2.2 added nine new success criteria. If you already meet WCAG 2.1 AA, these are the only additions you need. The six that matter most for small business websites:

• Focus Not Obscured (2.4.11) — Sticky headers and cookie banners must not hide the focused element.
• Dragging Movements (2.5.7) — Sliders, carousels, and drag-drop interfaces need click/button alternatives.
• Target Size Minimum (2.5.8) — Interactive targets must be at least 24×24 CSS pixels. Small social icons and close buttons often fail this.
• Consistent Help (3.2.6) — Help/contact links must appear in the same relative position on every page.
• Redundant Entry (3.3.7) — Multi-step forms should pre-fill repeated fields (name, address, email).
• Accessible Authentication (3.3.8) — No puzzle CAPTCHAs without alternatives; allow paste, password managers, and passkeys.

Note: criterion 4.1.1 Parsing was removed as obsolete — modern browsers handle it natively.

Your free 30-minute accessibility audit

You do not need expensive tools to find most issues. Start with this sequence:

1. Run WAVE — Install the free WAVE browser extension and scan your homepage. It flags contrast errors, missing alt text, and structural issues instantly.
2. Run Lighthouse — Open Chrome DevTools (F12), go to the Lighthouse tab, run an Accessibility audit. It gives you a score and a prioritized list.
3. Keyboard test — Unplug your mouse. Tab through every page. Can you reach every link, button, and form field? Can you see where focus is at all times?
4. 200% zoom test — Zoom your browser to 200%. Does the layout break? Can you still read and navigate everything?
5. Screen reader spot-check — Turn on VoiceOver (Mac) or NVDA (Windows) and listen to your homepage. Is the reading order logical? Are images described?

30-Day Accessibility Sprint Plan

Fixing accessibility does not have to be overwhelming. Break it into four weekly sprints:

• Week 1: Run WAVE on your top 10 pages. Fix colour contrast and add alt text to all meaningful images.
• Week 2: Fix form labels, replace vague link text, restore keyboard focus indicators.
• Week 3: Test keyboard navigation across all pages. Fix target sizes for mobile. Check heading hierarchy.
• Week 4: Screen reader test (VoiceOver or NVDA). Publish an accessibility statement. Consider a professional WCAG audit for formal documentation.

DIY vs Professional Audit — Which do you need?

Both approaches have their place. Here is how they compare:

Recommendation: Start with a DIY audit to fix the obvious issues. If you have had a complaint, sell to EU customers, or want formal documentation, get a professional WCAG audit for defensible evidence of compliance efforts.

UK Legal Context — What you need to know

Three laws govern website accessibility in the UK. Here is how they apply to your business:

• Equality Act 2010 — Applies to all UK service providers. Requires "reasonable adjustments" for disabled people. WCAG 2.2 Level AA is the benchmark courts and the EHRC use. Unlimited compensation via county court claims.
• PSBAR 2018 — Public sector bodies only (government, NHS, schools, councils). WCAG 2.2 Level AA is a legal requirement. EHRC investigations and public notices for non-compliance.
• European Accessibility Act (EAA) — Applies to UK businesses selling to EU customers. Based on EN 301 549 (WCAG 2.1 AA). Maximum penalty: €900,000 or 4% of annual turnover.

Key distinction: If you only serve UK customers, the Equality Act is what matters. If you sell to EU customers online, the EAA applies too. PSBAR only applies to public sector bodies.

Frequently asked questions

Next steps

If you want a quick free check of your current accessibility standing, run our free AI accessibility scan. For a thorough professional assessment with formal documentation, get a professional WCAG audit with specific remediation guidance. If you are building a new website and want accessibility baked in from day one, see our accessibility services or view our website packages.