We want anyone to be able to use Alethexis. This page explains what we check, how and with what result, and what the check does not cover yet.
We check the public website and the product screens with axe, an open-source automated tool, against the Web Content Accessibility Guidelines (WCAG) 2.0 and 2.1 success criteria at levels A and AA that an automated tool can test: colour contrast, the accessible name of buttons, links and form fields, the text alternative of images or the page language, among others.
The measurement is part of the automated tests that run on every change, before it reaches production, and it allows no violations: a change that introduces one is not merged.
On the public website, the main pages: the home page in Spanish and in English, pricing, the blog, the AI Act guide, the Route, the assessment and the page for DPOs, as well as this one.
In the product: onboarding, the dashboard, the inventory, classification, the use policy, Evidence and most sections of M2, M3 and the Agentic add-on, including the assessment wizards for a high-risk system.
In the latest measurement, on 2 November 2026, none of the pages and screens measured showed violations of those criteria. Getting there meant fixing, among other things, insufficient colour contrast, buttons without an accessible name and badly built lists.
An automated tool finding no violations does not mean there are no barriers: it means there are none of the kind that tool can detect.
Write to us at hello@alethexis.com and tell us the page or screen, what you were trying to do and, if you can, the browser and assistive technology you use. We will look into it and reply.
Page last reviewed: 2 November 2026. We update it when the scope of the measurement or its result changes.