Accessibility Statement

Published 19 September 2026 · Prepared by self-assessment · Next review March 2027

Vedomia Limited is committed to making vedomia.com usable by everyone, including people who use screen readers, keyboard navigation, magnification, or who find reading, concentration or working memory difficult.

Why we publish this

Vedomia is a private company, so Directive (EU) 2016/2102 does not apply to us directly. It applies to many of our customers — public bodies, and organisations delivering publicly funded work — and they are accountable for the accessibility of the tools they choose. This statement exists so that a procurement officer, a funder or a disabled colleague can check our position without having to ask, and so that they can attach it to their own documentation.

It follows the model in Commission Implementing Decision (EU) 2018/1523.

What was tested, and how

Assessed by self-evaluation on 19 September 2026 against the rendered pages, not against the source code alone. The following were measured rather than asserted:

Success criterion	Method	Result
1.1.1 Non-text Content	Every <img> across all 86 pages checked for a text alternative	Pass — 0 images without one
1.4.3 Contrast (Minimum)	Computed foreground and background colour of every rendered text node, including translucent text blended onto its background	Pass — 0 failures on measurable text
1.4.4 Resize Text	Text enlarged to 200%; checked for horizontal scrolling and clipped content	Pass — no scrolling, no clipping
1.4.10 Reflow	Viewport reduced to 320 px	Pass — no horizontal scrolling
2.1.1 Keyboard	Tab traversal of interactive elements	Pass on pages tested
2.4.7 Focus Visible	Keyboard focus observed live: 3 px outline, 3 px offset, in a colour that contrasts with both light and dark surfaces	Pass
2.3.3 Animation from Interactions	prefers-reduced-motion honoured in the stylesheets	Pass
3.1.1 Language of Page	lang attribute on every page	Pass — 0 pages without one
3.1.2 Language of Parts	Links leading to content in the other language carry hreflang; enforced by an automated test	Pass
2.4.1 Bypass Blocks	Skip link present on content pages	Pass

What is not yet fully assessed

We would rather name these than let a reader assume they were covered.

• Screen reader testing with real users. The site is built with semantic HTML and ARIA labelling, and has been checked structurally, but it has not yet been tested end to end with NVDA, JAWS or VoiceOver by people who use them daily. This is the most significant gap.
• The process-map builder. It is a large interactive application with drag-and-drop, modal dialogs and a live canvas. Keyboard operation and focus management have been implemented deliberately, but the builder has not been audited screen by screen to the depth of the content pages.
• Generated Word documents. The files the Workspace produces use heading styles, table headers and document language, which is what assistive technology reads. They have not been validated against the accessible-document checkers used for published PDFs.
• Text on gradient backgrounds. 41 text elements sit on gradients, where contrast cannot be computed automatically. They were designed against the same targets but have not been verified point by point.
• Third-party pages. Payment is completed on Stripe’s own checkout, which we do not control.

Feedback — and what happens next

If any part of this site is difficult for you to use, tell us. Write to contact@vedomia.com or phone 083 847 5268. Please say which page you were on and what happened.

We reply within five working days. If we can fix it, we say when. If we cannot fix it quickly, we find you another way to get the same result — including sending you the same information in a different format, or working through it with you directly.

Enforcement

Because Vedomia is a private company, the national enforcement procedure under Directive (EU) 2016/2102 does not apply to this site. If you are unsatisfied with our response you can contact us again and ask for it to be reviewed by the founder, who is named on this site and answers directly. For a service delivered to you by a public body using Vedomia, that body remains responsible under its own national procedure.

How this site is built

Accessibility here is treated as part of the work, not a layer added at the end: short sentences and one idea per step, a predictable order, keyboard operation, status never signalled by colour alone, no time limits while you are thinking, and a plain-language view of every process for the person going through it. Some of it is enforced automatically — the build refuses to publish a page that drops a reader into another language without saying so.

This is a statement of how we build and what we measured. It is not a certificate, and we do not claim the site is free of accessibility defects.