Join Club One

Accessibility statement for Booking Change website

Last reviewed date: 28 June 2025

This is an accessibility statement for change.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. Change.tallink.com is not yet fully accessible. Known limitations are listed under “Known accessibility gaps”.

As an alternative, you can change your current booking by contacting the customer service.

Compatibility

Change.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 accessibility@tallink.com 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

  • The title of the page is not translated according to the selected language. (9.2.4.2 Page titled)
  • Not all page regions are correctly marked up. (9.1.3.1 Info and relationships)
  • The page is missing a first level heading. Not all headings are correctly marked up. (9.1.3.1 Info and relationships)
  • Texts on the page do not respond to the browser’s font resize settings. (11.7 User preferences)
  • When the page is zoomed in using the browser settings, the page becomes horizontally scrollable. (9.1.4.10 Reflow)
  • Some green, gray and pink texts do not have sufficient contrast with their background colors. (9.1.4.3 Contrast (minimum))
  • On a mobile device, with an external Bluetooth-connected keyboard, most interactive elements cannot be focused and activated with keyboard. (9.2.1.1 Keyboard)
  • Some buttons cannot be focused and activated with keyboard. (9.2.1.1 Keyboard)
  • A few interactive elements are missing visible focus styles when navigating with keyboard. (9.2.4.7 Focus visible)
  • The page doesn’t always scroll the focused element into view and cannot always be scrolled into view when navigating with keyboard. (2.4.11 Focus Not Obscured (Minimum))
  • Informational tooltips cannot be opened with keyboard (9.2.1.1 Keyboard) nor screen readers (9.4.1.2 Name, role, value).
  • The passengers in cabin, the gender and the payment radio buttons cannot be changed with keyboard. (9.2.1.1 Keyboard)
  • On desktop, the vehicle type selector cannot be used with keyboard. (9.2.1.1 Keyboard)
  • There are two vehicle categories that are called “passenger car” which may be confusing when the width and height are not displayed. (9.2.4.6 Headings and labels)
  • When a new page or a modal dialog opens, screen reader (9.1.3.2 Meaningful sequence) and keyboard focus may get lost or move behind the modal. (9.2.4.3 Focus order)
  • The role and current state of some interactive elements are not accessible to screen readers. (9.4.1.2 Name, role, value)
  • When items are added or removed, screen readers do not always give feedback about the changes. (9.4.1.3 Status messages)
  • There is no programmatic connection between the direction (outward/return), the item/service name, and the button for selecting it. (9.1.3.1 Info and relationships)
  • Departure and arrival times are read out by the screen reader in incorrect order, row by row. (9.1.3.2 Meaningful sequence)
  • In mobile version, the passenger “Edit” buttons are read out by the screen readers before the name of the passenger which may create confusion. (9.1.3.2 Meaningful sequence)
  • Full description texts are read out by screen readers even if visually hidden. (9.1.3.2 Meaningful sequence)

Timetables

  • It is not possible to choose a departure in the timetable or choose a date from the calendar with keyboard. (9.2.1.1 Keyboard)
  • The departures timetable and the date picker calendar are not fully understandable with screen readers. (9.4.1.2 Name, role, value)
  • In desktop version, the departures timetable is read out by the screen reader in a confusing order that does not convey the relationships between the direction, the header and the data. (9.1.3.2 Meaningful sequence)

Inputs

  • Some input fields may not be correctly connected to their labels. (9.1.3.1 Info and relationships)
  • Mandatory fields are not programmatically marked as required. (9.1.3.1 Info and relationships)
  • Invalid fields are shown with only pink colour (9.1.4.1 Use of color) and are missing error messages. (9.3.3.3 Error suggestion)
  • On desktop version, invalid fields’ error messages are shown only as tooltips when the fields are hovered with a mouse. The tooltips cannot be opened with assistive technologies (9.4.1.2 Name, role, value). The tooltips cannot be dismissed or hovered. (9.1.4.13 Content on hover and focus)
  • When error messages appear, they are not read out automatically by the screen readers. (9.4.1.3 Status messages)
  • After selecting an option from a dropdown, the screen reader focus may unexpectedly jump to the beginning of the page (9.1.3.2 Meaningful sequence).
  • When user selects a need for special assistance, an info text appears, but it is not announced by the screen readers. (9.4.1.3 Status messages) The info text may include links that are not clickable or do not take user to the expected location. (9.2.4.4 Link purpose (in context))

Images

  • The logo in the header and the Club One card images are missing text alternatives. (9.1.1.1 Non-text content)
  • In the departures timetables, overnight trip, price per adult and price per car are marked with icons, but these icons are missing text alternatives. (9.1.1.1 Non-text content)
  • The vehicle height and width are read out as just numbers because the height and width icons are missing text alternatives. (9.1.1.1 Non-text content)
  • Some decorative images are read out by the screen readers. (9.1.1.1 Non-text content)
  • Some images have text alternatives that repeat the text that is visible next to the images. (9.1.1.1 Non-text content)

Cookie modal

  • The cookie modal’s label in code is “Modal” which may not be clear for screen reader users. (9.2.4.6 Headings and labels)
  • After clicking “Change settings”, the screen reader’s focus is lost and may move behind the modal. (9.1.3.2 Meaningful sequence)
  • After clicking “Change settings”, three tabs are shown, of which the first one is selected, but their role and current state are not accessible for assistive technologies. (9.4.1.2 Name, role, value)
  • The active and non-active tab are differentiated only by colour. (9.1.4.1 Use of color)
  • The language selector’s label in code is “Choose your language”, regardless of the selected language. (9.2.4.6 Headings and labels)
  • The language options in the language selector may be mispronounced by screen readers. (9.3.1.2 Language of parts)
  • Screen readers do not say which language option is selected. (9.4.1.2 Name, role, value)
  • Gray text and hovered links do not have sufficient contrast with their background colors. (9.1.4.3 Contrast (minimum))
  • Screen reader may read out some decorative images from the cookie modal. (9.1.1.1 Non-text content)