Accessibility

How accessible this site is

We build to the Web Content Accessibility Guidelines (WCAG) 2.2 at Level AA as a target.We do not claim to conform to it. This site has been assessed by its own team against the guidelines; it has not been independently audited, and it has not been tested with screen readers or other assistive technology. Known shortfalls are listed below rather than left for you to discover.

What has been built in

• A "Skip to content" link as the first thing a keyboard user reaches, so the navigation can be bypassed.
• Proper page structure — real header, navigation, main and footer regions, one first-level heading per page, and headings that descend in order without skipping levels.
• Every form field has a visible, permanently associated label. Related options are grouped in a fieldset with a legend, so their shared question is announced with them. Labels are not replaced by placeholder text.
• The current page is marked programmatically in the navigation, not by colour alone.
• A visible focus outline — three pixels of Bull Blue, offset from the element — so keyboard users can always see where they are. See the known issues below for where this is currently missing.
• Text contrast comfortably above the AA threshold in the main content: body text measures 7.6:1 against white, orange buttons 6.6:1, and white text on the deep blue panels 12.2:1, against a requirement of 4.5:1.
• Layouts built with relative units that reflow rather than break — the site works down to a 375-pixel-wide screen with no horizontal scrolling, and tolerates zooming and enlarged text.
• Almost no JavaScript. The content is server-rendered and readable without scripts, and there are no carousels, auto-playing media or content that moves on its own.
• Decorative graphics are hidden from screen readers; meaningful images carry text alternatives.

Known issues

These are real and we can reproduce them. They come from our own assessment, and they are the reason we do not claim conformance.

• Small orange section labels are too low-contrast. The short uppercase labels above section headings measure roughly 3.2:1 against white, below the 4.5:1 required for text at that size. The same words always appear in the heading beneath them, so no information is lost, but the labels themselves are hard to read for some people.
• Contact form fields lose the focus outline. When you tab into a field, the outline is suppressed and only the border colour changes. That is a weaker focus indicator than the rest of the site provides.
• Reduced-motion preferences are not yet honoured. The site has only small transitions on buttons and the header, but it does not currently detect or respond to a "reduce motion" system setting.
• Section images are placeholders. The large framed areas are labelled placeholders standing in for photography that does not exist yet. Their final text alternatives will be written when the real images are added.
• The contact form does not submit. Its buttons are deliberately inert while the site is in pilot, so it cannot currently be used to reach us. Use the e-mail address below instead.
• No assistive-technology testing has been done. There has been no screen reader pass, no full keyboard walkthrough and no independent audit. There may be problems we have not found.

Tell us if something does not work

If you hit a barrier on this site — including anything not listed above — please tell us atromina.popescu@datasentics.com. Describing the page and what you were trying to do helps us reproduce it. We read every report, and we would rather hear about a problem than have you work around it.

Status of this statement

This site is a pilot, published on a temporary address and still under construction. This statement reflects a self-assessment carried out on 26 July 2026 and will be reviewed — and the known issues above addressed — before the site moves to its permanent home.