TuriTop
it
Español English Português Italiano
Accedi Prova gratis →
Prova gratis

Note legali

Accessibility Statement

URL: /accessibility-statement Last reviewed: June 12, 2026 Next scheduled review: December 12, 2026

Our Commitment

At TuriTop, we believe that the web should work for everyone, regardless of their abilities. We are working to make turitop.com accessible to as many users as possible and to comply with applicable regulations, including Royal Decree 1112/2018 and the European Accessibility Act (EAA, Directive (EU) 2019/882), effective as of June 28, 2025.

Compliance Status

This website is partially compliant with the Web Content Accessibility Guidelines (WCAG) 2.1 Level AA, with the exceptions detailed below. The site was developed with accessibility criteria incorporated from the design phase:

  • Semantic structure: consistent use of <header>, <main>, <nav>, <footer>, hierarchical headings without level skips.
  • Color contrast: calibrated palette—the corporate green #1a7d80 on a white background meets the AAA ratio.
  • Keyboard navigation: All interactive elements are accessible via Tab and operable with Enter / Space. Focus indicators are visible on all buttons and links.
  • Alternative text: All informational images include a descriptive alt attribute. Decorative images are marked with alt=&quot;&quot; or role=&quot;presentation&quot;.
  • Multilingual: The lang attribute is set correctly for each locale (es / en / fr / it / pt / de).
  • Reduced motion: The site respects the user’s prefers-reduced-motion preference—scroll, hover, and transition animations are automatically disabled.
  • Touch Target Size: Interactive elements on mobile devices meet the minimum requirement of 24×24 pixels (WCAG 2.5.8), with most reaching 44×44 pixels (Apple HIG, Android Material).
  • Accessible cookie banner: The consent panel uses the vanilla-cookieconsent library, which provides correct ARIA semantics, focus management, and full keyboard support.

Non-Accessible Content

Despite our efforts, some elements may not fully comply with WCAG 2.1 AA at this time:

  • AI-generated images in some blog posts: Some header illustrations may have generic alt text. These will be reviewed and updated with complete descriptive text during the first quarter of 2026.
  • Third-party embeds (maps, YouTube videos, HubSpot calendars): These may not be 100% WCAG-compliant when embedded. When a limitation is detected, a text alternative is provided.
  • Complex comparison tables (pricing page): Although they have the correct <th> structure and are keyboard-navigable, on very narrow screens horizontal scrolling may make reading difficult. An alternative view is being evaluated.

How This Statement Was Prepared

This statement was prepared on June 12, 2026 through:

  • Continuous self-assessment: Each npm run preflight runs an audit using axe-core 4.x (the same engine used by Lighthouse). Results are available internally at /a11y-report.html.
  • Manual testing with screen readers (NVDA on Windows, VoiceOver on macOS) on critical pages: home, pricing, booking system, contact.
  • Keyboard testing on the main workflows—navigation, forms, and the cookie banner.
  • Lighthouse Accessibility in Google Chrome on the pages with the highest traffic.

Feedback and Contact Information

If you encounter any accessibility barriers on our site, or have suggestions for improving it, we’d love to hear from you. You can contact us via:

We are committed to responding within a maximum of 5 business days and resolving the reported issue based on its severity. Critical issues are prioritized for the next released version (typically 1–2 weeks).

Appeal Procedure

If a person believes that their accessibility requests have not been satisfactorily addressed, they may contact the relevant authorities:

Continuous Improvement Plan

Accessibility is an ongoing process, not a destination. TuriTop is committed to:

  1. Conducting an audit before each deployment using the automated script npm run preflight.
  2. Review this statement every 6 months or whenever significant changes are made to the site.
  3. Train the development and design teams on WCAG principles and testing with assistive technologies.
  4. Prioritize accessibility over commercial overlays—we prefer to fix the code rather than apply superficial patches that the accessibility community has shown to be counterproductive (Overlay Fact Sheet).

Technical Information

  • Technologies used: HTML5, CSS3, JavaScript ES2020+, Astro 7 framework (static rendering).
  • Tested assistive technology: NVDA 2024.x (Windows), VoiceOver (macOS 14+), keyboard navigation in Chrome / Firefox / Safari / Edge.
  • Audit tools: axe-core 4.x, Lighthouse (Accessibility category), WAVE.