TrustNet
Print / Save PDF
Legal · Draft

Accessibility Statement

What TrustNet is doing to make its service usable with assistive technology, what is known to be imperfect, and how to tell us.

Document: TrustNet-Accessibility-v0.1 Version: 0.1 Updated: 2026-10-21 Status: Draft — scope and audit pending Audience: all users
Print / Save PDF Give feedback

1Our commitment

TrustNet aims to meet WCAG 2.2 Level AA across the static legal pages and the authenticated dashboard. Accessibility is part of the product's usability, not a separate add-on: keyboard operation, visible focus, semantic headings and sufficient contrast are design requirements.

2Scope

This statement covers trustnet.app, the static legal and product pages, and the first-party SPA at me.trustnet.app (registration, sign-in, consent, dashboard and the RP portal). It does not cover relying parties operated by other organizations.

Whether the European Accessibility Act (and its Romanian transposition) applies to TrustNet as a consumer-facing service is still being assessed with counsel. This draft is published in the meantime; it is not a claim of full conformance and not a legal opinion.

3Conformance status

The service is partially conformant with WCAG 2.2 AA. A formal, independent audit has not yet been completed. The current state:

  • keyboard focus is visible and the main flows are operable without a pointer;
  • headings, landmarks and form labels are present on the primary screens;
  • the dark-theme active navigation pill was corrected on 2026-10-21 to meet AA contrast;
  • motion respects prefers-reduced-motion where scrolling or animation is used;
  • the legal pages are static HTML and work without JavaScript.

This list describes the current build, not a certificate. It will be revised after an audit and before any public accessibility claim.

4Known exceptions

  • Third-party relying parties are outside our control and may not be accessible.
  • Some complex data tables (audit and subprocessor tables) may need horizontal scrolling on narrow screens.
  • An independent WCAG 2.2 AA audit has not yet been completed, so further exceptions may be found.

5Feedback and enforcement

If you cannot use part of TrustNet, or find an accessibility barrier, write to privacy@trustnet.app with the page and what happened. We aim to acknowledge within five business days and to explain the next step. You can also complain to the competent Romanian authority once the applicable enforcement route is confirmed with counsel.

6Changes

This statement is reviewed when a material accessibility change ships, and at least once a year. The review date will be set when the first audit is completed.