Join Club One

Accessibility statement for Online Booking website

Last reviewed date: 28 June 2025

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

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

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;
  • 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 title of the page is not translated according to the selected language. (9.2.4.2 Page titled)
  • There is only one region on the page – the side panel – and it is unlabeled. Other page sections are not marked as regions. (9.1.3.1 Info and relationships)
  • Not all headings are marked up correctly. (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 zooming the page using e.g. browser zoom, a horizontal scroll bar appears, and the side panel is not fully visible. (9.1.4.10 Reflow)
  • Some texts do not have sufficient contrast with their background colors. (9.1.4.3 Contrast (minimum))
  • Some icons and inputs do not have sufficient contrast with their background colors. (9.1.4.11 Non-text contrast)
  • Arrow icons showing duration or direction are missing text alternatives. (9.1.1.1 Non-text content)
  • On rare occasions, some text alternatives may not be translated according to the selected language. (9.2.4.6 Headings and labels)
  • Some decorative images are read out by screen readers, causing repetitions. (9.1.1.1 Non-text content)
  • A few interactive elements are missing visible focus styles. (9.2.4.7 Focus visible)
  • Some links / buttons are not read out as links / buttons by screen readers (9.4.1.2 Name, role, value) and cannot be focused with keyboard. (9.2.1.1 Keyboard)
  • Tables do not always have correctly marked header cells. (9.1.3.1 Info and relationships)
  • Some messages and tooltips disappear automatically after a few seconds. (9.2.2.1 Timing adjustable)
  • When error messages appear, they are not announced automatically by the screen readers. (9.4.1.3 Status messages)
  • Closing buttons on modals and error messages cannot be focused and clicked with the keyboard. (9.2.1.1 Keyboard)
  • When modal dialogs open, screen reader does not announce that and the focus moves on under the modal. (9.1.3.2 Meaningful sequence)
  • On a rare occasion, the screen reader (9.1.3.2 Meaningful sequence) and keyboard focus (9.2.4.3 Focus order) may unexpectedly jump to the top of the page.

Top section

  • In the top section, in the calendar, the name, role, and current state of the date selections are not accessible for assistive technologies. (9.4.1.2 Name, role, value)
  • In the top section, in the calendar, when a keyboard user (using Tab navigation) enters the calendar, they cannot exit without moving through every date in the calendar. (9.2.1.2 No keyboard trap)
  • In the top section, the children amount selectors are not programmatically connected to their common label “Children”. (9.1.3.1 Info and relationships)
  • On amount selectors, there are buttons with “-” and “+” icons and an input field that shows the current value. The input field is read out as “read-only” and cannot be typed into, but the value still be changed with up and down arrow keys. (9.4.1.2 Name, role, value)
  • Reducing the number of adults to 0 will automatically add one 12–17-year-old child to the booking. Removing the child will add an adult to the booking. These changes happen automatically and are not announced by the screen readers. (9.4.1.3 Status messages)
  • In the top section, the city after “From” can be clicked and opens a list of departure city options, but its name and role are not accessible for assistive technologies. (9.4.1.2 Name, role, value)
  • In the top section, the name, role and current state of the city options after “To” are not accessible for assistive technologies. (9.4.1.2 Name, role, value)
  • In the top section, the trip types below the city options behave like radio buttons, as selecting a new option removes the previous one, but their role and current state are not accessible for assistive technologies. (9.4.1.2 Name, role, value)

Timetables

  • The “Roundtrip” and “One way” options may not be selectable with assistive technologies. (9.4.1.2 Name, role, value)
  • In the departures timetables, 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)
  • In the departures timetables, overnight departures are marked with a bed icon which opens a tooltip when hovered with a mouse. User cannot move their cursor onto the tooltip without it closing. This as well as other tooltips cannot be dismissed without moving the cursor. (9.1.4.13 Content on hover and focus)
  • Some timetables cannot be navigated with the keyboard. (9.2.1.1 Keyboard)
  • Screen readers read out information in the timetables in wrong order, row by row, losing connection between the route, date and departure details. Some information about the return trip is read out even in case of a one way trip. (9.1.3.2 Meaningful sequence)
  • The timetables are not correctly marked up as tables, so the connections between the data cells and the header cells are not available for assistive technologies. (9.1.3.1 Info and relationships)
  • The departures are not marked up as selectable options for assistive technologies. Screen readers do not say which departures are unavailable and which are selected. (9.4.1.2 Name, role, value)
  • In the departures timetables, some rows are marked with “No departures”, but this text has no programmatic association with any date. (9.1.3.1 Info and relationships)
  • In the departures timetables, automatic changes occur when user selects outward and return times that are impossible. These automatic changes are not communicated by the screen readers. (9.4.1.3 Status messages)

Side panel

  • In the side panel, the contact person fields do not have autocomplete attributes. (9.1.3.5 Identify input purpose)
  • In the side panel, the “Yes” and “No” buttons in the marketing e-mails section behave as radio buttons, as user can select only one of them, but their name, role, and current state are not accessible for assistive technologies. (9.4.1.2 Name, role, value)
  • In the side panel, the passengers name fields only have placeholders, but no labels. (9.3.3.2 Labels or instructions)
  • In the side panel, in the passengers section, the Club One icon button next to the name fields opens the Club One number input field, but the icon lacks a text alternative. The icon that appears after entering the number, also lacks a text alternative. (9.1.1.1 Non-text content)
  • The Club One number input field closes automatically on input. (9.3.2.2 On input)
  • In the side panel, incorrectly filled fields are marked with colour only, without a persistent error message. (9.3.3.1 Error identification)
  • The Club One points slider steps may be read out incorrectly with screen readers. (9.4.1.2 Name, role, value)

Issues in specific sections

  • In the hotel section, the city options next to “Filter by location” behave like radio buttons, as selecting a new option removes the previous one, but their role and current state are not accessible for assistive technologies. (9.4.1.2 Name, role, value)
  • In the hotel section, the arrow buttons that show more hotels do not have labels in code. (9.4.1.2 Name, role, value)
  • In the hotel section, the hotel ratings are not read out by screen readers. (9.1.3.1 Info and relationships)
  • In the hotel section, screen readers do not say which hotels are unavailable and which is selected. (9.4.1.2 Name, role, value)
  • The hotel room selection is marked up as nested lists which can be confusing for assistive technologies. (9.1.3.1 Info and relationships)
  • In the hotel section, the unavailable room icon does not have a text alternative. (9.1.1.1 Non-text content)
  • In the vehicles section, the “No vehicle selected” is a button which opens a list of vehicle options, but its role and current state are not accessible for assistive technologies. (9.4.1.2 Name, role, value)
  • In the vehicles section, it is not possible to select a vehicle using keyboard. (9.2.1.1 Keyboard)
  • In the travel class section, it is not possible to click the image thumbnails to view larger images using keyboard. (9.2.1.1 Keyboard)
  • In the onboard meeting room section, the time can be sometimes clicked to open a list of available times, but its role and current state are not accessible for assistive technologies. (9.4.1.2 Name, role, value)
  • In some sections, there are elements that can be expanded or collapsed, but their role and current state are not accessible for assistive technologies. (9.4.1.2 Name, role, value)
  • In some sections, the “Select” buttons behave as checkboxes, as they can be individually checked or unchecked, but their role and current state are not accessible for assistive technologies. (9.4.1.2 Name, role, value)
  • In some sections, the buttons with price per person behave as radio buttons, as selecting a new option removes the previous one, but their role and current state are not accessible for assistive technologies. (9.4.1.2 Name, role, value)
  • In some sections, the “Add” buttons are not programmatically connected to what can be added. (9.4.1.2 Name, role, value)
  • In some sections, when the “Add” button is clicked, another button with an “x” icon appears below it. Screen reader does not announce how many items are selected or that they can be removed by clicking the button below. (9.4.1.2 Name, role, value)

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)