Accessibility Statement

We build compliance software for organisations operating under EU law, including the European Accessibility Act and the Web Accessibility Directive. We hold ourselves to the same standard we ask our customers to meet: this statement describes what we did, how we checked it, and what we haven't finished yet.

Conformance target

eurocompliant.com is designed to conform to WCAG 2.1 Level AA, the standard referenced by EN 301 549 (the harmonised European standard for digital accessibility) and by the Web Accessibility Directive.

Conformance status: partially conformant. This means most of the site and application meet the standard, but we know of specific areas that don't yet, listed below. We have not commissioned an independent third-party audit — this statement reflects our own testing, described below, not an external certification.

What we did

Concrete measures currently in place across the marketing site and the application:

• Colour contrast checked against the WCAG relative-luminance formula (not eyeballed) — text and interactive elements target at least 4.5:1 against their background, both in light mode and in our dedicated dark theme.
• Every drag-and-drop interaction has a genuine keyboard equivalent: reordering plan tasks, arranging dashboard widgets, and customising sidebar navigation can all be done with a keyboard alone, with the result announced to screen readers.
• Form fields are programmatically associated with their labels, dialogs trap and return focus correctly, and status messages (saves, errors, uploads) are announced via aria-live regions rather than shown only as silent visual changes.
• Skip-to-content links, semantic landmarks, and visible focus indicators throughout.
• Charts carry a text description of what they show, for users who can't see the rendered image.
• Documents exported as PDF — policies, GDPR records of processing, AI Act risk assessment reports, certificates — carry a real tagged structure (headings, tables, and reading order a screen reader can navigate, computed from the same markup used to render the page, not a flat image of text), with the document's language and title set correctly.

Known limitations

Areas we know still need work, in rough priority order:

• The one DOCX export we generate (a security-questionnaire answer library) hasn't been reviewed for accessible heading and table structure yet.
• Some third-party embedded content (payment forms, SSO provider screens) is outside our direct control.
• Long-tail admin and configuration screens receive less testing than customer-facing workflows and may have gaps we haven't found yet.

Reporting a barrier

If you hit something that doesn't work with a keyboard, a screen reader, or otherwise falls short of what this statement promises, tell us — we treat these as bugs, not feedback for a future roadmap. Email accessibility@eurocompliant.com with the page, what you were trying to do, and the assistive technology you were using if applicable. We aim to acknowledge reports within two business days.

For anything else, see our Contact page, or our Trust & Security page for our wider compliance posture.