Accessibility statement

The target

In short: Level AA of the WCAG guidelines, the level required by existing digital accessibility regulations.

The Web Content Accessibility Guidelines define three levels: A, AA and AAA. Level AA is the one adopted by the standards that apply to digital services, including the European standard EN 301 549. That is this site’s target.

In practice it covers four requirements: content must be perceivable, operable without a mouse, understandable, and robust in the hands of assistive technology. The sections below say which of these are checked, and how.

What is checked on every change

In short: Part of the requirements is held by automated tests: they cannot regress without failing the build.

Text contrast is computed, not estimated. The brand gold is legible on a dark background and is not on white: a distinct colour replaces it in the light theme, and a test rejects any text colour that would fall below the ratio level AA requires.

Content is rendered by the server. Every page’s text exists in the document that is sent, before any script runs: a browser with scripting disabled, like assistive technology that applies styles without executing them, receives the whole page. A dedicated rule neutralises the animations’ starting states in that case.

The system reduced-motion setting is honoured: every decorative animation stops and the page decor freezes. Card tilting is also disabled on coarse pointers, where it has no target.

The contact form’s fields carry a linked label, their error state is announced, and the anti-robot field is removed from the tab order and from the accessibility tree. A skip link, visible as soon as it takes focus, jumps past the navigation.

Illustrations are decorative and declared as such: they carry no text, so nothing is lost for anyone who does not see them.

Keyboard navigation

In short: Anything that works with a mouse works with a keyboard, and focus stays visible.

Menus, the language switch, the theme switch and the expandable questions are fully operable from the keyboard. The frequently asked questions rely on the native element built for the purpose rather than on a rebuild in script, which gives them the expected behaviour for free.

The same choice applies to the contact form’s optional fields, folded behind a native element: it opens from the keyboard, announces its state, and stays usable if scripts do not run. Focus remains visible throughout, including on the skip link at the top of the page.

Known limitations

In short: No outside audit, no testing with people who use assistive technology, and language proofreading still incomplete.

This site has not been audited by a third party. The checks described above are automated or made by hand by the team that writes it, which is not a substitute for an independent examination.

No testing has been carried out with people who use a screen reader, voice navigation or an adapted pointing device daily. Automated tests can validate a structure and still miss a painful journey.

The Spanish version has not yet been proofread by a native speaker. Awkward wording is a comprehension obstacle, which belongs to accessibility as much as contrast does.

Some decorative effects remain outside the reduced-motion setting, notably card hover. They carry no information and block no action, but they exist.