Accessibility statement

We want everyone to be able to read this site, whatever device, browser or assistive technology they use. This page says what standard we work to, what we have checked, what we have not, and how to tell us when something is in the way.

Last reviewed 9 October 2026. Applies to cairnova.io. Each product has its own accessibility documentation, provided to customers.

The standard

We aim for this website to meet the Web Content Accessibility Guidelines (WCAG) 2.2 at level AA. Cairnova is a private company, so the Public Sector Bodies (Websites and Mobile Applications) Accessibility Regulations 2018 do not apply to this site. We follow them anyway, because the organisations we build for are bound by them and should expect no less of their suppliers.

We believe the site currently conforms. That belief rests on our own testing, described below, not yet on an independent audit; we say so rather than claim a certification we do not hold.

How this site is built

Plain HTML: Every page is hand-written HTML with one stylesheet and no JavaScript. Headings are in order, landmarks are present, lists are lists and tables are tables with captions and header cells. There is nothing a screen reader has to guess at and nothing that stops working when a script fails to load.
Keyboard: Everything can be reached and operated with a keyboard alone. A skip link is the first thing on every page. Focus is always visible, with a high-contrast ring that works on light and dark surfaces. The mobile menu is a native disclosure element, so it opens and closes with Enter or Space and needs no script.
Colour and contrast: Text meets the AA contrast ratio against its background in both the light and the dark theme. Status is never conveyed by colour alone; every indicator carries a label. When Windows high-contrast mode or another forced-colours mode is on, borders are added where colour would otherwise do the work.
Your preferences: The site follows your operating system’s choice of light or dark appearance, honours a request for reduced motion by removing the one animation it has, and reflows without horizontal scrolling at any zoom up to 400 per cent and at any text size. There is no fixed-size text and no content that requires a particular orientation.
Language and reading: Pages are marked as British English. We write in plain language, lead with the point, and keep lines short enough to read comfortably. Where we use a technical term we have tried to say what it means in the same sentence.

What we have tested

Keyboard-only navigation of every page, including the mobile menu and skip link
Reading order, names and landmark structure, checked in the browser accessibility tree
Contrast of every text and interface colour in the light and dark themes
Reflow at 320 pixels wide and at 400 per cent zoom
Reduced-motion and forced-colours modes
Automated checks for markup validity and common WCAG failures

We have not yet commissioned an independent audit of this site. We intend to when we commission the audit of our first customer-facing product, and will publish the result here.

Known limitations

We are not aware of any part of this site that fails WCAG 2.2 AA. Two things are worth knowing:

The product diagrams on this site are drawn with HTML and CSS and read in order as text; there are no images of text and no information carried only in a picture.
The site links to a small number of external pages, such as the Information Commissioner’s Office. We are not responsible for the accessibility of those sites.

Tell us

If any part of this site is hard to use, or you need information from it in another format — large print, plain text, or read over the telephone — email info@cairnova.io with “Accessibility” in the subject, or call +44 (0)7301 516129. We will reply within five working days and fix what we can.

In our products. The same commitment applies to the software we build. Cairnova Casework, for example, offers light, dark and high-contrast themes, two densities and three text sizes, is fully keyboard operable, and presents every chart’s figures as text. Independent audits of each product against WCAG 2.2 AA are part of the work that remains before first deployment, and we will say on each product page when they are done.