Where we stand
This is a dark-themed, animated site, and that design has real accessibility costs. We think the right thing to do is name them rather than publish a statement claiming full conformance, which would be untrue.
This site is partially conformant with WCAG 2.2 Level AA. The known failure is listed under Known problems, and what we have fixed, with the measured numbers, is under Fixed. If a barrier is stopping you from using the site, email us and we will send you the information another way the same day.
What we are aiming for
Our target is WCAG 2.2 Level AA. We are a Canadian business, so the relevant frameworks are the Accessible Canada Act federally and provincial accessibility legislation where it applies; both point at WCAG as the practical standard, and AA is the level that matters in practice.
We also build accessible systems for clients, which makes this page a reasonable test of whether we mean it. Publishing a list of our own unfixed problems is uncomfortable and that is rather the point.
Motion and animation
Since 1 November 2026 the site has almost no motion. There is no smooth scrolling, no scroll-triggered reveal, no cursor effect and no animated hero: text is at full strength the moment it appears, and scrolling behaves exactly as your browser normally would. We removed them because they slowed reading and did nothing for anyone deciding whether to work with us.
What is left is small: buttons and links change colour on hover, the mobile menu fades in, and the brand mark in a few places settles into place once. If animation causes you discomfort, turn on Reduce Motion in your operating system — macOS and iOS under Accessibility → Motion, Windows under Settings → Accessibility → Visual effects, Android under Accessibility — and those run at effectively zero duration.
Headings and body text are present and visible in the raw HTML, so nothing you need to read depends on an animation finishing or on JavaScript running at all.
Known problems
This is current and unfixed.
1. No formal screen-reader audit
We have written correct semantic HTML, labelled every form field, and wired up the error messaging properly — but nobody has sat down and driven the whole site with NVDA, JAWS or VoiceOver end to end. Until that happens we cannot claim it reads well, only that it is built to.
Fixed since first published
This statement first went up listing five problems. Four are fixed. They are kept here, with the date, rather than quietly deleted — so you can see what changed, and so that we cannot make the list shorter without having done the work.
Fixed 25 October 2026: a “skip to content” link
Keyboard users used to tab through the whole navigation on every page before reaching the content. Now the first Tab on any page reveals a “Skip to content” link; Enter moves focus past the navigation to the start of the page, and the next Tab continues from there.
Fixed 25 October 2026: visible focus indicators
Focus used to rely on the browser's default ring, which was hard to see against the dark background and on the gradient buttons. Every link, button and form field now shows a 2-pixel teal outline when reached by keyboard (cyan until the 31 October 2026 rebrand), measured at 11.9:1 against the page background — the standard asks for 3:1. Buttons get a ring shaped to the button. Clicking with a mouse draws nothing, except in text fields, where browsers show it by design because typing is a keyboard interaction.
Fixed 25 October 2026: the cursor glow now respects Reduce Motion
It used to check only whether you had a touch screen, so a mouse user who had asked for less motion still had a light trailing their pointer — the one piece of motion on the site that ignored the setting. It now honours it, including if you switch the setting on while the page is open. On 1 November 2026 the glow was removed altogether, with the other decorative motion.
Fixed 31 October 2026: secondary text meets the contrast minimum
Captions, form hints, footer links and table headings used to be drawn in white at 35 to 45% opacity, which measured between 3.3:1 and 4.1:1 against the page background — under the 4.5:1 that AA asks for. The site was repainted on 31 October 2026 (page background #0B0F1A) and those tiers were lifted. We then rendered sixteen pages in headless Chrome and computed the contrast of every visible text colour against that background: the lowest in use is white at 50%, about 5.3:1; body text at 60% is about 7.2:1; headings are about 19:1. Button labels are navy on the teal-to-blue gradient, at least 5.2:1 on its bluest stop. The large step numbers on the process page are decorative and are hidden from assistive technology. This is a measurement against the page ground, not a certification: text set over cards and gradients can differ slightly, and we have not measured every state of every control.
What should work well
- Keyboard. A skip link on every page, a clearly visible focus ring on every control, and a cookie-preferences dialog that holds focus while it is open and returns it when it closes.
- Content without JavaScript. Every page's headings and text are in the HTML the server sends. The site is readable with scripting disabled.
- The contact form. Every field has a real
<label>tied to it, the rightautocompletevalues so a password manager or browser can fill it, errors announced through a live region, invalid fields marked witharia-invalidand their message linked byaria-describedby, and focus moved to the first field that needs attention when a submission fails. - Structure. One
<h1>per page, a sensible heading order, landmarks, and visible breadcrumbs that match the structured data. - Zoom and reflow. The layout is responsive and works at 400% zoom and at phone widths without horizontal scrolling.
- Images. Every meaningful image has alternative text; decorative graphics are hidden from assistive technology rather than announced as noise.
- Tables on the legal pages use proper row and column headers, so they can be navigated cell by cell.
How we tested, and did not
Honesty about method, since an accessibility statement is only as good as the testing behind it:
- Done: automated checks via Lighthouse and the browser accessibility inspector; manual review of the HTML the server sends; contrast ratios calculated from the actual colour tokens rather than eyeballed; the Reduce Motion paths exercised by hand.
- Not done: a full manual keyboard traversal of every page; a screen-reader pass; testing with voice control, a switch device or a braille display; and any testing with disabled people, which is the only kind that really settles the question.
Report a barrier
If something here stops you doing what you came to do, tell us — it is the fastest way for us to find out and the most useful thing you can do for the next person.
Please say what page you were on, what you were trying to do, and what assistive technology or settings you use if you are comfortable sharing that. We will reply within two business days, tell you honestly whether and when we can fix it, and in the meantime get you the information or complete the enquiry for you by email or phone — whichever you prefer.
Clovai Inc. prepared this statement on the date shown beside these sections, based on a review of our own code. We will revise it when we fix something or find something new, and we will not quietly remove an item from the list without having actually fixed it.