Accessibility

• An automated axe-core scan of the public website, most recently in August 2026, covering the homepage, pricing, comparison and trust pages.
• Targeted manual keyboard checks of the surfaces that scan flagged: the site navigation, the in-page section rail and the demo request form.
• The public website is presented on a single dark theme by design, so it is reviewed in that presentation only. The signed-in platform supports both a light and a dark theme.

• The in-page section rail kept its buttons in the tab order while hidden from screen readers, so keyboard users could reach controls they could not hear announced.
• Several small controls, including the mobile menu button and the links that move between page sections, were below the minimum target size and have been enlarged.
• The navigation regions in the site header and footer had no accessible names, so a screen reader listed several identical "navigation" landmarks with nothing to distinguish them.
• A heading level was skipped on the homepage, which breaks the document outline screen reader users navigate by.
• Required fields in the demo request form were marked only with a visual asterisk, so a screen reader user was not told a field was required until after submitting.

We would rather name these than leave them implied:

• No full manual WCAG 2.2 AA audit has been carried out. Automated tooling detects a minority of the success criteria, so passing it is a floor and not a result.
• We have not yet run structured testing with people who use screen readers, magnification or voice control day to day.
• The signed-in platform has not been independently audited for accessibility. The testing described above covers the public website.
• The cookie consent banner is provided by a third party, so its markup and keyboard behaviour are not fully under our control. We are reviewing it.