Accessibility

Built to work
for every patient.

CannaLog is designed to meet WCAG 2.1 AA. This statement explains how we test, the known gaps we're still working on, and how to tell us when something doesn't work for you.

Last reviewed · 12 May 2026

01 Our commitment

WCAG 2.1 Level AA, no exceptions for the parts that ship.

CannaLog Technologies Limited is committed to making cannalog.co.uk, the CannaLog patient portal, and the CannaLog mobile apps usable by the widest possible audience — including patients who use screen readers, magnification, voice control, switch-access devices, or who navigate exclusively by keyboard.

We design and build against the Web Content Accessibility Guidelines (WCAG) 2.1 at Level AA, the standard cited in the UK Public Sector Bodies (Websites and Mobile Applications) (No. 2) Accessibility Regulations 2018 and adopted by the NHS Digital Service Manual.

02 · Compliance status

Partially compliant.

This website is partially compliant with WCAG 2.1 Level AA. The non-compliances listed under "Known issues" below are tracked publicly and worked through in priority order; a full external audit is planned ahead of the v1.0 mobile-app launch.

03 What we test against

The five checks every release passes.

Screen readers
NVDA on Windows (latest), VoiceOver on macOS + iOS (latest two versions).
Keyboard-only navigation
Every interactive control reachable via Tab / Shift+Tab; visible focus ring on every focused element; no keyboard traps.
Colour contrast
Automated checks (axe DevTools) plus manual sampling against the WCAG 4.5:1 (normal text) and 3:1 (large text) thresholds.
Reduced motion
Every animation respects the user's prefers-reduced-motion setting and degrades to a static fallback.
200% zoom
The page reflows without horizontal scroll, hidden content, or overlap at 200% browser zoom.
04 Known issues we're working on

Transparent about the gaps.

These items don't yet meet WCAG 2.1 AA. They're tracked internally and fixes will land in future releases.

Carousel pagination

The "More ways" carousel on the home page uses pagination dots rather than the full WAI-ARIA carousel pattern. Keyboard users can navigate via the Prev / Next buttons but cannot jump to a specific slide from the keyboard alone.

Target fix: Q3 2026
Inline styles in legacy components

Some pages still use a mix of utility classes and inline style="" attributes. This doesn't fail any WCAG criterion but makes high-contrast / user-stylesheet overrides harder.

Target fix: refactor through 2026
Third-party assets

The "Get it on Google Play" badge is supplied by Google and we cannot modify its colour contrast. We render it with an explanatory alt text.

Cannot fix · Supplier asset
05 Reporting a barrier

Tell us — we treat it like a clinical-data query.

If you cannot access part of the site, or anything is missed by your assistive technology, please tell us. We will respond within 5 working days with either a fix, a temporary workaround, or a clear timeline.

06 Enforcement

If we don't respond, escalate.

The Equality and Human Rights Commission (EHRC) is responsible for enforcing the Public Sector Bodies (Websites and Mobile Applications) Accessibility Regulations 2018. If you are not happy with how we respond to your complaint, you can contact the Equality Advisory and Support Service (EASS).

07 Technical specification

What we build on, what we support.

CannaLog.co.uk is built on Microsoft Blazor with progressive enhancement; the marketing site renders fully server-side and works with JavaScript disabled (with a degraded interactivity experience). We aim to support the most recent two major versions of Chrome, Edge, Firefox, and Safari on desktop and mobile.

Spotted something
we missed?

We're a small team and we won't get accessibility right on day one. The fastest way to fix a barrier is to tell us about it — we treat a11y reports with the same priority as clinical-data queries.

WCAG 2.1 AA target
NVDA + VoiceOver tested
Keyboard-first design
5-day response SLA