Accessibility

Our accessibility commitment

Last updated: 26 July 2026

This reflects a genuine, code-level self-review — not a certified third-party audit. We checked real contrast ratios, keyboard navigation, and semantic structure against WCAG on this site, and fixed what we found. It hasn't yet been through a formal accessibility audit or real assistive-technology testing (e.g. with an actual screen reader user), so treat this as an honest current status, not a compliance certificate.

The standard we target

We aim to meet WCAG 2.1 Level AA — the Web Content Accessibility Guidelines published by the W3C, and the benchmark referenced by both major accessibility regulations relevant to us:

The European Accessibility Act (EAA) — which points to EN 301 549, itself aligned with WCAG 2.1 AA, for the digital services it covers.
The Americans with Disabilities Act (ADA) — which doesn't specify a technical standard directly, but WCAG 2.1 AA is the de facto benchmark referenced in U.S. Department of Justice guidance and accessibility litigation.

We're a UK-based platform; the EAA applies most directly if we're serving customers within the EU, and ADA relevance depends on serving US-based organisations. We're treating WCAG 2.1 AA as our baseline regardless of exactly which regulation technically applies to a given customer, rather than trying to draw that line precisely.

What we've actually checked and fixed

As part of preparing this page, we reviewed our marketing site's real colour contrast, keyboard behaviour, and page structure, and made concrete fixes rather than just writing a policy:

Colour contrast — we measured every text/background colour combination in use. Two failed WCAG AA's 4.5:1 minimum for normal text (our secondary "muted" text colour, and white text on one button colour) — both have been darkened to pass with margin.
Keyboard focus — every interactive element (links, buttons, cards) now shows a clear, consistent visible outline when navigated to by keyboard, not just by mouse.
Semantic structure — pages use a single, correctly-nested heading hierarchy, and every image has appropriate alternative text.
Keyboard-operable components — our FAQ page's expandable questions are built with native HTML disclosure elements, so they work correctly with a keyboard alone, with no custom scripting required to make them accessible.

What we haven't done yet

In the interest of being genuinely useful rather than reassuring: we haven't run this through a screen reader with a real user, haven't had a professional accessibility audit, and haven't yet extended this level of review to the certificate issuance and verification application itself (as opposed to this marketing site). These are reasonable next steps we intend to take, not gaps we're pretending don't exist.

Certificate verification specifically

Every certificate we issue includes a public verification page, viewable without an account. We consider this page's accessibility particularly important, since it's often the one page a person outside your organisation actually needs to use.

Report an issue

If you hit an accessibility barrier anywhere on we-verifi or Cert Verifi — something you couldn't do with a keyboard, a screen reader that didn't announce something correctly, or text you couldn't read — please tell us. Contact hello@we-verifi.co.uk with what happened and, if you can, what page you were on. We treat these reports as genuine bugs, not just feedback.