Accessibility statement

The target is conformance with the Web Content Accessibility Guidelines 2.2 at Level AA across every page of uvam.ai.

We believe we substantially meet that standard today. We are not claiming full conformance, because that claim should follow an independent audit and ours has not happened yet. The section on what we have not done is where the gap is described.

Accessibility is a build gate here rather than a periodic report. Every pull request runs an automated axe scan and a Lighthouse accessibility audit against the built site, and a regression fails the build before it can be merged.

Automated tools catch somewhere around a third to a half of real accessibility problems. We know that, which is why the gate is a floor rather than the whole of our answer.

We also test by keyboard, at 200% zoom, and with the operating system's own contrast and reduced-motion settings switched on.

These are properties of the code rather than intentions:

• A skip link that reaches the main content, as the first thing in the tab order.
• Landmarks throughout — header, navigation, main and footer — with every navigation region individually labelled.
• A visible focus outline on everything focusable, using a colour that changes with the theme so it stays visible in both.
• Full keyboard operation, including the mobile menu, which closes on Escape and stops the page behind it scrolling.
• A high-contrast mode you can switch on from the header, which overrides both the theme and every chapter accent.
• Light and dark themes, applied before the first paint so nothing flashes on load.
• Respect for prefers-reduced-motion: the orbiting diagram freezes, and transitions across the site are reduced to nothing.
• The animated diagram is paired with a real list of focusable buttons carrying the same information, so nothing is only available inside a canvas.
• Headings in order, one h1 per page, and text that reflows to 320px without a horizontal scrollbar.
• Body text that meets AA contrast in both themes, checked against the token values rather than assumed.
• Form fields with real labels, errors tied to their field, and an error summary that takes focus when a submission is rejected.

No independent accessibility audit has been carried out. We have not published a VPAT or an accessibility conformance report, and we will not produce one from automated results.

We have not completed a full manual screen reader pass across every page with every combination we would want to cover. Our testing so far has been partial.

The orbiting platform diagram is decorative in the strict sense — it carries no information that is not also in the button list beneath it — but it has not been tested with a screen magnifier at high zoom.

Some accent colours meet AA for body text but not the stricter AAA threshold. We use them for text at normal weight and size, where AA applies, and the high-contrast mode exists as the escape hatch for anyone who needs more.

The animated diagram responds to hover as well as to focus and click. Hovering over it moves the selection, which can be distracting if you use a pointer imprecisely. Every value it can show is also available from the buttons below it, and the animation stops entirely if your system asks for reduced motion.

Long legal pages carry an on-this-page navigation that becomes sticky on wide screens. At very high zoom it stacks above the content rather than beside it, which lengthens the route to the first section.

If something on this site is difficult or impossible for you to use, email hello@uvam.ai. Describe what you were trying to do and what happened — you do not need to know the guideline number or name the barrier correctly.

We will acknowledge within two working days and tell you what we are going to do. If a fix will take time, we will say how long and offer another way to get whatever you were after in the meantime.

If you asked for something you needed and our answer did not resolve it, say so again and it will be escalated rather than closed.

Anything on this site is available by email or on a call if that suits you better. Ask at hello@uvam.ai and we will send it in whatever format works — plain text, a document, or a conversation.

There is no separate accessible version of this site, and there will not be. One site that works is the goal; a parallel stripped-down version is how the stripped-down version ends up out of date.

Prepared on 30 July 2026 based on our own evaluation of the site, which combines automated testing in the build pipeline with manual keyboard, zoom and system-preference testing.

It will be reviewed when the site changes materially, and updated when the independent audit happens. The site's revision history is public, so what changed and when is a matter of record rather than of trust.