Legal and trust

Accessibility

Xovris is for everyone, so xovris.ai is built for everyone to use – with a keyboard, a screen reader, magnification, voice control or a switch, on a phone or a computer.

In force since 5 November 2026 - the same text for every visitor.

How you should be able to use this website

  • Change colours, contrast and fonts with your browser or device settings: every colour comes from one source whose contrast steps are tested.
  • Zoom in up to 400% without text spilling off the screen: every page is measured at 320 pixels wide with no sideways scrolling.
  • Reach every control from the keyboard, with a visible focus ring: every control is a native or React Aria control.
  • Turn motion down or off, and hear nothing unless you turn sounds on.

A person’s review with screen readers (JAWS, NVDA and VoiceOver) and speech recognition has not been done yet; the report below marks each criterion it still owes, and this page says when it is done.

Our accessibility standard

We build every page to WCAG 2.2 level AA. That meets the web content requirements of EN 301 549, the European standard the European Accessibility Act points to.

Where we stand

This statement is our own assessment: no independent audit has been done yet. We check pages with automated accessibility tools and from the keyboard while we build them, and fix what we find. When an independent audit is done, its date and its result are published here.

What you can change on this site

  • Motion: full, calm or off, at the foot of every page. Until you choose, the site follows your device’s reduce-motion setting.
  • Colours: match your device, light, dark, or high contrast in light or dark.
  • Sounds stay off unless you turn them on, and never play while motion is off.
  • Glyph, the helper, can be put away with one press, moved with the arrow keys, and never rests over what you are reading.
  • Search the whole site from the keyboard with Ctrl K, or Cmd K on a Mac.

Conformance report

Every WCAG 2.2 level A and AA success criterion, in the order of the industry’s Accessibility Conformance Report (VPAT 2.5), with where xovris.ai stands and how we know. It is our own assessment until an independent audit replaces it: 24 checked, 21 partly checked, 2 not yet checked and 8 that do not apply to this site. A criterion moves only when the way it is checked does.

xovris.ai against WCAG 2.2 level A and AA, self-assessed
Success criterionLevelWhere it standsHow we knowMeasured on this build
1.1.1 Non-text ContentAPartly checkedaxe (WCAG 2.2 AA rules) after an 8-second wait on each kind of page finds no image, icon or control without a text alternative; a person’s review with a screen reader and keyboard is still owed of whether each alternative says the right thing.Reading this build’s measurement…
1.2.1 Audio-only and Video-only (Prerecorded)ADoes not applyThe site has no audio or video recordings. Its animations show the product working and carry no information that is not also in words.Reading this build’s measurement…
1.2.2 Captions (Prerecorded)ADoes not applyNo prerecorded video with sound.Reading this build’s measurement…
1.2.3 Audio Description or Media Alternative (Prerecorded)ADoes not applyNo prerecorded video.Reading this build’s measurement…
1.2.4 Captions (Live)AADoes not applyNo live audio or video.Reading this build’s measurement…
1.2.5 Audio Description (Prerecorded)AADoes not applyNo prerecorded video.Reading this build’s measurement…
1.3.1 Info and RelationshipsAPartly checkedHeadings, lists, tables with captions and header cells, and labelled regions are built in the shared components; axe (WCAG 2.2 AA rules) after an 8-second wait on each kind of page finds no structure fault; a person’s review with a screen reader and keyboard is still owed.Reading this build’s measurement…
1.3.2 Meaningful SequenceAPartly checkedPages are written in reading order with logical start and end, never reordered visually; a person’s review with a screen reader and keyboard is still owed.Reading this build’s measurement…
1.3.3 Sensory CharacteristicsAPartly checkedInstructions name controls by their words, never by shape, colour or position alone; a person’s review with a screen reader and keyboard is still owed of every page.Reading this build’s measurement…
1.3.4 OrientationAACheckedNo page locks the screen’s orientation; every page is laid out for 320 to 1920 pixels wide in both orientations.Reading this build’s measurement…
1.3.5 Identify Input PurposeAAPartly checkedFields that ask about the person (email address) carry their autocomplete purpose; a person’s review with a screen reader and keyboard is still owed of every form.Reading this build’s measurement…
1.4.1 Use of ColorAPartly checkedEvery state (pass, advice, fault, could not read) is said in words and shown by a mark as well as a colour; a person’s review with a screen reader and keyboard is still owed.Reading this build’s measurement…
1.4.2 Audio ControlACheckedNothing plays sound by itself: the helper’s sounds are off until the person turns them on, and never play while motion is off.Reading this build’s measurement…
1.4.3 Contrast (Minimum)AACheckedText colours come from the one token source every colour comes from, its contrast steps tested (at least 4.5:1 for text), and axe (WCAG 2.2 AA rules) after an 8-second wait on each kind of page measures the drawn page in dark, light and high contrast.Reading this build’s measurement…
1.4.4 Resize TextAAPartly checkedType is set in rem and pages reflow at 200% zoom in the layout sweep; a person’s review with a screen reader and keyboard is still owed at 200% text-only zoom.Reading this build’s measurement…
1.4.5 Images of TextAACheckedThe site draws no text as a picture: the mark, the helper and every figure are live text or vector shapes.Reading this build’s measurement…
1.4.10 ReflowAACheckedEvery page works at 320 pixels wide with no sideways scrolling.Reading this build’s measurement…
1.4.11 Non-text ContrastAAPartly checkedControl borders and focus rings come from the one token source every colour comes from, its contrast steps tested at 3:1 or more; a person’s review with a screen reader and keyboard is still owed for charts and the helper.Reading this build’s measurement…
1.4.12 Text SpacingAANot yet checkedStill to be confirmed with text-spacing overrides applied.Reading this build’s measurement…
1.4.13 Content on Hover or FocusAAPartly checkedTooltips and the helper’s tips can be dismissed with Escape and stay while the pointer is over them (React Aria); a person’s review with a screen reader and keyboard is still owed.Reading this build’s measurement…
2.1.1 KeyboardAPartly checkedEvery control is a native or React Aria control, and the helper and the helper’s figure are pressed from the keyboard before each release; a person’s review with a screen reader and keyboard is still owed of every page.Reading this build’s measurement…
2.1.2 No Keyboard TrapAPartly checkedDialogs close with Escape and return focus to what opened them (React Aria; the release gate checks the helper); a person’s review with a screen reader and keyboard is still owed.Reading this build’s measurement…
2.1.4 Character Key ShortcutsACheckedEvery shortcut uses a modifier key (Ctrl or Cmd K, Alt X); the 404 game’s arrow keys work only while the game has focus.Reading this build’s measurement…
2.2.1 Timing AdjustableACheckedNothing on the site has a time limit: a check, a form or the helper waits as long as the person needs.Reading this build’s measurement…
2.2.2 Pause, Stop, HideACheckedMotion is full, calm or off from the foot of every page and follows the device’s reduce-motion setting until chosen; the helper can be put away with one press; every replay has pause.Reading this build’s measurement…
2.3.1 Three Flashes or Below ThresholdACheckedNo animation on the site flashes: motion is movement and fades.Reading this build’s measurement…
2.4.1 Bypass BlocksACheckedEvery page in the site frame starts with a skip link to its one main landmark.Reading this build’s measurement…
2.4.2 Page TitledACheckedEvery page has its own title, checked by axe (WCAG 2.2 AA rules) after an 8-second wait on each kind of page and by the build’s search checks.Reading this build’s measurement…
2.4.3 Focus OrderAPartly checkedFocus follows the reading order of the source; a person’s review with a screen reader and keyboard is still owed.Reading this build’s measurement…
2.4.4 Link Purpose (In Context)APartly checkedLinks name where they go in their own words; axe (WCAG 2.2 AA rules) after an 8-second wait on each kind of page finds no empty link; a person’s review with a screen reader and keyboard is still owed.Reading this build’s measurement…
2.4.5 Multiple WaysAACheckedEvery page is reachable from the header, the footer’s site map, search (Ctrl or Cmd K) and the helper.Reading this build’s measurement…
2.4.6 Headings and LabelsAAPartly checkedEach page has one h1 and labelled sections (the release gate checks one main and one h1); a person’s review with a screen reader and keyboard is still owed.Reading this build’s measurement…
2.4.7 Focus VisibleAACheckedEvery control shows a visible focus ring when reached from the keyboard (React Aria focus-visible).Reading this build’s measurement…
2.4.11 Focus Not Obscured (Minimum)AANot yet checkedStill to be confirmed with the sticky header and the helper on screen.Reading this build’s measurement…
2.5.1 Pointer GesturesACheckedNothing needs a multi-point or path gesture; every action is one press.Reading this build’s measurement…
2.5.2 Pointer CancellationACheckedControls act on release (native buttons and React Aria press events), so moving off before letting go cancels.Reading this build’s measurement…
2.5.3 Label in NameAPartly checkedIcon buttons’ names start with their visible words where they have any; a person’s review with a screen reader and keyboard is still owed.Reading this build’s measurement…
2.5.4 Motion ActuationACheckedNothing responds to shaking or tilting the device.Reading this build’s measurement…
2.5.7 Dragging MovementsAACheckedDragging is never needed: the helper’s figure can be moved with the arrow keys and opened with one press; a link dropped on it can be pasted instead.Reading this build’s measurement…
2.5.8 Target Size (Minimum)AACheckedEvery control is at least 24 by 24 pixels or spaced so, on phone and desktop.Reading this build’s measurement…
3.1.1 Language of PageACheckedEvery page declares en-GB, checked by axe (WCAG 2.2 AA rules) after an 8-second wait on each kind of page.Reading this build’s measurement…
3.1.2 Language of PartsAADoes not applyThe site is in one language; names in other languages are proper names.Reading this build’s measurement…
3.2.1 On FocusACheckedReaching a control leaves the page as it is; only pressing it acts.Reading this build’s measurement…
3.2.2 On InputAPartly checkedTyping or choosing never leaves the page without a press (the currency switch re-prices in place); a person’s review with a screen reader and keyboard is still owed.Reading this build’s measurement…
3.2.3 Consistent NavigationAACheckedOne header and one footer, from one layout, on every page of the site frame.Reading this build’s measurement…
3.2.4 Consistent IdentificationAACheckedOne component and one name for each action everywhere (one copy catalogue, one control per kind).Reading this build’s measurement…
3.2.6 Consistent HelpACheckedThe helper and the contact link are in the same place on every page.Reading this build’s measurement…
3.3.1 Error IdentificationAPartly checkedA check that cannot read an address says which field and why in words; a person’s review with a screen reader and keyboard is still owed of every form.Reading this build’s measurement…
3.3.2 Labels or InstructionsAPartly checkedEvery field has a label (axe (WCAG 2.2 AA rules) after an 8-second wait on each kind of page); a person’s review with a screen reader and keyboard is still owed of the instructions’ wording.Reading this build’s measurement…
3.3.3 Error SuggestionAAPartly checkedErrors say what to do next; a person’s review with a screen reader and keyboard is still owed.Reading this build’s measurement…
3.3.4 Error Prevention (Legal, Financial, Data)AADoes not applyThe website takes no payment and makes no legal commitment; the sign-up form can be changed or withdrawn by email.Reading this build’s measurement…
3.3.7 Redundant EntryACheckedNothing asks twice: an address checked on one page carries into the next step.Reading this build’s measurement…
3.3.8 Accessible Authentication (Minimum)AADoes not applyThe website has no sign-in; signing in happens in the Xovris app, whose own report covers it.Reading this build’s measurement…
4.1.2 Name, Role, ValueAPartly checkedControls are native or React Aria, so their state reaches assistive technology; axe (WCAG 2.2 AA rules) after an 8-second wait on each kind of page finds no fault; a person’s review with a screen reader and keyboard is still owed.Reading this build’s measurement…
4.1.3 Status MessagesAAPartly checkedCheck results, the helper’s answers and its notes are announced through status regions; a person’s review with a screen reader and keyboard is still owed.Reading this build’s measurement…

No automatic rule tests this; the method beside it is how it is known.

Known failures and their repair

Reading this build’s measurement…

    The European Accessibility Act

    The European Accessibility Act (Directive (EU) 2019/882) has applied since 28 June 2025 to many services sold to consumers in the European Union, including services bought online. Xovris’s plans for people and families are services of that kind, so we treat them as covered and build them to the standard above.

    This statement covers the website. The statement for the Xovris product itself – the command centre and the apps – is published here before accounts open.

    Tell us what gets in your way

    If anything on xovris.ai is hard to use with the way you browse, write to support@xovris.ai. Say which page and what happened, and we reply with a fix or another way to get what you need.

    If you are not satisfied with our reply, in the European Union you can contact the authority that oversees accessibility in your country; in the United Kingdom, the Equality Advisory and Support Service can help.

    Questions

    support@xovris.ai · Accessibility in the trust centre · Acceptable use

    No recorded example is needed here: this page is the document itself, and the check at its head ran in your browser as you opened it.

    Ask Xovris

    Open the full page