Knosys

Back to the home page

Accessibility

Last updated 27 August 2026.

Status: partially conformant with WCAG 2.2 Level AA. We built this site to that standard and the measures below are in place today. Our full audit — automated testing across every section, plus manual screen reader passes with NVDA and VoiceOver — is scheduled and not yet complete, so we are not yet claiming full conformance. We would rather say that than say something we have not checked.

What we have done

Keyboard

Every control on this site can be reached and operated with a keyboard alone, in a logical order. A Skip to main content link is the first thing you reach, and it moves focus — not just the viewport — to the main region. Focus is always visible; we never remove focus outlines. Following a link to a section moves focus into that section, so a screen reader announces where you have arrived instead of leaving you where you were.

Motion

If your system is set to reduce motion, we honour it. Animations stop, the scroll-snapping between sections is switched off, and the animated product demonstration does not play — it shows a still frame with a Play demo button, so it is your choice rather than ours.

When the demonstration does play, it has a Pause button that is always visible, and it pauses on its own when keyboard focus enters it, when it scrolls out of view, and when the browser tab is hidden. Nothing on this site moves for more than five seconds without a way to stop it, and nothing flashes.

The product demonstration

The animated demonstration in the page header is a picture, and pictures do not read well aloud. So the whole animation is hidden from screen readers and a full text transcript of the conversation sits beside it in the page — present from the moment the page loads, readable at your own pace, and saying exactly what the animation says. Three buttons let you jump to each part of the demonstration, and pressing one announces what you have jumped to.

We deliberately do not announce the animation as it runs. A demonstration that narrated itself every few seconds, forever, would make the rest of the page unusable with a screen reader.

The demo request form

Labels sit above every field and stay visible — we never use a placeholder as a label. Errors appear as text next to the field they belong to, with an icon, never as colour alone, and they are linked to the field so a screen reader reads them together. If you submit with something missing, focus moves to the first field that needs attention rather than leaving you to hunt for it. When the form succeeds, focus moves to the confirmation heading; if it fails, the form and everything you typed stay exactly where they are.

Reading and seeing

Text and interface colours meet or exceed the AA contrast minimum, and we do not use colour on its own to carry meaning. The page reflows to a single column on small screens and when you zoom in. Headings are properly nested, regions are labelled, and every image that carries meaning has a text alternative.

If your system asks for more contrast, we honour it: the translucent panels turn solid, borders get stronger, text darkens and the focus outline thickens. If your system uses forced colours (Windows high contrast), we step out of the way and let your palette through, giving every panel a real border so nothing loses its edge.

Privacy as an accessibility feature

This site sets no cookies and stores nothing in your browser, so there is no cookie banner and no overlay to dismiss before you can read anything.

Known limitations

These are the things we know about. We would rather list them than let you find them.

Tell us when something does not work

If any part of this site stops you doing what you came to do, email [CONFIRM: accessibility feedback address]. Tell us the page, what you were trying to do, and what happened — and, if you can, what you were using to browse with. We aim to reply within five working days.

If you need something on this site in a different format, ask and we will get it to you.

Enforcement

[CONFIRM: the enforcement body and procedure for your jurisdiction, if any applies.] If you are not happy with how we respond to your report, you can escalate it there.

How this statement was prepared

Written on 27 August 2026 from a review of the site’s own code and behaviour, alongside automated testing carried out during development. It will be updated when the full audit is complete.

Privacy Terms Home