Join Club One

Accessibility statement for Mobile Booking site

Last reviewed date: 28 June 2025

This is an accessibility statement for mobile.tallink.com from Tallink, first published on 28 June 2025.

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

Compatibility

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

  • 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%).

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 website is not navigable with a keyboard. (9.2.1.1 Keyboard)
  • Texts on the page do not respond to the browser’s font resize settings. (11.7 User preferences)
  • When zooming the page using e.g. browser zoom, depending on the screen size, a few elements may become partially hidden. (9.1.4.4 Resize text)
  • Some texts do not have sufficient contrast with their background colors. (9.1.4.3 Contrast (minimum))
  • The title of the page does not change according to the opened page and is not translated according to the selected language. (9.2.4.2 Page titled)
  • Page sections are not marked as regions in code. (9.1.3.1 Info and relationships)
  • Headings are not marked as headings in code. (9.1.3.1 Info and relationships)
  • When a new page or a modal dialog opens, the screen reader does not announce that, and the focus may get lost or move behind the modal. (9.1.3.2 Meaningful sequence)
  • When error messages appear, they are not announced automatically by the screen readers. (9.4.1.3 Status messages)
  • Some messages disappear automatically after a few seconds. (9.2.2.1 Timing adjustable)
  • When info about the outward and return trips is shown in two columns, it may be read out by the screen reader in incorrect order, row by row. (9.1.3.2 Meaningful sequence)
  • Some decorative images and icons may be read out by screen readers as file names. (9.1.1.1 Non-text content)
  • Some links / buttons are not read out as links / buttons by screen readers. (9.4.1.2 Name, role, value)
  • Disabled buttons are not always read out as “disabled” by screen readers. (9.4.1.2 Name, role, value)
  • Inputs are not always programmatically connected to their labels. (9.4.1.2 Name, role, value)
  • Required input fields are not always marked as required in code. (9.4.1.2 Name, role, value)
  • Input fields sometimes include “X” buttons that empty the field. These are not always accessible for assistive technologies. (9.4.1.2 Name, role, value)
  • On some pages, in the top left corner, there is a “Back” button with an arrow icon which is missing a text alternative. Its name and role are not accessible with assistive technologies. (9.4.1.2 Name, role, value)
  • Links that expand description texts or that are inside description texts cannot be activated with assistive technologies. (9.4.1.2 Name, role, value)
  • Full description texts are read out by screen readers even if visually hidden. (9.1.3.2 Meaningful sequence)
  • In calendars, the name, role, and current state of the date selections are not accessible for assistive technologies. (9.4.1.2 Name, role, value)
  • The toggle for joining Club One is not accessible for assistive technologies. (9.4.1.2 Name, role, value)
  • The toggle for joining Club One does not have sufficient contrast with its background. (9.1.4.11 Non-text contrast)

Home page

  • The logo is missing a text alternative. (9.1.1.1 Non-text content)
  • There are three tabs “Ship”, “Ship + Hotel” and “Hotel”, of which the first one is selected by default. Their role and current state are not accessible for assistive technologies. (9.4.1.2 Name, role, value)
  • The buttons “From” and “To” open a modal with destination options. The role and current state of the “From” and “To” buttons and the destination options are not accessible for assistive technologies. (9.4.1.2 Name, role, value)
  • There is a button between “From” and “To” which changes the direction of the trip. The button has no text alternative. (9.4.1.2 Name, role, value)

Timetables

  • There may be trip type tabs at the top of the page, of which the first one is selected by default. Their role and current state are not accessible for assistive technologies. (9.4.1.2 Name, role, value)
  • There are buttons in the timetables which add a car to the booking. The button has no text alternative. (9.4.1.2 Name, role, value)
  • When car is selected, car prices are shown in the calendars. When it is not possible to book a car on a certain date, an icon is shown instead of a price, but it has no text alternative. (9.4.1.2 Name, role, value)
  • Some dates in the cruise calendar open a description text when selected. The description text is not programmatically connected to the selected cruise date. The description is read out by screen readers after the last day of the week. (9.1.3.2 Meaningful sequence)
  • When clicking “Load more” in the calendar, screen reader focus moves onto the “Done” button instead of the new dates. (9.1.3.2 Meaningful sequence)

Passengers & vehicles

  • On the Passengers and the Vehicles pages, there are four buttons at the top of the page that add different passengers or vehicles to the booking. The buttons are not read out as buttons by screen readers. (9.4.1.2 Name, role, value)
  • On the Vehicles page, the “Show all” button opens a list of buttons to add all different vehicle categories. The buttons are not read out as buttons by screen readers. (9.4.1.2 Name, role, value)
  • When passengers or vehicles are added or removed, the screen reader doesn’t announce the change. (9.4.1.3 Status messages)
  • Added passengers can be edited by clicking on “Fill out now or later” links, but these links are not read out as links by screen readers. (9.4.1.2 Name, role, value)
  • Added vehicles have “Remove” buttons, but they are not read out as buttons by screen readers. (9.4.1.2 Name, role, value)
  • Added passengers cannot be removed with assistive technologies. (9.4.1.2 Name, role, value)
  • 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)
  • The “Vehicle licence plate number” input field is not programmatically connected to its label. (9.4.1.2 Name, role, value)
  • On the passenger details page, fields with multiple inputs like gender and date of birth are not programmatically connected. (9.1.3.1 Info and relationships

Travel class, hotels, meals, services

  • The amount of some services can be adjusted using buttons with “-” and “+” icons. The decreasing button is before the amount and the increasing button is after the amount. The buttons are missing text alternatives. (9.1.1.1 Non-text content)
  • When services are added or removed, screen reader doesn’t announce the change. (9.4.1.3 Status messages)
  • Sometimes, when travel class is unavailable, the button area is grayed out, but this information is not read out by screen readers. (9.1.3.1 Info and relationships)
  • When there are multiple images of one cabin, there are arrow buttons on the left and right side of the image. The arrow buttons lack text alternatives. (9.1.1.1 Non-text content)
  • The different cabin surprises can be seen under the selected cabin only by swiping left and right with a finger. (2.5.7 Dragging Movements)
  • Screen reader users cannot skip the cabin surprise section and must move over each item in the list. (9.1.3.2 Meaningful sequence)
  • Buttons for adding meals and extra services can be selected or unselected, but their role and current state are not accessible for assistive technologies. (9.4.1.2 Name, role, value)
  • Buttons for adding meals and extra services are not connected to additional information like the time and price. (9.1.3.1 Info and relationships)
  • On the hotels list page, the hotel ratings are not read out by screen readers. (9.1.3.1 Info and relationships)
  • On the hotels list page, there may be tabs for “Check in” and “Check out” and for different cities, but their role and current state are not accessible for assistive technologies. The first tab is selected by default. (9.4.1.2 Name, role, value)
  • On the hotel room selection page, in the top left corner, there is a “Back” button with an arrow icon which is not accessible with assistive technologies. Alternatively, it is possible to exit the view by clicking the “Done” button. (9.4.1.2 Name, role, value)

Checkout and payment

  • On the payment overview and methods page, there can be radio buttons for selecting the payment method. Their role and current state are not accessible for assistive technologies. The first radio button is selected by default. (9.4.1.2 Name, role, value)
  • On the payment page, there is a button with an X icon at the top right corner which has a title “← Back” which does not match the visual label. (9.2.5.3 Label in name)

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)