Accessibility

Accessibility statement

Last reviewed: 28 October 2026

This statement covers this website, xperios.ai, including its blog. It does not cover the Xperios software itself, the Ensemble desktop application, or the portals our customers run on Xperios. Paritor’s own website has its own statement.

Using this website

We want as many people as possible to be able to use this website. You should be able to:

  • zoom in up to 400% without the text spilling off the screen or the page scrolling sideways
  • change the text spacing without losing content
  • get around the whole site with a keyboard alone, and always see where you are
  • use the site in light or dark mode, with every colour combination meeting the contrast standard in both
  • use the site with animation switched off, if your device is set to reduce motion
  • use every page with JavaScript switched off

Pages have a clear heading structure, a link to skip to the main content, and text alternatives for every meaningful image. Nothing plays, moves or times out on its own.

How accessible this website is

We aim to meet the Web Content Accessibility Guidelines (WCAG) version 2.2 at level AA. We believe xperios.ai meets that standard, with the exceptions below.

What we know is not perfect yet

  • Some older blog posts, written before this website moved to xperios.ai, skip a heading level inside the article (for example, from the title straight to a smaller heading). The content is all there, but the outline a screen reader shows is less tidy than it should be.
  • Some older posts show screenshots of Xperios or Ensemble. Each has a short text description, but the description does not repeat every field on the screen. Ask us if you need the detail.
  • The Ensemble user guide is a long PDF. It is tagged for screen readers and has its language set, but it has no document title, so some screen readers announce the file name instead. The Xperios guide is a website, not a PDF.
  • A few blog posts link to videos and documents on other organisations’ websites, which we don’t control.
  • We have tested the site with automated tools, a keyboard and the browser checks described below, but not yet with a screen reader such as NVDA, JAWS or VoiceOver.

How we tested this website

On 28 October 2026 we tested every page and every blog post on this website, in both light and dark mode:

  • with axe-core, an automated checker, against WCAG 2.2 levels A and AA
  • at a width of 320 pixels, which is what a 1280-pixel screen shows at 400% zoom
  • with letter, word, line and paragraph spacing increased to the levels WCAG sets
  • with a keyboard alone, checking that every link and button shows where the focus is

We fixed every problem those tests found, including adding text descriptions to 46 images in older posts that had none. Automated tools find only some accessibility problems, which is why we would like to hear about anything you come across.

Tell us about a problem

If something on this website doesn’t work for you, or you need information in a different format such as large print or plain text, email info@paritor.co.uk. Tell us the page and what went wrong. A person from the team will reply.

About this statement

This statement was prepared on 28 October 2026, after the testing described above. We review it at least once a year, and whenever we make a significant change to the website.