Join Club One

Accessibility statement for Online Booking website

Last reviewed date: 30 April 2025

This is an accessibility statement for booking.tallink.com from Tallink, first published on 30 April 2025.

We want every journey with us to be smooth – both on sea and online. That’s why we’re working to ensure our website is accessible to all our guests, in line with the European Accessibility Directive and the standard EN 301 549.

This accessibility statement is based on an accessibility audit from an external evaluator. Tallink.com is not yet fully accessible. Known limitations are listed under “Known accessibility gaps”.

As an alternative, you can ask for information and book a trip by contacting the customer service.

Compatibility

Booking.tallink.com is designed and tested to be compatible at least with the following assistive technologies:

  • Chrome browser on PC with JAWS screen reader;
  • Chrome browser on PC with a physical keyboard;
  • Safari browser in iOS with VoiceOver screen reader;
  • Safari browser in iOS with Voice Control voice commands;
  • Safari browser in iOS with a physical keyboard;
  • Browser and operation system zoom and font size increase options (up to 200%).

Contact

If you spot an accessibility issue or need any information in a more accessible format, just drop us a line at info@tallink.ee or see more ways to contact us – we’ll do our best to make your experience with Tallink enjoyable and barrier-free.

Known Accessibility Gaps

This is the list of known issues and the EN 301 549 standard requirements that are not met. We’re prioritizing fixes based on user impact and technical feasibility, and we appreciate your patience as we make these improvements.

General

  • Some pages may have the same page title, and the page title may not be translated according to the selected language. (9.2.4.2 Page titled)
  • A skip link may be missing. (9.2.4.1 Bypass blocks)
  • Some pages may be missing a main region. (9.1.3.1 Info and relationships)
  • Some heading tags may be used inaccurately or in the wrong hierarchy. (9.1.3.1 Info and relationships)
  • On a rare occasion, screen reader focus may move to an unexpected place. (9.1.3.2 Meaningful sequence)
  • In some places, new content is automatically loaded and screen reader user may get stuck on the continuously added content. (9.1.3.2 Meaningful sequence)
  • Some icons may be missing text alternatives. Some decorative images may be read out by screen readers. (9.1.1.1 Non-text content)
  • Some labels and alternative texts may not be translated according to the selected language. (9.2.4.6 Headings and labels)
  • Lists may not always be correctly marked up. (9.1.3.1 Info and relationships)
  • Some tables may have an incorrect structure and missing headers. (9.1.3.1 Info and relationships)
  • On a rare occasion, visually hidden parts may be read out by screen readers. (9.1.3.2 Meaningful sequence)
  • Some elements may be read out multiple times by screen readers. (9.1.3.2 Meaningful sequence)
  • Some abbreviations may not be understandable when read out by screen reader. (9.1.3.1 Info and relationships)

Inputs and controls

  • Some inputs and controls may be missing labels or may not be connected to their labels. (9.3.3.2 Labels or instructions, 9.1.3.1 Info and relationships)
  • Some controls visible labels do not match their accessible names. (9.2.5.3 Label in name)
  • Some controls may not be programmatically connected their related context and may be unclear to assistive technologies. (9.2.4.6 Headings and labels, 9.1.3.1 Info and relationships)
  • Some controls may be missing a name and may not have the correct role or state. (9.4.1.2 Name, role, value)
  • Some optional fields may be marked as required for screen reader users. (9.1.3.1 Info and relationships)

Messages

  • Error messages and notifications are not always announced correctly and automatically by screen readers. (9.4.1.3 Status messages)
  • Keyboard focus may not be able to move onto links inside a floating error message. (9.2.1.1 Keyboard)
  • Some error messages may not explain what needs to be corrected. (9.3.3.3 Error suggestion)

Issues with specific elements

  • Cruise info button may not be accessible with screen readers or voice commands (9.4.1.2 Name, role, value) and is accessible with keyboard only after selecting the cruise. (9.2.4.3 Focus order)
  • Keyboard focus may move behind an open modal. (9.2.4.3 Focus order)
  • Keyboard focus may stop on the same dropdown multiple times. (9.2.4.3 Focus order)
  • Some accordions may not be closable with keyboard. (9.2.1.1 Keyboard)

Visual issues

  • Some links may not have sufficient contrast on hover. (9.1.4.3 Contrast (minimum))
  • Selected radio buttons and checkboxes may be missing visible focus styles. (9.2.4.7 Focus visible)
  • The focus style of some controls may be shown only with color. (9.1.4.1 Use of color)
  • In the departures table, the cheapest departures are marked only with color. (9.1.4.1 Use of color)
  • Some focused elements may be visually hidden under another element. (2.4.11 Focus Not Obscured (Minimum))
  • On smaller screens or when zooming in, some content may be hidden and available only by swiping. The arrow buttons may not be usable with a mouse or keyboard. (9.1.4.10 Reflow, 9.2.5.1 Pointer gestures)
  • When zooming in, some sections may become unusable as they get covered by sticky elements. (9.1.4.10 Reflow)
  • When resizing text, some texts may overlap or get partially hidden (9.1.4.4 Resize text)
  • On a rare occasion, link font size may not increase according to browser text size settings. (11.7 User preferences)