Accessible by design, compliant by default.
WCAG 2.2 AA audits and remediation, treated as a discipline rather than a pre-launch checklist — across every CMS platform we support.
More than a compliance checkbox
Accessibility reduces legal risk — but the sites that treat it as a discipline see the benefits well beyond compliance.
Legal & compliance risk
The Equality Act 2010 creates a duty to make reasonable adjustments online. WCAG 2.2 AA is the standard regulators and courts point to when judging whether you’ve met it.
Public-sector ready
Public Sector Bodies Accessibility Regulations require a published accessibility statement and WCAG 2.2 AA conformance — and it’s increasingly a procurement gate for private-sector contracts too.
Reach every customer
One in five UK adults has a disability. An inaccessible site doesn’t just risk complaints — it quietly excludes a fifth of your potential market before they ever convert.
Better SEO, for free
Semantic markup, meaningful alt text and logical heading structure are exactly what search engines want to parse. Accessibility work and SEO work overlap more than most teams realise.
Fewer support tickets
Clear structure, full keyboard support and sensible forms reduce confusion and failed transactions for every user — not just those using assistive technology.
Built in, not bolted on
Retrofitting accessibility after launch is always more expensive than designing and building it in from day one. We treat it as a discipline, not a pre-launch checklist item.
What WCAG 2.2 AA actually requires
Every success criterion in WCAG rolls up into four principles — POUR. We audit and build against all four.
Perceivable
Information and interface components must be presentable to users in ways they can perceive — alt text for images, captions for video, sufficient colour contrast, and text that can be resized without breaking layout.
Operable
Interfaces and navigation must be operable by everyone — full keyboard access, enough time to read and use content, no seizure-inducing flashes, and interactive targets that are large enough to hit reliably.
Understandable
Content and interface behaviour must be understandable — readable language, navigation that behaves predictably, and clear input assistance that helps users avoid and correct errors.
Robust
Content must be robust enough to be reliably interpreted by a wide range of user agents, including current and future assistive technology — which in practice means valid, semantic markup.
New in WCAG 2.2
— four of the nine new criteria that catch most CMS sites out.Focus Not Obscured
Sticky headers, cookie banners and chat widgets can no longer hide the element that currently has keyboard focus.
Target Size (Minimum)
Interactive targets — buttons, links, form controls — must be at least 24×24 CSS pixels, or have equivalent spacing.
Dragging Movements
Anything that relies on a drag gesture (sliders, reordering, drag-and-drop) needs a single-pointer alternative.
Accessible Authentication
Login can’t rely purely on a cognitive test — like remembering a password — without an accessible alternative such as a password manager or biometrics.
Scoped around your estate, not a price sheet
Three conversations before we quote anything — a Accessibility estate for a 5,000+ employee organisation looks nothing like a single-site brochure.
Discovery
Audit current architecture, traffic profile and compliance requirements.
Scope
Design the SLA, team structure and infrastructure plan around what we find.
Proposal
A fixed proposal, priced against your estate — not a published rate card.
Prefer to talk first? Call 020 3608 2525
Frequently asked questions
Get your free accessibility health check
A no-obligation WCAG 2.2 AA snapshot of your site, with the quick wins flagged in plain English.