E
EuFSI DPP

Accessibility Statement

Last updated: May 2026

Our commitment

European Frontier for Sustainability and Innovation BV (“EuFSI”) is committed to making the EuFSI Digital Product Passport platform usable by everyone, including users of assistive technology. This statement is published in compliance with Directive (EU) 2019/882 (the European Accessibility Act, “EAA”) Article 9(1), which requires service providers to publish accessibility information for any service in scope of the Directive.

Scope

This statement covers:

  • The marketing site at https://dpp.eufsi.com.
  • The platform dashboard at https://app.dpp.eufsi.com (all roles).
  • Public Digital Product Passport pages at https://app.dpp.eufsi.com/dpp/<slug>.
  • The QR resolver redirect service that consumers reach by scanning a product QR code.

The statement does not cover third-party services we link to (sub-processor websites, external regulatory portals); accessibility responsibility for those rests with the respective operators.

Conformance status

We design and test against WCAG 2.2 Level AA and the EN 301 549 v3.2.1 harmonised standard referenced by the EAA. The platform is currently partially conformant with WCAG 2.2 Level AA: most surfaces meet or exceed the criteria; a small set of known limitations is listed below and tracked under our internal accessibility programme.

A formal EN 301 549 conformance evaluation report (TASK-A11Y-002) is in preparation and will be linked from this page when published.

What we do

  • Use semantic HTML (proper headings, landmarks, lists, form labels) so screen readers can navigate the document structure.
  • Maintain a 4.5:1 minimum colour-contrast ratio for body text and 3:1 for large text and UI components.
  • Support keyboard-only navigation: every interactive control is reachable and operable without a pointing device.
  • Provide visible focus indicators on every focusable element.
  • Preserve form labels, error messages, and field-help text in a way that screen readers announce alongside the field.
  • Honour the user’s prefers-reduced-motion media query: animations and transitions are scaled down or disabled when the user has expressed that preference at the OS level.
  • Honour the user’s forced-colors mode (Windows High Contrast).
  • Surface dynamic content updates through ARIA live regions where appropriate.
  • Caption all video content (where present).
  • Support browser zoom up to 200% without loss of content or functionality.
  • Localise the dashboard interface in six EU languages (English, German, French, Spanish, Italian, Dutch).

Supported assistive technology

We test the platform against the following combinations. Reports of issues with other combinations are still welcome — see “Feedback” below.

  • NVDA on Firefox / Chrome / Edge (Windows).
  • JAWS on Chrome / Edge (Windows).
  • VoiceOver on Safari (macOS, iOS).
  • TalkBack on Chrome (Android).
  • Browser zoom up to 200% on the latest two major versions of Chrome, Edge, Firefox, and Safari.

Known limitations

The following limitations are known and being addressed; we list them so users with specific needs can plan around them.

  • Inline PDF viewer: the in-app PDF viewer used for compliance documents relies on the browser’s native viewer; on some assistive-technology combinations the document outline is not surfaced. Workaround: download the PDF using the “Download” button next to the viewer and open it in a dedicated PDF reader.
  • Drag-and-drop file upload: the upload zone supports drag-and-drop and a click-to-browse fallback. Drag-and-drop is announced to screen readers but is awkward to operate without a pointer. The click-to-browse button is the supported keyboard / screen-reader path.
  • Charts and dashboards: data visualisations are accompanied by an accessible data-table view. We are migrating to a single chart-plus-table layout as part of the Phase 7 launch programme; until then, look for the “Show data” toggle on the chart.
  • QR scanning on the public DPP page: consumers reach the public page by scanning a printed QR code. The on-page QR-scan camera flow is in development; the QR resolver redirect path itself is fully accessible (a screen reader announces the destination DPP page).

Feedback and contact

Per EAA Article 9(3), we provide a feedback mechanism for users to report accessibility barriers and request alternative formats.

Email accessibility@eufsi.com with:

  • Where you encountered the barrier (URL or screenshot).
  • What you were trying to do.
  • What did or did not work.
  • Your assistive-technology setup if relevant (e.g. “NVDA + Firefox 122 on Windows 11”).
  • Whether you would like a response in plain text, by phone callback, or another format.

SLA: we acknowledge feedback within 2 business days and provide a substantive response (fix, workaround, or alternative format) within 14 calendar days. If a fix requires a release we will confirm the expected release date in the response.

Security-relevant accessibility issues (e.g. a barrier that exposes other users’ data) should go to security@eufsi.com under our Responsible Disclosure policy instead.

Enforcement procedure

If you are not satisfied with our response to a barrier you have reported, you may escalate to the relevant national accessibility-enforcement body in your EU member state. The list of national bodies is published by the European Commission at ec.europa.eu/social.

How this statement is maintained

This statement is reviewed at least annually and after every material change to the platform’s accessibility posture (a new feature, a fix that closes a known limitation, a change in supported assistive-technology combinations, a new EAA or EN 301 549 revision). The review schedule is part of our internal annual review cadence.