Accessibility Statement

Robovue is committed to being usable by everyone, including people using assistive technology. This page states our real, current conformance status against the Web Content Accessibility Guidelines (WCAG) 2.1, Level AA — the standard referenced by EN 301 549 and required under the EU Accessibility Act (enforceable since 28 June 2025). We'd rather tell you exactly what's been checked and what hasn't than imply a broader guarantee than what's actually been verified.

Conformance status

Fully conformant with WCAG 2.1 Level A and AA as of the audit dated below, across every page of the Robovue application (app.robovue.co.uk) and this marketing site (robovue.co.uk) that could be exercised in a real, logged-in session — no open violations were found.

Two pages exist only in a transient, one-time authentication step — the page shown immediately after a brand-new signup, before a workspace exists, and the page shown when accepting a teammate invitation — and share their layout and components with the sign-in page, which was itself verified clean. They weren't independently re-run in this audit pass because reaching their exact live state requires a session our test environment doesn't hold open; this is disclosed here rather than silently assumed clean.

That status covers web pages. The emails Robovue sends are assessed separately, with their own limits — see Transactional email below.

How this was measured

Automated scanning with axe-core, checked against the WCAG 2.1 A and AA rule sets, run against every real page in both light and dark themes, plus a narrow mobile viewport on every page containing a data table or card grid. This was paired with manual keyboard checks on interactive controls — tab order, visible focus, and the reorder controls used to rearrange dashboard widgets without a mouse. Automated tooling catches a meaningful share of accessibility issues but not all of them (it can't judge focus order or keyboard operability on its own), which is why the manual pass is part of the same audit, not a substitute for it.

Transactional email

The emails Robovue sends — alerts, team invitations and billing notices — are HTML too, and held to the same WCAG 2.1 AA standard. As of the check dated below, every one of them passed the same axe-core rule sets in both light and dark colour schemes, including versions with maximum-length and right-to-left names, and every one reflows to a single column at a 320px width. Each email also carries a plain-text version with the same content, for text-only mail clients and assistive technology that reads mail without HTML.

That check renders each email in a browser, and a browser is not a mail client. Some mail clients invert an email's colours on their own, and Outlook on Windows uses a different rendering engine altogether, so how each email looks in every inbox has not been verified yet. We're not claiming it.

One email can't fully conform. The verification and password-reset code email is sent by our sign-in provider, Amazon Cognito, as a single HTML part inside an envelope we don't control: we can't set its language attribute, and it has no plain-text alternative.

Email last checked: 2026-09-14.

Report a barrier

If you use assistive technology and run into something that doesn't work, tell us — contact@robovue.co.uk. Include the page, what you were trying to do, and the assistive technology you're using if you can; we'll investigate and fix genuine barriers.

Last audited: 2026-08-19.