Accessibility Statement

Vilkax is built to be usable by as many people as possible, including people who rely on assistive technology. Accessibility is treated as a living standard inside the product, not a one-off box to tick. This statement explains what we aim for, what is in place today, where we know we fall short, and how to tell us about a barrier.

Our standard

We target conformance with the Web Content Accessibility Guidelines (WCAG) 2.1, Level AA. This is the benchmark referenced by European accessibility law, including the European Accessibility Act. We treat AA as the bar to hold and design new surfaces against it.

What is in place today

Vilkax maintains a shared, reusable accessibility system across its high-traffic surfaces - the marketing and account site, the consumer app, and the operator consoles. In practical terms that means, on the surfaces it covers:

• Reduced motion - we honour your operating system's "reduce motion" setting (WCAG 2.3.3); animated glows, pulses and transitions are neutralised for users who ask for it, without flattening the experience for everyone else.
• Keyboard & focus - dialogs trap and restore focus so keyboard users do not get lost behind a modal (WCAG 2.4.3), and a visible focus ring marks where you are (WCAG 2.4.7). A skip-to-content link is provided.
• Semantics & screen readers - named navigation landmarks, labelled form fields (placeholders are not used as labels), icon-only buttons carry accessible labels, and decorative graphics are hidden from assistive tech (WCAG 1.3.1 / 4.1.2).
• Contrast - text colours, including the risk / severity palette, use text-safe tokens tuned to meet AA contrast on our dark surfaces (WCAG 1.4.3).

These behaviours are covered by automated tests that run against the real source on every change, so they do not silently regress.

Known limitations

We are honest that conformance is a work in progress, not a finished state. Areas we know still need work include:

• Some dense operator and investigator tables and a number of secondary dialogs have not yet been routed through the shared accessible dialog and keyboard-operability pattern.
• Not every screen in every app has been swept for complete labelling; adoption of the shared system continues surface by surface as they are touched.
• We have not yet completed a formal, independent third-party accessibility audit.

If you hit a barrier that is not listed here, please tell us - real reports are the fastest way we find and fix gaps.

Feedback & contact

If any part of Vilkax is hard to use with assistive technology, or you need information in a different format, contact us and we will help and work to fix the underlying issue:

Accessibility & support: [email protected]
Privacy & data questions: [email protected]

You can also reach us through the in-product support widget on any page. We aim to acknowledge accessibility feedback quickly and to keep you updated on a fix.

This statement is provided for transparency and describes our current accessibility posture; it is subject to review and will be updated as coverage improves and after formal evaluation.

Last updated: 2026-06-10 · Based on the internal Vilkax accessibility system and its automated conformance tests.