Top (back to the top of the page)

How we checked the website

The website was checked with axe-core, a free tool from the company Deque Systems that automatically checks whether a web page is accessible; that is, whether it can be used by people with a screen reader, with a keyboard only, with low vision and with other needs.

It opens each page in a browser and checks it against some seventy rules from the WCAG guidelines. For example, it looks at whether images have alternative text for people who cannot see them, whether every button and form field has a name that a screen reader can read out, whether text has enough contrast against its background and whether the page is properly structured.

We ran it on every page of the website, in Spanish and in English (24 pages), on both mobile and desktop (48 views), using version 4.14. What the tool cannot resolve on its own, such as the colour contrast of certain text, is left for manual review.

What WCAG is

Think of a building with ramps for people in wheelchairs, big signs for people who see poorly and announcements you can hear for people who cannot read. It is built so that everyone can get in and move around. WCAG is the set of rules that asks for the same thing, but for web pages.

They were written by the W3C, an international organisation that works to make the internet work the same for everyone. WCAG stands for Web Content Accessibility Guidelines. They say things like these:

  • Every photo needs a written description. That way, a blind person knows what is in it, because their computer reads it out loud.
  • Everything has to work with the keyboard alone, without a mouse, for people who cannot use a mouse.
  • Letters have to stand out clearly from the background, so they can be read even with poor eyesight.

The rules have three levels: A, AA and AAA, a bit like the levels of a video game. A is the basics, AA is more demanding and is the level usually taken as the target, and AAA is the hardest of all. This website follows version 2.2 at level AA.

This page does not present an accessibility certification: it reports measurements and their limitations.

Latest review: 12 October 2026

On that day axe-core was run on all 24 pages, and our own in-browser measurements were added for what automated tools do not check:

  • Visible, unobscured focus (2.4.7 and 2.4.11): tabbing through each page, on mobile and on desktop, no focused element was found to be completely obscured. The focus outline on form fields has a contrast ratio of 5.57:1 (the minimum is 3:1).
  • Size of buttons and links (2.5.8): across all 24 pages, none is smaller than 24 × 24 pixels without having the spacing the standard requires.
  • Motion (2.2.2): after each page loaded on desktop, no timed animation was detected repeating indefinitely; the longest measurable duration was 4.5 seconds. With the system “reduce motion” setting turned on, animations are switched off and transitions are cut to an imperceptible duration.
  • Cookies and external resources: during the review of all 24 pages, only the first-party session cookie (PHPSESSID, deleted when the browser is closed) was detected, with no requests to other domains. That is why there is no cookie notice covering the content.

What was fixed

The review of 12 October found four failures in the version that was published at the time:

  • the text that screen readers announced on the language selector did not match the text shown on screen;
  • the cookie notice could cover the element selected with the keyboard;
  • the “Booking” button had an animation that did not stop;
  • the selection outline on form fields had low contrast.

All four were fixed and published the same day, and the published website was measured again.

What this review does not cover

Automated tests and in-browser measurements are necessary, but they are not enough. They do not replace real people using screen readers, magnifiers or other assistive technology, and that testing has not yet been done. The measurements were made with Chrome; they have not been repeated in Firefox or Safari.

Have you found a fault?

Please send it to us and we will fix it. If you come across a barrier while using this website with any assistive technology, tell us with the button below or write to sanildefonso [at] crusa [dot] es.

Report a fault