WCAG Compliance for UK Businesses 2026: Legal Requirements and Audit Checklist

UK businesses are legally required to meet WCAG 2.1 AA accessibility standards under the Equality Act 2010. Failure to comply creates discrimination liability. This guide covers the specific legal thresholds, the 12 most common WCAG failures on UK SME websites, and a practical 2-hour audit checklist you can run today. Launchwork Digital builds every site to WCAG 2.2 AA as standard from our London office — accessibility baked into the design phase, not retrofitted after launch.

According to the Office for National Statistics, **14.6 million people in the UK have a disability** — roughly 22% of the population. An inaccessible website excludes roughly one in five of your potential customers before they read a single word of your content. The business and legal case for accessibility has never been stronger. This guide covers what the law requires, which failures are most common, and how to fix them.

The Legal Framework: Equality Act 2010 and What It Means for Your Website

The **Equality Act 2010** is the primary legislation. Section 29 requires businesses to make "reasonable adjustments" so that disabled people are not put at a substantial disadvantage when accessing services — and courts have consistently ruled that digital services fall within its scope. In 2019, the Royal National Institute of Blind People (RNIB) successfully supported legal action against Domino's Pizza over an inaccessible app. No exemption exists for small businesses. While most UK accessibility cases settle before reaching full trial, RNIB reports that legal fees alone for defending an accessibility discrimination claim typically run £15,000–£50,000, making proactive compliance far cheaper than reactive litigation. **The Public Sector Bodies Accessibility Regulations 2018** require government, NHS, and education sector websites to formally comply with WCAG 2.1 AA and publish an accessibility statement. **The European Accessibility Act (EAA)**, effective June 2025, extends mandatory WCAG 2.2 compliance to private sector businesses in e-commerce, banking, transport, and digital media when they serve EU customers. If your checkout accepts EU payment methods or ships to EU addresses, the EAA applies to you. **What "reasonable adjustments" means in practice:** The Equality Act does not set a specific technical standard, but WCAG 2.2 AA is the benchmark courts and the Information Commissioner use when assessing compliance. WCAG 2.2 AA is the standard any UK business should target.

WCAG Failure Rates: The Data UK Businesses Need to See

A 2024 WebAIM Million report (covering 1 million websites globally, with UK subset analysis) found that **96.3% of home pages had detectable WCAG 2.1 AA failures**, averaging 56 errors per page. The most common failures: - **Low contrast text:** 83% of pages - **Missing image alt text:** 55% of pages - **Missing form labels:** 48% of pages - **Empty links (no descriptive text):** 44% of pages - **Missing document language:** 28% of pages UK SME websites show comparable failure rates. These are not edge-case failures — they are the structural errors that make websites unusable for screen reader users, keyboard-only users, and users with low vision.

!Person using assistive technology with screen reader software on laptop — testing website accessibility *Photo by SHVETS production / Pexels*

The 12 Most Common WCAG 2.1 AA Failures on UK SME Websites

These are the failures that appear most consistently in automated accessibility audits on UK business websites — and most of them are fixable in hours, not weeks. **1. Missing or inadequate alt text on images.** Images without alt text are invisible to screen readers. Decorative images should use `alt=""` so screen readers skip them. For linked images, the alt text should describe the destination, not the image itself. **2. Insufficient colour contrast.** Text that does not meet the 4.5:1 contrast ratio against its background fails WCAG 2.2 AA. Light grey text on white backgrounds — popular in minimalist design — is a frequent offender. Large text (18pt+ or 14pt bold) requires a 3:1 ratio minimum. **3. Missing form labels.** Every form input needs a visible, programmatically associated label using `for`/`id` attributes or `aria-labelledby`. Placeholder text does not substitute for a label — it disappears when the user starts typing. **4. Keyboard navigation traps.** Modal dialogs, dropdown menus, and date pickers that trap keyboard focus block keyboard-only users completely. Implement proper focus management: move focus into modals on open, trap focus within them while open, and return focus to the trigger element on close. **5. Auto-playing media without controls.** Videos or audio that play automatically without user consent are a Level A failure if they run for more than 3 seconds without a pause mechanism. **6. No skip navigation link.** Keyboard and screen reader users have to tab through every navigation item on every page unless a skip link is provided. Add a visually hidden "Skip to main content" link as the first focusable element on every page. **7. Focus indicators removed or invisible.** Never use `outline: none` without providing a custom focus style that meets the minimum 2px, 3:1 contrast requirement. Many designers remove the default browser outline because it does not match their design system — this makes the site completely unusable for keyboard navigation. **8. Tables used for layout, not data.** Layout tables are read aloud by screen readers in source order, which is often meaningless. Use CSS for layout. Mark up data tables with `<th scope="col">` and `<th scope="row">` attributes. **9. PDF documents without accessibility tags.** Untagged PDFs are read by screen readers as a stream of raw text with no structure. Export PDFs with accessibility tags enabled from the source document. **10. Touch targets too small on mobile.** Under WCAG 2.2 AA, interactive elements must be at least 24×24 CSS pixels. Apple's Human Interface Guidelines recommend 44×44px as the target size for comfortable use. **11. Missing document language declaration.** The `<html lang="en">` attribute tells assistive technologies which language to use for pronunciation. Missing this causes screen readers to default to the user's system language. **12. Colour used alone to convey meaning.** Error states that only use red text (without an icon or text label) are invisible to colour-blind users. Always pair colour indicators with a secondary cue.

A 2-Hour Accessibility Audit Checklist for UK Businesses

This checklist requires no specialist tools and can be completed in approximately 2 hours. It identifies the most commercially significant accessibility barriers on your website. **Automated scan (30 minutes):** 1. Install the WAVE browser extension from WebAIM (wave.webaim.org) — free 2. Run WAVE on your homepage, primary service/product page, contact page, and any page with a form 3. Note every red (error) flag — these are Level A and AA failures 4. Check the Contrast Errors section specifically — this is the most common failure category 5. Run Google Lighthouse (F12 → Lighthouse tab → Accessibility) on the same pages. Target score 90+. **Keyboard navigation test (20 minutes):** 1. Disconnect your mouse 2. Press Tab to move through all interactive elements 3. Verify every element receives a visible focus indicator 4. Open any modal, dropdown, or form — confirm you can complete and close it without a mouse 5. Attempt your primary user journey (submitting a form, completing a purchase) without touching the mouse **Content and structure check (30 minutes):** 1. Verify every image has descriptive alt text (right-click in browser → Inspect → check `alt` attribute) 2. Confirm every form field has an associated `<label>` element 3. Check heading structure: one `<h1>`, logical `<h2>` and `<h3>` hierarchy, no skipped levels 4. Test colour contrast on your body text and key UI elements at webaim.org/resources/contrastchecker 5. Verify the `<html lang>` attribute is set on every page **Mobile and touch test (20 minutes):** 1. On a smartphone, attempt to tap every interactive element — note anything that requires precision tapping 2. Increase text size to 200% in browser settings — verify the page remains usable 3. Check that no content overlaps or becomes unreadable at larger text sizes

Free Tools to Check Your Website Accessibility

**WAVE (Web Accessibility Evaluation Tool)** — A browser extension from WebAIM that adds inline annotations showing exactly where each failure occurs. Excellent for identifying missing labels, contrast failures, and heading structure issues. Available for Chrome and Firefox. **axe DevTools** — Available as a free browser extension. Lower false-positive rate than Lighthouse, with clear remediation guidance for each issue. Used by accessibility specialists in large organisations. **Google Lighthouse** — Built into Chrome DevTools (F12 → Lighthouse tab). Runs an accessibility audit alongside performance, SEO, and best practices checks. Aim for a score of 90 or above. Scores below 70 indicate significant structural issues. **WebAIM Contrast Checker** — Paste in your foreground and background hex codes to verify contrast ratios for text at webaim.org/resources/contrastchecker. **NVDA** (Windows, free) — The most widely used screen reader globally. Download from nvaccess.org. Use with Chrome or Firefox to experience your site as a screen reader user.

How Much Does an Accessibility Fix Cost?

The cost depends heavily on the current state of your site and how the work is approached. **A professional WCAG 2.2 AA audit** for a small-to-medium UK business website typically costs **£1,500–£5,000**, with remediation work on top. **Common fix cost ranges:** - Adding missing alt text and form labels across a 20-page site: £200–£600 (developer day) - Fixing colour contrast issues across a design system: £500–£2,000 (designer + developer) - Keyboard navigation remediation for complex interactive components: £1,000–£5,000 depending on component count - Full WCAG 2.2 AA audit and remediation for a medium site (15–50 pages): 2–4 weeks of developer time **Building accessible from the start** adds roughly 5–10% to project cost compared to an equivalent non-accessible build, but avoids the substantially higher cost of retrofitting compliance later. Our web development services include WCAG 2.2 AA compliance as standard on every project. Our UI/UX design for accessibility addresses accessibility at the design stage, before code is written — which is significantly more efficient than retrofitting.

Is My Website Legally Required to Be Accessible in the UK?

Yes. The Equality Act 2010 requires all UK businesses to make reasonable adjustments so that disabled people can access their services — and courts have consistently ruled that websites are services within the Act's scope. There is no exemption for small businesses. The standard against which compliance is assessed is WCAG 2.2 AA. For public sector organisations (government, NHS, universities), the **Public Sector Bodies Accessibility Regulations 2018** impose additional requirements: formal WCAG 2.1 AA compliance, a published accessibility statement, and regular monitoring. Enforcement is handled by the Cabinet Office. For private sector businesses selling to EU customers, the **European Accessibility Act** (June 2025) extends mandatory WCAG 2.2 compliance to e-commerce, banking, transport, and digital media.

What Is WCAG 2.2 and What Are the New Requirements?

WCAG (Web Content Accessibility Guidelines) is an internationally recognised standard published by the W3C. WCAG 2.2, published in October 2023, adds **9 new success criteria** to WCAG 2.1 with particular focus on: - **Mobile usability:** Minimum touch target size (24×24px AA), dragging movement alternatives - **Cognitive accessibility:** Accessible authentication (no memory-based puzzles required), redundant entry prevention - **Focus visibility:** Focus indicators must not be completely obscured by sticky headers; focus appearance must meet minimum size and contrast requirements For UK businesses, WCAG 2.2 AA is the current benchmark for Equality Act compliance and the minimum required by the EAA for organisations serving EU customers.

Frequently Asked Questions

**Is my website legally required to be accessible in the UK?** Yes. The Equality Act 2010 requires UK businesses to make reasonable adjustments so disabled people can access their services — and websites are services under the Act. The RNIB has supported successful legal action against inaccessible digital services. There is no size exemption: a sole trader's website falls within the Act's scope. The standard courts reference is WCAG 2.2 AA. The European Accessibility Act (June 2025) extends mandatory compliance to private sector e-commerce, banking, and digital media businesses that serve EU customers. Non-compliance carries civil liability, regulatory enforcement, and reputational risk. A WCAG 2.2 audit costs £1,500–£5,000 — a fraction of the cost of defending a single claim.

**What is WCAG 2.1 AA and does it apply to small businesses?** WCAG 2.1 AA is the 2018 version of the Web Content Accessibility Guidelines, covering four principles: perceivable, operable, understandable, and robust. It applies to all UK businesses through the Equality Act 2010's "reasonable adjustments" requirement. There is no minimum business size or turnover threshold. WCAG 2.2 AA (published October 2023) is the updated standard — it adds 9 new criteria covering mobile usability, cognitive accessibility, and focus visibility. Both versions apply to private sector UK businesses. New builds and major redesigns should target WCAG 2.2 AA. Existing sites should at minimum meet WCAG 2.1 AA and plan a path to 2.2.

**How do I check if my website is accessible?** Start with three free automated tools: **Google Lighthouse** (built into Chrome DevTools), the **WAVE browser extension** from WebAIM, and the **axe DevTools extension**. Run all three on your homepage, a product or service page, a form page, and any page with video. Then perform a manual keyboard test: disconnect your mouse and navigate your entire site using only Tab, Shift+Tab, Enter, and Arrow keys. If you get stuck anywhere, that is a failure. Finally, test with a screen reader — NVDA is free for Windows users, VoiceOver is built into macOS and iOS. For formal compliance certification, commission a professional WCAG 2.2 audit from an accredited assessor.

**What are the most common WCAG failures?** The 2024 WebAIM Million analysis found the six most common failures on UK and global websites are: (1) low contrast text, present on 83% of pages — body text that does not meet the 4.5:1 contrast ratio minimum; (2) missing image alt text, on 55% of pages; (3) missing form labels, on 48% of pages; (4) empty links with no descriptive text, on 44% of pages; (5) missing document language declaration, on 28% of pages; (6) missing button text, on 27% of pages. These failures account for the vast majority of real-world accessibility barriers and are all fixable without structural redesign.

**How much does an accessibility audit cost UK?** A professional WCAG 2.2 AA audit for a UK small-to-medium business website typically costs £1,500–£5,000, depending on the number of pages and templates. A full audit includes: automated scanning using axe-core across all key pages, manual keyboard testing across primary user journeys, assistive technology testing with NVDA and VoiceOver, and a prioritised remediation report with WCAG success criterion references and code examples. Audit-only costs: £1,500–£2,500 for a small site (under 20 pages); £2,500–£5,000 for a medium site (20–100 pages). Remediation costs vary based on the findings but typically add another £1,000–£8,000 for a standard SME site. Building to WCAG 2.2 AA from the start costs 5–10% more than a non-accessible build — far less than retrofitting later.

Ready to Build an Accessible Website?

Accessibility is not an optional extra in 2026 — it is a legal obligation, an SEO advantage, and the right way to build for 22% more potential customers. At Launchwork Digital, our web development services build to WCAG 2.2 AA as standard. Our UI/UX design for accessibility addresses accessibility at the design stage, before code is written. We work with UK businesses across sectors to build fast, inclusive, and legally compliant websites. Contact our team to discuss an accessibility audit or a new accessible build. **Related reading:** - Dark mode design and contrast requirements — Inclusive dark theme design with WCAG 2.2 compliance - Choosing the Right Web Design Agency — What to ask about accessibility in agency briefings - Web Development Services — Our approach and technology stack