Accessibility statement

Last updated: 5 October 2026

SupaSailing SL wants supaferry.com, the passenger booking site and the operator back office to be usable by everyone, including people who rely on assistive technology. This statement describes what we do, how we test, and how to tell us when something is in the way.

1. Standard and scope

We build to the Web Content Accessibility Guidelines (WCAG) 2.2, level AA, which is the level the European Web Accessibility Directive (2016/2102), the European Accessibility Act (2019/882) and the Spanish Royal Decree 1112/2018 require of public bodies and of the digital services they procure. The statement covers the product website, the passenger booking site (/book) and the operator back office (/admin).

2. What is in place

  • Keyboard: every control can be reached and operated with the keyboard; a skip link is the first focusable element on each page and focus is always visible.
  • Structure: one main landmark, headings in order, labelled form fields, error messages tied to their fields, tables with headers.
  • Reading preferences: the accessibility panel on every page offers text size, high contrast, reduced motion, a large cursor, a dyslexia-friendly typeface (Atkinson Hyperlegible), wider line and letter spacing, link highlighting, hidden images, a reading ruler and read-aloud. Choices stay on the device.
  • Colour: contrast of at least 4.5:1 for text in the default theme; information is never carried by colour alone (status badges carry text).
  • Motion: no auto-playing animation; the system setting for reduced motion is respected.
  • Documents: tickets and bills of lading print with real text, not images of text; QR codes come with the same code printed in letters.
  • Language: each page declares its language; the booking site can be translated per operator.

3. How we test

Every release is checked with automated audits (Lighthouse and axe rules) in the build, and the booking and boarding flows are exercised with a keyboard and a screen reader (VoiceOver on macOS and iOS, NVDA on Windows) before a release that changes them. Automated scores are published to customers on request.

4. Known limitations

  • Operator branding: an operator may choose a primary colour with insufficient contrast for white text. The platform switches the text to dark automatically, and the high-contrast mode overrides the branding entirely.
  • Third-party payment pages: when a card gateway hosts its own page, its accessibility is the gateway's. We choose providers that publish a conformance statement.
  • PDF tickets are tagged for reading order but not yet fully PDF/UA; the same ticket is available as an accessible web page.

5. Feedback and enforcement

If you cannot use part of the service, write to [email protected] or call +34 617 731 448. We answer within five working days and fix blocking issues as a priority. If you are not satisfied with our answer, you can contact the enforcement body for your country; in Spain this is the Ministry for Digital Transformation's Unit responsible for the accessibility of public sector websites.

6. Preparation of this statement

This statement was prepared on 5 October 2026 on the basis of a self-assessment and automated audits of the three surfaces named above. It is reviewed at every major release.