Join Club One

Accessibility statement for tallink.com websites

Last reviewed date: 28 June 2025

This is an accessibility statement for tallink.com from Tallink, first published on 28 June 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

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

  • Headings are not always correctly marked up. (9.1.3.1 Info and relationships)
  • There are multiple navigation and header regions that are not uniquely labelled. The side menu is not marked as a navigation region. (9.1.3.1 Info and relationships)
  • The selected menu element in the side menu is marked only with colour. (9.1.4.1 Use of color)
  • Some light green and white texts do not have sufficient contrast with their background colors. (9.1.4.3 Contrast (minimum))
  • Texts on the page do not respond to the browser’s font resize settings. (11.7 User preferences)
  • On small screens or when the page is zoomed in, tabs may become horizontally scrollable. There are buttons for scrolling the tabs, but they do not function when clicked. The dropdowns’ and date picker’s options may not be fully visible. The feedback button may cover the content of the page. (9.1.4.10 Reflow)
  • On mobile devices when the page is zoomed in, text and icons may overlap or overflow their containers. (9.1.4.4 Resize text)
  • There is no skip-link that would allow to navigate to the main content of the page, skipping the header and navigation. (9.2.4.1 Bypass blocks)
  • Links that open PDF documents are not always marked accordingly. (9.2.4.4 Link purpose (in context))
  • On a mobile device, some tabs may not be focusable with an external keyboard. (9.2.1.1 Keyboard)
  • Keyboard focus may move onto closed modals and get stuck. (9.2.1.2 No keyboard trap)
  • On a rare occasion, an interactive element may not receive visual focus style when navigated to with a keyboard. (9.2.4.7 Focus visible)
  • The role and state of the language selector, some menu elements, tabs, search box, some expandable sections, some dropdowns and their options may not be accessible for screen readers. (9.4.1.2 Name, role, value)
  • Tables and lists are not always correctly marked up. (9.1.3.1 Info and relationships)
  • Some expandable accordion titles and dropdowns are read out twice by screen readers. (9.1.3.2 Meaningful sequence)
  • On a rare occasion, screen readers read out text that is visually hidden. (9.1.3.2 Meaningful sequence)
  • “Switch routes” button changes the direction of the selected trip, but screen reader users do not get feedback about the change. (9.4.1.3 Status messages)
  • Status messages are not automatically announced by the screen readers. (9.4.1.3 Status messages)
  • When modals are opened, they are not always announced by screen readers. (9.4.1.2 Name, role, value)
  • Language options are missing the respective language tags. (9.3.1.2 Language of parts)
  • Expandable menu items may not be openable with screen readers. (9.4.1.2 Name, role, value)
  • Feedback and chat buttons cannot be activated with voice commands. (9.4.1.2 Name, role, value)

Inputs

  • The search box in the header is missing a label. (9.3.3.2 Labels or instructions)
  • It is not possible to choose a date from the calendar with keyboard. (9.2.1.1 Keyboard)
  • The date picker calendars are not fully understandable with screen readers. (9.4.1.2 Name, role, value)
  • There are dropdowns for choosing the start and destination cities. The meaning of those dropdowns may not be clear for screen reader users. (9.4.1.2 Name, role, value)
  • Some dropdowns are focused twice when navigating with keyboard. (9.2.4.3 Focus order)
  • Radio buttons may not be properly grouped. (9.1.3.1 Info and relationships)
  • Screen reader and keyboard focus may sometimes jump to an unexpected location after closing a dropdown, date picker or search box. (9.2.4.3 Focus order)

Images

  • The search box includes an icon button labelled “Close search” but it does not close the search, but empties it instead. (9.2.4.6 Headings and labels)
  • Image / icon buttons may have text alternatives that are not translated according to the selected language. (9.2.4.6 Headings and labels)
  • Some icons are missing text alternatives are read out by the screen readers as “images” or “buttons”. Some images are read out by the screen readers as numbers or repetitive text. (9.1.1.1 Non-text content)
  • On a rare occasion, text on a banner is presented as an image. (9.1.4.5 Images of text)

Carousels

  • It is not possible to stop the automatic changing of the carousel slides. (9.2.2.2 Pause, stop, hide)
  • Carousel’s navigation dots are not labelled so they are not understandable for screen readers and cannot be activated with voice commands. (9.4.1.2 Name, role, value)
  • Carousel’s navigation dots do not have enough contrast with their background. (9.1.4.11 Non-text contrast)
  • In some carousels, it is not possible to change the slides using a keyboard. (9.2.1.1 Keyboard)
  • In carousels, the focused element may not always be visible when navigating with a keyboard. (9.2.4.7 Focus visible)
  • In carousels, screen readers read out all slides of the carousel, even if not visible. (9.1.3.2 Meaningful sequence)