Accessibility statement for Shopping website

Last reviewed date: 28 June 2025

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

You can also visit Tallink Silja Line stores in Tallinn or get more information by contacting the customer service.

Compatibility

Shopping.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

• Some pages are missing titles or have titles that are not unique or descriptive. (9.2.4.2 Page titled)
• Headings are not always correctly marked up. (9.1.3.1 Info and relationships)
• Some light green and gray texts are not contrasted enough. (9.1.4.3 Contrast (minimum))
• The terms «wishlist» and «shopping list» are used interchangeably. The terms «cart» and «basket» are used interchangeably. (9.3.2.4 Consistent identification)
• There are multiple navigation and header regions that are not uniquely labelled. Some pages may be missing a main region. (9.1.3.1 Info and relationships)
• Not all texts on the page respond to the browser’s font resize settings. (11.7 User preferences)
• When the page is zoomed in to mobile view, the “Print” button is hidden. (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)
• On a small mobile device, tabs may become horizontally scrollable. Tabs may be scrollable only by sliding with a finger or they may have arrow buttons which are not clickable. (9.2.5.1 Pointer gestures)
• 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)
• Interactive elements do not always receive a visual focus style when navigated to with a keyboard. (9.2.4.7 Focus visible)
• On a rare occasion, it may not be possible to focus and use an interactive element with keyboard. (9.2.1.1 Keyboard)
• Keyboard focus may move onto invisible content and get stuck. (9.2.1.2 No keyboard trap)
• Screen reader focus may stay behind the modal when it opens. (9.1.3.2 Meaningful sequence)
• It may not be possible to close modals using assistive technologies. (9.2.1.1 Keyboard, 9.4.1.2 Name, role, value)
• Tab content may not always change when tabs are used with keyboard. (9.2.1.1 Keyboard)
• Screen reader and keyboard focus may sometimes jump to an unexpected location after clicking an expandable accordion, button or input. (9.2.4.3 Focus order)
• The role and state of the language selector, some menu elements, search box, tabs, cart steps, expandable accordions, star rating buttons, 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)
• Status messages are not automatically announced by the screen readers. (9.4.1.3 Status messages)
• Some expandable accordions and dropdowns may be read out twice by screen readers. (9.1.3.2 Meaningful sequence)
• Some clickable elements may be focused twice when navigating with keyboard. (9.2.4.3 Focus order)
• Screen reader’s focus may not go onto tooltips. (9.1.3.1 Info and relationships)
• It may not be possible to open tooltips with keyboard. (9.2.1.1 Keyboard)
• Tooltips cannot be closed without moving the focus away. (9.1.4.13 Content on hover and focus)
• On a rare occasion, screen reader may read out uninformative or confusing elements. (9.1.3.1 Info and relationships)
• Product cards contain three links which all lead to the same product detail page: the product’s image, the product’s name and the «View details» button. (9.2.4.4 Link purpose (in context))
• When clicking a page number in the pagination with a keyboard or screen reader, focus doesn’t go to the content of that page. (9.2.4.3 Focus order)

Inputs

• Some inputs are missing labels. (9.3.3.2 Labels or instructions)
• Some inputs are not connected to their labels in code. (9.1.3.1 Info and relationships)
• Some labels may not give enough information about the input. (9.3.3.2 Labels or instructions)
• Invalid or required input fields are sometimes shown only with a light red background color. (9.1.4.1 Use of color)
• When inputs fields are not correctly filled, error messages are not always shown. (9.3.3.1 Error identification)
• Some error messages may not give enough information about how to fix the error. (9.3.3.3 Error suggestion)
• Some product amount inputs can be typed into when navigating with a keyboard, but not with e.g. a mouse. (9.4.1.2 Name, role, value)
• Radio buttons may not always be properly grouped. (9.1.3.1 Info and relationships)

Menu

• Some main menu buttons open a submenu when clicked, but they cannot always be opened using screen readers. (9.4.1.2 Name, role, value)
• Some menu elements are expandable, but screen reader does not say that they can be expanded and does not read out their current states. (9.4.1.2 Name, role, value)
• On desktop, submenus open when hovered with the mouse, but they cannot be closed without moving the focus away. (9.1.4.13 Content on hover and focus)

Images

• Image / icon buttons may have text alternatives that are not translated according to the selected language. (9.2.4.6 Headings and labels)
• Product and banner images may be read out by the screen readers as numbers, uninformative or repetitive text. (9.1.1.1 Non-text content)
• Some icon buttons are missing text alternatives and are read out by the screen readers as “buttons” or uninformative text. Voice command users may not be able to activate those buttons. (9.4.1.2 Name, role, value)
• Some decorative and uninformative icons may be read out by the screen readers. (9.1.1.1 Non-text content)
• Product star-ratings are not read out by screen readers. (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)
• On the cart page, on mobile, the steps are read out by the screen readers as just «images». (9.1.1.1 Non-text content)

Carousels

• It is not possible to stop the automatic changing of the carousel banner. (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 scrolled into view 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)