The Spanish version is the legally binding version. Read the Spanish text.
- Content supports keyboard navigation.
- Informative images have alternative text.
- Device settings can reduce animation.
- Report barriers with the page and issue encountered.
1. Objective and scope
The website uses WCAG 2.2 AA as a technical reference. This statement is not independent certification or a claim of complete conformance without a full audit. Specific duties, including the European accessibility framework, depend on the service and provider circumstances. The described scope covers static Spanish and English pages, navigation, expandable questions and preference settings. It does not establish physical accessibility at an unverified facility.
2. Navigation and structure
Pages include a skip link, one main heading and section headings supporting reading. Links have real destinations and controls show visible focus. The mobile menu opens by keyboard and closes with Escape, returning focus to its button. Language switching leads to the equivalent page. Questions use native browser controls. Tables sit inside scrollable containers so narrow screens do not cut off essential information.
3. Reading and motion
Text uses a readable base size and supports browser enlargement. Columns adapt to available width and long words can wrap. Informative images have scene descriptions without identity claims. Decorative motion is disabled when the device requests reduced motion. Text and background colours are reviewed for readability, but automated checks are not a replacement for assessment with users and assistive technologies.
4. Forms and external services
Fields have explicit labels and consent is not accepted through a preselected checkbox. The preference notice does not block reading and permits optional categories to be rejected. The future FormSubmit receiving flow needs assessment before activation, including accessibility review. External pages may change independently. If a channel is unusable, describe the barrier and request a suitable alternative before sharing sensitive information.
5. Reporting a barrier
Contact [email protected] with the page, device, browser and action you could not complete. Avoid unnecessary personal information when describing the difficulty. The proposed response time is 2 business days. Issues should be reviewed, a solution considered and progress explained clearly. Access requirements for an in-person session need confirmation before booking rather than assumptions from photographs. This statement is reviewed alongside meaningful changes in design, content or services.
Also read: Service terms · Privacy policy · Contact and booking.