Skip to content
KRYOS V6

Legal

Accessibility Statement


What we build for, what has been checked, what remains unverified, and how to tell us when something blocks you.

Our commitment


This site targets the WCAG 2.2 AA standard. Accessibility is treated as part of the build rather than an afterthought, and reported barriers are treated as defects.

What the site does


The following behaviours are built into every page.

  • Every interactive element can be reached and operated with a keyboard alone, with a visible focus outline.
  • Headings follow a single logical order, and each page has one main heading.
  • Text and interface colours are chosen for contrast against the dark background.
  • Images carry descriptive alternative text, and decorative artwork is hidden from screen readers.
  • Every interactive diagram has an equivalent written explanation that conveys the same information without interaction.
  • Motion is restrained and respects the reduced-motion setting in your operating system.
  • Layouts reflow down to small phone widths without sideways scrolling.
  • Forms use real labels, describe their own errors, and never rely on colour alone.

What has been tested


Pages have been checked with automated browser runs at phone, tablet, and desktop widths, covering keyboard traversal, focus visibility, image loading, layout overflow, and interactive controls across all industry pages.

Known gaps


We have not yet completed testing on physical touch hardware or with screen readers in real use. Dense reference tables can be demanding to read at very small widths.

Presentations and reference sources hosted on other websites are outside our control, and their accessibility may differ from this site.

Report a barrier


If any part of this site stops you from getting to what you need, tell us through the contact page. Describe the page, what you were trying to do, and the device or assistive technology you were using.

We aim to acknowledge accessibility reports promptly and will offer the information in another format while a fix is being made.

Questions about this page? Contact us.