Accessibility statement
We want everyone to be able to use aivaco.ai, including people who use screen readers, keyboards, magnification or other assistive technology. This statement says how accessible the site is and what to do if you hit a problem.
Our standard
We aim to meet the Web Content Accessibility Guidelines (WCAG) 2.2 at level AA. The site is plain HTML, CSS and a small amount of JavaScript, and every page is readable without the scripts.
What we have done
- Text and interface colours are checked against the WCAG contrast ratios on both light and dark sections.
- Every link, button and form control can be reached and used with a keyboard, and shows a visible outline when it has focus.
- Form fields have labels, and error messages are announced.
- Pages use headings in order, and images that carry meaning have descriptions. Decorative images are hidden from screen readers.
- Layouts adapt to phones, tablets and large screens, and text can be enlarged without losing content.
- Animation is switched off for people who have asked their device to reduce motion.
Known limitations
- The A1 to D4 risk tier grid on the platform page responds to hover and touch. The same information is given in the table beside it.
- The whitepaper is a long web document designed to be printed. Its page numbering and layout are for print, and some of its diagrams are described in the surrounding text rather than in full alternative text.
- The interactive demonstrator at demo.aivaco.ai is a separate application. We have tested it for keyboard use and contrast, but it has not had a full independent audit.
Tell us about a problem
If you cannot use something on this site, or you need information in a different format, email hello@aivaco.ai and tell us what page you were on and what happened. We aim to reply within five working days and to fix confirmed problems promptly.
If you are not satisfied
If our reply does not resolve the problem, you can contact the Equality Advisory and Support Service (EASS) at equalityadvisoryservice.com.
This statement was prepared on 28 October 2026 from our own testing and was last reviewed on that date.
