TouringXX
ES EN
Request an assessment

Intelligence and automation

Enterprise AIFeatured AI HubPlatform · featured Chatbots and conversational agentsWeb · messaging · voice Automation and integrations Internal apps and systems AI avatars and digital twins

Web and product

Web design and development E-commerce development Performance and optimisation Maintenance and support

Visibility and marketing

SEO, GEO and AI visibility Marketing, content and social media

Brand and production

Design, print and production Branding and visual identity Problem solving & technical fixes

Not sure which service you need?

Tell us your goal and we will propose the next step.

Request an assessment
Legal document

Accessibility statement

Last updated: · Version 1.0 · Replaces —

En una frase

We build to WCAG 2.2 level AA as our reference standard, and we publish the known exceptions alongside the commitment.

01Where we stand

The site is being built with WCAG 2.2 level AA as its reference standard. The definitive conformance statement will be published after production QA; until then this document records the commitment, what is already resolved and the outstanding points.

We publish the known exceptions alongside the commitment: a statement with no exceptions has rarely been verified.

02What is already resolved

These decisions are taken in the design system, not page by page, so they apply to everything we publish.

Contrast. All text meets at least 4.5:1; large headings and interface elements, 3:1. The brand colours were chosen with this constraint already in place.
Keyboard. The whole site can be traversed and used with the tab key, including the services menu and the forms. Focus is always visible, with a two-pixel outline.
Zoom and text. Content works at 200% zoom and with enlarged text, with no clipping or overlap. Nothing is smaller than 12 px.
Motion. If your system requests reduced motion, we disable animations and transitions. Nothing flashes and nothing plays automatically with sound.
Forms. Every field has a visible label, errors are explained in text — not only in red — and say what to do to correct them.
Touch. On mobile, no tappable element goes below 44 × 44 pixels, with sufficient separation between them.

03What does not comply yet

This site is published new, so it carries no legacy material without captions and no untagged PDFs. When a concrete barrier appears — our own or in a third-party component — it is published here with the date by which we expect it resolved. If a date passes unmet, it is updated rather than deleted.

04How we check it

Automated review at every publication, a manual keyboard walkthrough and contrast verification on the design before anything is coded.

What we still don’t do as often as we should: testing with people who use a screen reader daily. When it becomes part of the routine, we say so here.

05If you find a barrier, tell us

If you find an accessibility barrier, contact us at the contact form and tell us the page, the problem and, if possible, the device or assistive technology used.

With that information we can reproduce the problem and fix it. If something can’t be resolved, we say so and offer an alternative way to get what you needed.

Version history
1.0 First version published with the new site.

The date this document was last updated will be shown on this page when there are relevant changes.

A question about your data?

Get in touch and we’ll resolve it. No legal forms or particular wording are needed: just explain what you need.

Escribir a the contact form