Built to WCAG 2.1 AAA.

flexiweb.digital passes the WCAG 2.1 enhanced (AAA) contrast threshold at 100/100 — tested with the axe accessibility engine on 17 May 2026, zero errors, zero warnings, zero notices.

Below: the standard, what was specifically tested, how anyone can verify it in about thirty seconds, and why I think this matters.

IAAP Member — committed to accessible and inclusive web practices.

The standard

Two thresholds. I aim for both.

The web has two accessibility tiers worth caring about. AA is the legal floor in the UK under the Public Sector Bodies Accessibility Regulations and, for many commercial sites, the Equality Act 2010 — it covers the basics: readable contrast, keyboard navigation, semantic markup, sensible alt text, sane heading order. AAA is the enhanced threshold — 7:1 contrast for normal text (versus 4.5:1 at AA), stricter heading order, unique accessible names on links serving different purposes, fuller keyboard parity, and a number of smaller refinements that add up.

For client work I aim for AA at minimum, because that’s the legal bar your business needs to clear and the moral bar your visitors deserve. Where the design and content reasonably allow, I push to AAA — which is what flexiweb.digital itself is built to. Not as a brag; as a worked example.

What was tested

A list, not a slogan.

“The site passes AAA” is often a fuzzy claim. Here’s what was specifically tested on the latest pass — every page, not a sample:

Colour contrast at ≥7:1 for normal text and ≥4.5:1 for large text. Every visible text element, including small captions, mono labels, and button text.
Heading order with no level skipped between h1, h2, h3, h4.
Unique accessible names on links serving different purposes — e.g. four “Read the case” CTAs on the homepage each carry an aria-label naming the specific case.
Semantic landmarks (nav, main, footer) so screen readers can skip between regions.
Keyboard navigability — every interactive element reachable and operable without a mouse. Mobile menu opens via the toggle, closes on ESC, returns focus correctly.
Visible focus indicators on every interactive element.
Alt text — descriptive on content images (case study screenshots, the line-drawing portrait), empty (alt="") on decorative ones.
Reduced-motion respect — the scroll-reveal animations honour prefers-reduced-motion and skip the transition entirely for visitors who’ve opted out.

Last full retest: 17 May 2026. The site is retested on every meaningful design or template change — typically every two to four weeks during active development.

How to verify

Don’t take my word for it.

A 100/100 claim is only useful if you can check it yourself. Three ways, no specialist tools needed:

Chrome / Edge Lighthouse — open DevTools (Cmd+Option+I on Mac, F12 on Windows), click the Lighthouse tab, tick “Accessibility”, click Analyze. Should return 100/100 on every page.
axe DevTools browser extension — the engine the WCAG audit was originally run with. Install, open any page, click “Scan all of my page”. Should return zero errors, zero warnings.
WebAIM Contrast Checker — for individual colour pairs. Inspect any text element on the site, grab the foreground and background colours from DevTools, paste them in. Get the precise contrast ratio.

If you find anything that fails, email [email protected] — I’ll fix it inside a working day.

Why it matters

The law is the floor, not the ceiling.

Around one in five UK adults has a disability that affects how they use the web — visual, motor, cognitive, or auditory. Sites that don’t account for that quietly exclude a meaningful chunk of their audience by accident.

For regulated sectors — care, education, finance, public-facing services — accessibility is also a legal requirement, and the regulator can act when sites fall short. Most agencies treat it as a checkbox at the end of a project. I treat it as part of the build, every page, every commit. It’s cheaper to bake in than to retrofit, and it’s the right thing to do regardless.

If you’re building a site where accessibility actually matters — or you’re worried your existing site is quietly excluding people — that’s a conversation worth having. Get in touch, or book a 30-minute discovery call from the contact page.