Legal information

Accessibility statement

Last reviewed: May 23, 2026

Stradiax wants stradiax.com to be usable by everyone, including people who rely on assistive technologies or have visual, auditory, motor or cognitive impairments. This document summarises the current state of the site against the international WCAG 2.2 standard, Level AA, and how to reach us if you encounter a barrier.

1. Target standard

Standard: W3C Web Content Accessibility Guidelines (WCAG) 2.2, conformance Level AA.
European framework: European Accessibility Act (Directive (EU) 2019/882), applicable since 28 June 2025, and the harmonised standard EN 301 549.
Scope: the public site stradiax.com, in its English and Spanish versions. It does not include the admin dashboard or external linked platforms (NeuralPitch, Shift Directivo), which carry their own statements.

2. Conformance status

We declare a partial conformance status. We have closed the higher-impact Level AA criteria after an internal technical review in May 2026. A full audit with real assistive technologies (NVDA, JAWS and VoiceOver screen readers) and thorough manual testing is still pending; we will keep this declaration honest until that audit is complete.

This statement is a self-assessment; it has not been issued or validated by an external certification body.

3. What we have implemented

These are the accessibility measures currently live on stradiax.com:

Skip to main content: a "Skip to main content" link that appears on first keyboard focus on every page, jumping straight past the navigation.
Semantic structure: consistent use of HTML5 landmarks (<header>, <nav>, <main>, <footer>) and a heading hierarchy without skipped levels (a single <h1> per page).
Visible focus indicator: every interactive element (links, buttons, form fields) shows a light-blue outline when it receives keyboard focus.
AA contrast verified: text meets the minimum 4.5:1 ratio against the dark background. Light-mode sections use a darker corporate blue (6:1 ratio) to preserve readability.
Respect for prefers-reduced-motion: if your operating system requests reduced motion, the background animation, smooth scrolling, marquee band and reveal effects are turned off or scaled back.
Images with text alternatives: all informative images carry an alt attribute. Purely decorative ones (3D hero canvas, animated background) are marked aria-hidden="true" so screen readers do not announce them.
Identified icon buttons: elements that only display an icon (mobile menu, social, share) carry an aria-label in the page language.
Accessible forms: the email fields on the newsletter and contact form carry an accessible label via aria-label. Native browser validation accompanies error messages.
Adequate touch targets: on small screens (mobile), footer social links and share buttons have an active area of at least 44 × 44 px.
Declared language: every page declares its primary language (<html lang="en"> or <html lang="es">) so that screen readers pronounce content with the right engine.
Tabular numerals: meaningful numeric data uses tabular figures (equal width per digit) to ease visual scanning and magnification tools.

4. Known limitations

We are actively working on the items below. If any of them blocks you, contact us and we will deliver the content through an alternative channel.

Animated 3D graphics in the hero and on product pages (projection canvases): they are purely decorative, carry no information. They are marked aria-hidden but have no textual alternative description.
ROI calculators (services and product modals): 100% keyboard navigation across all sliders and fields has not been formally audited. If you need them and hit a barrier, write to us.
Chat assistant: the bottom-right chatbot has not yet been tested with screen readers. If you want to ask the same question by email, use the contact below.
Long blog articles: they do not include an accessible reading progress bar. The internal structure (TOC, headings, blockquotes) remains navigable.
Full audit pending with automated tooling (axe-core, Lighthouse) and real assistive technologies. Planned for the second half of 2026.

5. Report an accessibility barrier

If you find a page, piece of content or interaction you cannot use for accessibility reasons, write to info[arroba]stradiax[punto]eu — escríbelo manualmente and tell us:

The exact URL of the page where you found the issue.
Your browser, operating system and, if you use one, the assistive technology (screen reader, magnifier, voice control, etc.).
A short description of the barrier and, if you have one, a suggested fix.

A real person from the team replies, never an automated template. Maximum response time: 5 working days. If the content is critical for you, say so and we will prioritise.

6. Escalation path if you are not satisfied

If, after our reply, you still cannot access the content or you consider the proposed remedy unreasonable, you can address the competent disability-rights body in your jurisdiction. In Spain, that authority is the Directorate-General for the Rights of Persons with Disabilities of the Ministry of Social Rights, and ultimately the Spanish Ombudsman.

7. Continuous improvement

Accessibility is not a one-off compliance step, it is an ongoing practice. Every new feature or page on stradiax.com is designed with keyboard, screen reader, magnifier and voice-control users in mind. When we discover a barrier, we prioritise it and ship the fix as soon as the schedule allows.