Accessibility Statement

1. About This Statement

vaicat B.V. is committed to making CUEBES usable by everyone, including people with disabilities. This statement describes the current accessibility status of the platform, what we know is missing, how to give us feedback, and what to do if you are not satisfied with our response.

This statement is published in the spirit of the European Accessibility Act (Directive (EU) 2019/882) and the Web Content Accessibility Guidelines (WCAG) 2.1 Level AA. Whether the EAA technically compels us to publish depends on our enterprise size and service classification; we publish anyway because honest expectations are the right default.

2. Scope

This statement covers:

• cuebes.eu — the CUEBES web platform (Codicles, CUES, Cubes, Wave, Talent Bank, research, messaging, EU rights flows)
• Integrated apps: EUnify, mEUvy, EUorigin, CathAI

Third-party content embedded in CUEBES (e.g. YouTube or Vimeo embeds, external Codicles linked-out content) is not within our control; their accessibility is governed by their respective providers.

3. Conformance Status

CUEBES has not been formally audited against WCAG 2.1 Level AA. We do not have evidence to claim Partial or Substantial conformance, and we are not willing to claim it without that evidence. We therefore treat the status as Not Conformant until a structured audit is performed.

This is the honest position. The platform has been built with some accessibility primitives in mind (semantic HTML in many places, keyboard-navigable forms, alt text on most uploaded media), but we have not verified compliance against the WCAG 2.1 AA criteria, and we know there are surfaces where accessibility is likely incomplete.

4. Areas Likely Needing Work

Based on the kinds of surfaces CUEBES contains and what is typical of unaudited platforms, the following areas are likely to have accessibility gaps. We have not verified this list against a formal audit; it is provided so users know where to expect rough edges and so the audit, when it happens, has a starting point.

• Rich-content editors — code editors (Codicles), the compose box, and any wysiwyg surfaces typically need targeted screen-reader and keyboard work
• Custom UI components — modals, dropdowns, autocomplete, custom date pickers, drag-and-drop interactions are common gap areas
• Dynamic and infinite-scroll surfaces — feeds, search results, real-time updates can present challenges for assistive technology
• Colour contrast — the glass-morphism design system has not been formally contrast-audited; some surfaces may fall below WCAG AA contrast thresholds
• Focus management — single-page-application route changes, modal open/close, and async loading states need to be verified for focus handling
• Media — uploaded videos may lack captions or audio descriptions; we do not generate these automatically
• Forms and error messages — error association, required-field announcements, and validation feedback need to be verified end-to-end
• Maps, charts, and data visualisations — used across mEUvy, EUnify, Talent Bank, and analytics; visual content needs accessible text or table alternatives
• Mobile / responsive surfaces — touch-target sizes, gesture alternatives, and mobile screen-reader behaviour all need review

5. Our Commitment

We are committed to working toward Partial Conformance with WCAG 2.1 Level AA over time. We will update this statement as accessibility work progresses, and we will not claim a higher conformance level than we can substantiate.

We do not commit to a specific deadline because we have not yet scoped the remediation work. We do commit to: documenting accessibility gaps as we find them, treating accessibility regressions as bugs (not feature requests), and surfacing accessibility on our public roadmap once a baseline assessment is complete.

6. Alternative Ways to Get Help

If you encounter content or a feature on CUEBES that is not accessible to you, contact us — we will do our best to provide the information or perform the action through an alternative channel. Email support@vaicat.com with subject "Accessibility Help" and a description of what you were trying to do.

7. Feedback

We rely on user feedback to identify accessibility barriers. If you encounter one:

• Email: support@vaicat.com with subject "Accessibility Issue"
• Tell us: the URL or screen, the assistive technology you use (if any), the browser / OS, and a description of the barrier
• We aim to acknowledge accessibility feedback within 5 business days. Resolution time depends on the complexity of the underlying work; we will keep you informed.

For formal complaints, email privacy@vaicat.com.

8. Enforcement Procedure

If you are not satisfied with our response to your accessibility feedback, you may lodge a complaint with the relevant Dutch authority responsible for accessibility-related compliance. As of the date of this statement, the relevant body for accessibility complaints in the Netherlands is the College voor de Rechten van de Mens (Netherlands Institute for Human Rights) — www.mensenrechten.nl. The specific competent body for European Accessibility Act (Directive 2019/882) market-surveillance is being designated by Member States; we will update this statement when the Dutch market-surveillance authority for EAA is named.

You may also reach the European Consumer Centre (Netherlands) at www.eccnederland.nl for cross-border consumer issues.

9. Preparation of This Statement

• Method: self-declaration by vaicat B.V. No external audit has been performed.
• Date of preparation: May 7, 2026
• Date of last review: May 7, 2026
• Next review: within 12 months, or sooner if accessibility work changes the conformance status

Operator

• vaicat B.V.
• Noordeinde 99B, 2514 GD The Hague, Netherlands
• KvK (Dutch Trade Register): 89360672
• Email: support@vaicat.com