UK Web Marketing builds to WCAG 2.2 AAA — the strictest of the three Web Content Accessibility Guidelines conformance levels. This statement covers ukwebmarketing.com (the company website you're reading) and the default build target for every client site we deliver. Public Sector Bodies Accessibility Regulations 2018 apply broadly to schools, councils, and any organisation receiving substantial public funding; AAA exceeds the AA minimum those regulations require.

1. Our commitment

Every site we build — including ukwebmarketing.com itself — is designed and tested against WCAG 2.2 AAA from the first commit, not bolted on after launch. AAA covers a wider audience than AA: people with motor impairments need larger tap targets (SC 2.5.5 Enhanced), people with cognitive impairments benefit from clearer language (SC 3.1.5), people with low vision need 7:1 contrast (SC 1.4.6), and so on. For clients in regulated sectors — independent schools (KCSIE / Public Sector Bodies regs), clinics (CQC accessibility expectations), solicitors (SRA Principle 1) — AAA is the defensible baseline.

2. What we do, technically

Hand-coded semantic HTML — landmark elements (<main>, <nav>, <article>, <aside>), one <h1> per page, properly-nested heading hierarchy.
Skip links — multiple bypass-blocks links in the header, jumping to main content, navigation, and footer (SC 2.4.1 AAA Enhanced).
Target size — every interactive control is at least 44×44 CSS pixels (SC 2.5.5 Enhanced).
Contrast ratios — body text is 7:1 against background (SC 1.4.6 AAA); UI text on coloured buttons (e.g. --accent-dark #4339c0 at ~7.95:1) tested per element.
Keyboard-only navigation — every page navigable without a mouse; visible focus indicator (3px solid outline, brand colour) on every focusable element.
Screen reader semantics — ARIA labels on icon-only buttons (e.g. the WhatsApp sticky button), aria-current="page" on breadcrumbs, aria-label on landmark <nav> regions, aria-live on form status regions.
Form labels — every input has an explicit <label for=> association; error messages are programmatically connected.
Images — meaningful images have descriptive alt attributes; decorative images use alt="" or role="presentation".
Motion preferences — animations and transitions respect prefers-reduced-motion; no auto-playing video.
Language — <html lang="en-GB"> set on every page so screen readers select the right voice.
No JavaScript dependency — every site we build renders, reads, and converts without JavaScript (the lead-magnet form is the only progressive-enhancement exception, and falls back to an email mailto).

3. Tools we test with

Every build goes through a manual + automated accessibility pass before launch and on every significant change:

Lighthouse / axe-core — automated rule coverage for contrast, landmarks, ARIA correctness.
Keyboard-only walkthrough — Tab through every interactive element on every page.
Screen reader spot-check — VoiceOver (macOS / iOS) for the main flows; clients can request a NVDA pass.
Real device testing — iOS Safari (iPhone), Chrome Android, plus desktop Firefox / Safari / Chrome.
Browser zoom — every page tested at 200% zoom without loss of content or function (SC 1.4.4).

4. Known limitations

We're honest about the gaps. As of the last-updated date above:

Some embedded third-party content (Google Maps embeds, YouTube where used, Stripe Checkout pages) follows the provider's own accessibility posture, which we don't control. We pick providers with reasonable AAA scores but cannot guarantee them.
Older client sites built before WCAG 2.2 ratification (October 2023) may meet 2.1 AAA but not yet every 2.2 success criterion. We bring those up as part of any major content refresh.
Long-form blog content from external authors may use less plain English than ideal (SC 3.1.5 AAA reading-level); we edit for clarity but don't strip nuance from technical posts.

5. Feedback & reporting an issue

If you find a barrier on this site, or on a site we built for a client and you want to escalate it, email hello@ukwebmarketing.com. Include the page URL, what assistive technology you're using, and what specifically didn't work. We aim to acknowledge within 1 working day and fix within 5.

6. Enforcement

If you're not satisfied with our response, in England, Wales and Scotland you can contact the Equality Advisory and Support Service (equalityadvisoryservice.com). For public-sector clients, complaints can be escalated to the Equality and Human Rights Commission.

7. Statement preparation

This statement was prepared on the date above by Jordan Gilbert (founder, UK Web Marketing). It was based on a self-assessment against WCAG 2.2 AAA, carried out with the tools listed in section 3. It is reviewed at least annually and on any significant site change.

8. Related documents

9. Changelog

v1.0 — June 2026 — initial publication on the EU-sovereign rebuild.

← Back to legal index

Accessibility Statement