Join Club One

Accessibility statement for Mobile app

Last reviewed date: 28 July 2025

This is an accessibility statement for the Tallink Silja Line mobile app 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 Silja Line mobile app 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 Silja Line mobile app is designed and tested to be compatible at least with the following assistive technologies:

  • iOS with VoiceOver screen reader;
  • iOS with VoiceOver voice commands;
  • Android with TalkBack screen reader;
  • Android with Voice Access voice commands;
  • Both Android and iOS with a physical keyboard;
  • 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.

Native app

  • The app doesn’t fully follow the device settings for font size and type. (11.7 User preferences)
  • In Android, the app can only be used in portrait orientation. (11.1.3.4 Orientation)
  • In OS, on the Club One page, in landscape orientation, only a part of the Club One card and “Close” button are visible, the rest of the page cannot be scrolled into view. The “Close” button may not be clickable. (11.1.3.4 Orientation)
  • On the settings page, when a modal dialog opens, screen reader (11.1.3.2 Meaningful sequence) and keyboard focus (11.2.4.3 Focus order) may move on behind the modal.
  • Headings are not marked up as headings for assistive technologies. (11.5.2.10 Text)
  • Not all links and buttons are read out as links / buttons by the screen readers. (11.5.2.5 Object information) Since 11.5.2.5 is failed, then 11.4.1.2 is also failed. (11.4.1.2 Name, role value)
  • It may not be possible to activate all links and buttons with voice commands. (11.5.2.12 Execution of available action)
  • In Android, some interactive elements don’t have visible focus styles when navigating with an external Bluetooth-connected keyboard, making it difficult to understand where the focus currently is. (11.2.4.7 Focus visible)
  • The screen readers read the whole booking card out as one text element. Some of the information is read in a confusing order. (11.1.3.2 Meaningful sequence)
  • On the Club One page, screen readers do not read out the Club One card and the QR code. (11.5.2.10 Text)
  • On the Club One page, screen readers don’t read the Club One level progress bars out in an understandable way. (11.1.3.1 Info and relationships)
  • In iOS, it is not possible to change the country and language settings with an external Bluetooth-connected keyboard (11.2.1.1 Keyboard), voice commands or screen reader. (11.5.2.12 Execution of available action)
  • In iOS, on the Club One page, it is not possible to activate the “Add to Apple Wallet” button with an external Bluetooth-connected keyboard (11.2.1.1 Keyboard), voice commands or screen reader. (11.5.2.12 Execution of available action)
  • Screen readers do not announce when the page is being loaded. (11.4.1.3 Status messages)
  • When a booking is added by entering the booking number and security code, screen reader does not announce if the booking was added successfully. (11.4.1.3 Status messages)
  • The input fields are not connected to their respective labels in code. (11.5.2.8 Label relationships)
  • On Android, when an incorrect booking number or security code are entered, an error message is displayed which may not give enough information about what went wrong. (11.3.3.3 Error suggestion)
  • The logo is missing a text alternative. (9.1.1.1 Non-text content)
  • In Android, the settings button is missing a text alternative. (11.1.1.1 Non-text content)
  • Some decorative images and icons may be read out by screen readers as uninformative texts. (9.1.1.1 Non-text content)
  • Green texts do not have sufficient contrast with their background colors. (11.1.4.3 Contrast (minimum))
  • Some clickable icons, progress bars, and toggles in “off” state do not have sufficient contrast with their background. (11.1.4.11 Non-text contrast)

Journey timeline (web view)

  • The texts do not fully respond to the device’s font size and type settings. (11.7 User preferences)
  • In Android, after increasing font size in settings, some content isn’t fully visible. (9.1.4.4 Resize text)
  • On rare occasions, a part of the page may require two-way scrolling to see all information. (9.1.4.10 Reflow)
  • Headings are not marked as headings for assistive technologies. (9.1.3.1 Info and relationships)
  • Screen readers read out the route as e.g. “TAL HEL” from which it may not be clear, that it’s a trip from Tallinn to Helsinki. (9.2.4.6 Headings and labels)
  • Some green, gray and white texts are not contrasted enough. (9.1.4.3 Contrast (minimum))
  • Some clickable icons do not have sufficient contrast with their background. (9.1.4.11 Non-text contrast)
  • On the ship maps, the different areas are marked only with different colors, and the colours are not always contrasted enough against each other. (9.1.4.1 Use of color)
  • The ship maps lack meaningful 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 illustrative icons and images may be read out by screen readers. (9.1.1.1 Non-text content)
  • In iOS, the journey timeline back button’s accessible name is “Navibar back white” which can be confusing. On some pages, the back button is missing a text alternative. In both iOS and Android, the accessibility statement icon button’s accessible name is “Read our accessibility statement” which may be difficult to guess for voice command users. (9.1.1.1 Non-text content)
  • The back arrow icon button is visually the first element but is read out by screen readers as the last element. (9.1.3.2 Meaningful sequence)
  • On rare occasions, content may be read out by the screen reader in a confusing order. (9.1.3.2 Meaningful sequence)
  • Some texts may be read out by screen readers even if visually hidden. (9.1.3.2 Meaningful sequence)
  • Not all links and buttons are read out as links / buttons by the screen readers. (11.5.2.5 Object information)
  • The role and current state of tabs are not accessible for assistive technologies. (9.4.1.2 Name, role, value)
  • Some buttons, links and input fields are accessible with an external Bluetooth-connected keyboard. (9.2.1.1 Keyboard)
  • On rare occasions, a few interactive elements may not have visible focus styles when navigating with an external Bluetooth-connected keyboard, making it difficult to understand where the focus currently is. (11.2.4.7 Focus visible)
  • In Android, “Info for passengers with cars” and “View travel class info” buttons cannot be activated with the screen reader. (9.4.1.2 Name, role, value)
  • It may not be possible to activate all links and buttons with voice commands. (9.4.1.2 Name, role, value)
  • When a modal dialog is open, the screen reader (9.1.3.2 Meaningful sequence) and keyboard focus (9.2.4.3 Focus order) may move behind the modal.
  • In the “Add to calendar” modal, the input fields are not programmatically connected to their respective labels. (9.1.3.1 Info and relationships)
  • After clicking “Copy link to clipboard”, a message “Link copied to clipboard!” appears on the screen. That message is not automatically read out by screen readers. (9.4.1.3 Status messages)
  • “Thanks for your order” modal and welcome messages close automatically after a few seconds. This time limit cannot be extended. ( 9.2.2.1 Timing adjustable)
  • On the journey timeline, there are numbers displayed in front of each step. When navigating with a screen reader, the meaning of those numbers may be unclear.
  • In tablet and desktop versions, there is an additional text displayed on the right of the journey timeline. The text refers to the timeline as “on the left”. In the code, the timeline is before the additional text. (9.1.3.3 Sensory characteristics)