Website Accessibility UK: WCAG Compliance Guide for 2026
Over 14 million people in the UK have a disability. An inaccessible website excludes them — and exposes your organisation to legal risk under the Equality Act. This guide explains what compliance requires and how to achieve it in 2026.
What are UK websites legally required to do for accessibility in 2026?
UK websites are legally required to be accessible under the Equality Act 2010, which prohibits discrimination against disabled people and requires 'reasonable adjustments' to remove barriers to service. For public sector bodies — government, NHS, universities, local councils — the Public Sector Bodies Accessibility Regulations 2018 impose a specific legal duty to meet WCAG 2.1 Level AA, publish an accessibility statement, and conduct regular reviews. Non-compliance can trigger enforcement action by the Cabinet Office and the Central Digital and Data Office (CDDO). Private sector organisations face a lower-specificity obligation under the Equality Act, but inaccessibility that prevents disabled users accessing services can constitute unlawful discrimination.
The legal landscape hardened in 2025–2026 as enforcement activity increased and case precedent expanded. The EHRC (Equality and Human Rights Commission) published updated technical guidance confirming that website inaccessibility is a form of indirect discrimination under the Equality Act for organisations providing services to the public. Several UK disability organisations have pursued or threatened legal action against private sector websites, particularly in financial services, retail and travel. UK businesses that process the personal data of disabled users under UK GDPR also face the argument that inadequate accessibility undermines the data minimisation and purpose limitation principles.
WCAG 2.2 (Web Content Accessibility Guidelines) became the de facto standard for UK web accessibility in 2023–2024, adding nine new success criteria to the previous WCAG 2.1 standard. The most impactful new criteria for UK website owners include: Focus Not Obscured (2.4.11/2.4.12 — keyboard-navigated elements must remain visible when focused), Dragging Movements (2.5.7 — functionality that requires dragging must have a single-pointer alternative), Target Size Minimum (2.5.8 — interactive elements must be at least 24x24 pixels), and Accessible Authentication (3.3.7/3.3.8 — login processes must not require cognitive tests that disadvantage users with cognitive disabilities).
The four principles of WCAG — Perceivable, Operable, Understandable and Robust (POUR) — provide the organising framework for accessibility compliance. Perceivable means information must be presentable to users in ways they can perceive (images have alt text, videos have captions). Operable means all functionality must be accessible via keyboard, not just mouse. Understandable means content must be readable and interfaces predictable. Robust means content must be interpretable by current and future assistive technologies including screen readers. Compliance requires addressing all four principles across three conformance levels (A, AA, AAA), with AA being the legal target for UK organisations.
How do you carry out a website accessibility audit for a UK site?
A website accessibility audit combines automated testing and manual expert review — neither alone provides complete coverage. Automated tools (Axe, WAVE, Google Lighthouse, Deque's axe DevTools) can identify approximately 30–40% of WCAG failures: missing alt text, insufficient colour contrast, missing form labels, and structural heading hierarchy issues. These tools are valuable as a baseline but are insufficient as a compliance assessment because the majority of accessibility issues — keyboard trap scenarios, screen reader compatibility, cognitive load problems, and accessible authentication failures — require human testing to identify.
Manual testing for UK website accessibility should include keyboard-only navigation testing across all pages and interactive elements, screen reader testing with NVDA (Windows, free) and VoiceOver (macOS/iOS, built-in), and testing with a representative sample of assistive technologies. Critical manual test areas: can a keyboard user access all functionality (including menus, modals, carousels, date pickers and forms) without a mouse? Does the screen reader announce dynamic content changes (AJAX updates, live chat notifications, form error messages) appropriately? Do all images have accurate, meaningful alt text, or are they described generically?
User testing with disabled participants is the highest-quality accessibility input available, and is strongly recommended by the EHRC for organisations with significant accessibility obligations. A structured usability test with six to eight disabled participants — including users of screen readers, voice control software (Dragon NaturallySpeaking), switch access devices, and users with cognitive and learning disabilities — will identify real-world barriers that no automated or expert manual test can fully anticipate. UK accessibility consultancies typically charge £3,000–£8,000 for a comprehensive audit including user testing; CDDO-registered auditors are required for public sector bodies.
Accessibility audit reporting should categorise findings by WCAG success criterion, severity (critical, major, minor), and estimated remediation effort. A well-structured audit report provides: a prioritised remediation roadmap (fix critical issues blocking users entirely first, then major barriers, then minor improvements), code-level recommendations for each issue where possible, and clear guidance for content editors on ongoing accessibility obligations (image alt text, video captions, document accessibility). The audit report becomes the specification document for remediation work — without this level of detail, development teams cannot implement fixes consistently.
Make your UK website accessible and legally compliant
iGrowix provides website accessibility audits and WCAG 2.2 remediation for UK organisations — offshore delivery keeps costs 40–60% below London agency rates while meeting the highest compliance standards.
Get a free accessibility consultation →What are the most common WCAG failures on UK websites?
The most common WCAG failure on UK websites is missing or inadequate image alternative text. WebAIM's 2025 Million analysis found that 55% of all homepage images on the web had missing or empty alt text — meaning screen reader users receive no information about these images. For decorative images, an empty alt attribute (alt='') is correct; for informative images, the alt text must describe the image's meaning or function accurately, not just its visual appearance. A button displaying only an icon with no text and no alt attribute is completely invisible to a screen reader user — one of the most severe functional accessibility failures possible.
Insufficient colour contrast between text and background is the second most prevalent WCAG failure on UK websites. WCAG 2.2 requires a minimum contrast ratio of 4.5:1 for normal text and 3:1 for large text (18pt+ or 14pt+ bold). Many UK website designs fail this criterion for body text on mid-tone backgrounds, placeholder text in form fields, and text overlaid on photographs. Chrome DevTools, the WAVE browser extension, and the WebAIM Contrast Checker (free, online) allow developers and designers to check contrast ratios instantly. Fixing colour contrast failures is typically low-effort but requires design authority to approve colour changes.
Missing form labels are the third most common failure class and are particularly damaging for accessibility because they prevent screen reader users from understanding what information is required in a form. Every form field — text inputs, dropdowns, checkboxes, radio buttons — must have an associated HTML label element or ARIA label attribute. Placeholder text is not a substitute for a label: when a user starts typing, the placeholder disappears, leaving users with cognitive disabilities unable to remember what the field was for. Forms that use label elements consistently also benefit from improved usability for all users, not just those using assistive technology.
Keyboard accessibility failures — interactive elements that are unreachable or unusable via keyboard navigation alone — affect a large proportion of UK websites and represent significant functional barriers for users with motor disabilities, users of switch access devices, and power users who prefer keyboard navigation. Common keyboard accessibility failures include: custom dropdown menus that don't respond to keyboard events, modal dialogs that trap keyboard focus or don't return focus to the trigger element when closed, carousels that don't expose control buttons to keyboard navigation, and date pickers built as canvas or SVG elements without proper ARIA roles and keyboard interaction patterns.
How much does it cost to make a UK website accessible?
Website accessibility remediation costs in the UK depend on the severity of current issues, the size and complexity of the site, and the technology stack. For a small business website (10–30 pages, standard CMS like WordPress or Squarespace) with moderate accessibility issues, remediation typically costs £1,500–£4,000 for a comprehensive fix. For a mid-size ecommerce or corporate site (100–500 pages) with multiple interactive components, remediation costs £4,000–£15,000. For large enterprise sites or bespoke web applications with complex interactive features and multiple user types, remediation projects can reach £20,000–£80,000.
iGrowix provides WCAG accessibility audits and remediation for UK organisations at offshore delivery costs 40–60% below equivalent London digital agency rates. A WCAG 2.2 Level AA audit for a 50-page UK business website, including automated scanning, manual expert testing and prioritised remediation roadmap, is typically delivered for £1,200–£2,500 — versus £2,500–£5,000 from a London-based specialist. Remediation implementation is quoted separately based on audit findings, with UK-hours communication and delivery transparency throughout.
The cost of not investing in accessibility must be weighed against remediation cost. The UK has approximately 14.6 million disabled people (22% of the population), and the 'purple pound' — the annual spending power of disabled people and their households — is estimated at £274 billion by Purple Trading. An inaccessible website excludes this market segment entirely. Beyond the commercial loss, the legal risk is non-trivial: while definitive UK court awards in website accessibility cases are rare, the EHRC's enforcement powers include unlimited fines in egregious cases, and reputational damage from public accessibility complaints can far exceed the remediation cost.
Ongoing accessibility maintenance is required after initial remediation because websites change continuously. New content, new features, CMS updates and third-party widget integrations can all introduce new accessibility failures. Best practice is to integrate automated accessibility testing into the development pipeline (running axe-core or Lighthouse CI on every deployment), train content editors on accessible writing and image alt text requirements, include accessibility acceptance criteria in website development tickets, and conduct a full expert re-audit annually. Building accessibility into the development process is significantly less costly than periodic remediation sprints.
How do you write an accessibility statement for a UK website?
UK public sector bodies are legally required to publish an accessibility statement under the Public Sector Bodies Accessibility Regulations 2018. The statement must: confirm which accessibility standard the site aims to conform to, list known accessibility issues and when they will be fixed, provide a mechanism for users to report accessibility issues, and state a contact address for accessibility concerns. The government's model accessibility statement template is available on GOV.UK and must be followed in substance if not exactly in wording. Statements must be updated whenever the site's accessibility status changes.
Private sector UK organisations are not legally mandated to publish an accessibility statement under current legislation, but doing so demonstrates good faith, reduces legal risk, and signals commitment to accessibility to users. A private sector accessibility statement should cover: the organisation's commitment to accessibility, the standard being aimed for (WCAG 2.2 Level AA recommended), the date of the last accessibility review, known issues and remediation timeline, and contact details for accessibility feedback. Publishing a statement and then failing to act on reported issues creates a paper trail of inaction that is more damaging legally than having no statement at all.
The accessibility feedback mechanism specified in the accessibility statement must be genuinely responsive. Users who report accessibility barriers should receive an acknowledgement within 5 working days and a substantive response within 20 working days — aligning with the public sector's statutory timeframe. Establishing an accessibility issue queue within your development process, with clear ownership and escalation paths, is the organisational infrastructure that makes a published accessibility statement credible rather than purely performative. Some UK organisations appoint a named Accessibility Officer responsible for managing this queue.
Accessibility statements should be linked from the footer of every page of the website — a common convention that ensures users can find it regardless of which page they land on. The link text should be 'Accessibility statement' or 'Accessibility' — not buried under 'Legal' or 'Policies' where users expecting to find it won't look. Some UK organisations combine accessibility statement content with a broader 'inclusive design' page that explains their approach to accessibility, their testing methodology and their improvement roadmap — a more expansive and user-friendly format than the minimum regulatory requirement.
How does accessibility relate to SEO for UK websites?
Website accessibility and SEO share substantial common ground because both require clear, well-structured, machine-readable content. Image alt text, which screen readers require for accessibility, also provides the text description that Google uses to understand image content for image search. Logical heading hierarchy (H1, H2, H3) required for screen reader navigation also provides the content structure that Google uses to understand page organisation and extract featured snippet content. Descriptive link text ('read our guide to WCAG compliance') required for accessibility also provides context-rich anchor text that contributes to internal and external link signals.
Core Web Vitals, which Google uses as a ranking signal, measure the user experience dimensions of page loading speed (LCP), visual stability (CLS) and interactivity (INP). These same performance dimensions affect users with disabilities who rely on assistive technologies that parse the DOM: slow page loads are disproportionately impactful for screen reader users who are waiting for content to be announced; layout shifts cause confusion for users with cognitive disabilities; poor interactivity responsiveness affects users with motor disabilities who interact more slowly. Improving Core Web Vitals simultaneously improves SEO performance and the experience of disabled users.
Structured data markup, essential for SEO rich results, also contributes to accessibility by making page content interpretable to AI systems and assistive technologies beyond standard screen readers. In 2026, AI Overview citations, voice search responses and smart home device answers all draw on structured data to understand and present web content. A website with comprehensive schema.org markup — Organisation, Product, FAQ, Article, BreadcrumbList — is simultaneously optimised for Google's rich results, for AI Overview citation, and for the semantic interpretation capabilities of modern assistive technology platforms.
The business case for treating accessibility and SEO as a unified programme rather than separate initiatives is compelling. Both require technical quality (fast, standards-compliant HTML), content quality (clear, well-structured, meaningful text), and ongoing maintenance. An SEO programme that also addresses accessibility delivers: improved Google rankings, improved user experience for all visitors, reduced legal risk, and expanded addressable market including 14+ million UK disabled users. Commissioning a combined accessibility and SEO audit — as iGrowix offers — is more efficient and cost-effective than commissioning two separate workstreams with overlapping recommendations.
Audit and improve your UK website's accessibility
Get a WCAG 2.2 accessibility audit and remediation roadmap for your UK website — with expert testing, prioritised recommendations and optional implementation support at offshore rates.
Request your accessibility audit →What tools and resources should UK web teams use for accessibility?
The essential free tools for UK web accessibility testing include: Google Lighthouse (built into Chrome DevTools, runs automated accessibility checks and reports WCAG failures with code references), the WAVE Web Accessibility Evaluation Tool (browser extension and online tool from WebAIM, provides visual overlay of accessibility issues), axe DevTools (browser extension from Deque, more comprehensive than Lighthouse for automated testing), and the Colour Contrast Analyser (desktop app from TPGi, allows eyedropper colour sampling for contrast testing outside of browser environments). These four tools together cover the majority of automatable WCAG failures at zero cost.
Screen readers for testing UK websites include NVDA (NonVisual Desktop Access, free for Windows), JAWS (industry-standard commercial screen reader, annual licence ~£1,000), VoiceOver (built into all Apple devices, free), and TalkBack (built into Android, free). UK government and large enterprise accessibility testing typically uses NVDA and JAWS on Windows and VoiceOver on macOS and iOS. For a representative test, run through your site's key user journeys with NVDA on Firefox as a minimum — this combination is widely used by UK screen reader users and surfaces most real-world screen reader compatibility issues.
WCAG documentation and resources: the official WCAG 2.2 specification (wcag.nl/en/guidelines/wcag22) provides the authoritative criteria text; the WCAG 2.2 Quick Reference (w3.org) provides filterable, practical guidance; the Government Digital Service (GDS) accessibility guidance (gov.uk/guidance/accessibility-requirements-for-public-sector-websites) provides the authoritative UK public sector implementation guide. The CDDO's accessibility monitoring methodology, published annually, details the specific testing approach used for government enforcement — which private sector organisations would do well to apply to their own sites.
Training resources for UK web and content teams: the Deque University accessibility curriculum provides structured online training for developers, designers and content creators at approximately £300–£500 per year per user. The Accessibility Association (IAAP) offers the Certified Professional in Accessibility Core Competencies (CPACC) qualification, widely recognised in UK public sector organisations. The Shaw Trust's '5-day Accessibility Challenge' is a free introductory resource for teams beginning their accessibility journey. Building internal accessibility capability through training is more sustainable than perpetual reliance on external audit, and creates the cultural change needed to prevent accessibility regressions between periodic review cycles.