How we work with accessibility
We want our digital services to be accessible to as many people as possible, regardless of their circumstances. Therefore, we continuously work to identify and address accessibility issues. On this page, you will find our accessibility statement, where we describe the known challenges and how we plan to improve accessibility in the future.
How accessible are our digital services?
Have you encountered something that didn't work? We are very grateful if you report issues to us so we can improve the experience for everyone.
Our Platforms
Accessibility on the website skistar.com
Throughout 2024/2025, we have continuously worked to improve accessibility on skistar.com. This is an ongoing effort where we consider requirements and legislation in all new developments and continuously work to deprecate old solutions. The most common problems on the website are low contrast on graphic components, making it difficult to distinguish symbols and icons, and some images lack alt text, meaning they are not described for screen readers. In addition, icons are sometimes read as images because they lack accessible names, and focus indicators have low contrast, making them hard to see.
Text size cannot always be adjusted via the browser, which hampers readability. The date picker is difficult to navigate with a keyboard and unclear for screen reader users. For example, it departs from expected behavior with month selection where the list expands with the spacebar and selections are made with enter, and the status of the selected month is not read aloud.
Many input fields lack labels, making it difficult for screen reader users to understand their function. Focus often lands incorrectly when using pop-up windows, and checkboxes change automatically with tab navigation, which can lead to unintentional selections. The focus order is not always logical or predictable, and some interactive elements cannot be accessed with the keyboard, limiting usability. Focus indicators on input fields are often unclear, and headings do not follow a logical hierarchy, which can confuse users.
Information is sometimes conveyed only with color, which can be problematic for colorblind users.Subtitles often lack information about which company the page belongs to, and the website lacks support for dark mode, which can be straining on the eyes. The site sometimes has issues with pop-up windows, such as the close button not being visually visible. Additionally, error messages are often unclear, which can lead to misunderstandings.
Work is underway to update SkiStar's technical design system to ensure all components meet accessibility requirements. Estimated completion: December 2025.
Editorial work is underway to write alt-texts for all images in all languages. Estimated completion: August 2025
Images missing alt-text
Example: Images in heroes and advertisements.
WCAG 2.1, Guideline 1.1.1 (A)
Low contrast on graphical components
Example: White checkmark on blue background.
WCAG 2.1, Guideline 1.4.11 (AA)
Low contrast on focus indicator
Example: White focus indicator on "Secure your winter holiday today!".
WCAG 2.1, Guideline 1.4.11 (AA)
Unclear focus indicator on input fields
Example: Customer registration.
WCAG 2.1, Guideline 1.4.11 (AA)
Input fields missing label
Example: Booking flow skipass.
WCAG 2.1, Guideline 1.3.1 (A)
Illogical heading structure
Example: My customer details.
WCAG 2.1, Guideline 1.3.1 (A)
Color used as the sole means of conveying information
Example: Booking conditions.
WCAG 2.1, Guideline 1.4.1 (A)
Text cannot be modified to user needs
It is not possible to adjust the website's text size via the browser.
EN301549 - 11.7
Dark mode missing
The website lacks support for dark mode.
EN301549 - 11.7
Page titles are not descriptive
Titles lack information about which company the page belongs to.
WCAG 2.1, Guideline 2.4.2 (A)
Focus lands behind popup
Example: Login popup.
WCAG 2.1, Guideline 2.4.11 (AA)
Multiple issues with pop-up windows
Pop-up windows lack a visually visible close button.
WCAG 2.1, Guideline 2.1.1 (A)
Focus changes checkbox state
Example: Customer registration module.
WCAG 2.1, Guideline 2.1.1 (A)
Interactive elements do not receive keyboard focus
Example: Package offer.
WCAG 2.1, Guideline 2.1.1 (A)
Illogical focus order
Example: Accommodation booking flow.
WCAG 2.1, Guideline 2.4.3 (A)
Icons are read as images
Example: Shopping cart in the header.
WCAG 2.1, Guideline 4.1.2 (A)
Unclear error message when clicking "add to cart"
Error messages are not clear.
WCAG 2.1, Guideline 3.2.6 (A)
App accessibility
The most frequent issues in the Android app are that components lack available names and roles, images lack alt texts, visual headers are not coded as headers, and there are problems with color contrast and incorrect button names. In the iOS app, the most common problems are that text size settings are not respected, components lack accessibility roles, and some elements are unclear for screen reader users. Additionally, support for keyboard navigation is sometimes inadequate, the app does not work in landscape mode, and user settings for text size are not respected.
In the iOS app, the most common problems are that components lack available names and roles, there is low contrast on text in input fields, and some elements are unclear for screen reader users.
Components lack accessible names
Buttons and other interactive components lack accessible names.
WCAG 2.1, 4.1.2 (A)
Visual headings not coded as headings
Texts that visually appear as headings are not coded as headings.
WCAG 2.1, 1.3.1 (A)
Images missing alt-texts
Several images lack meaningful alternative texts.
WCAG 2.1, 1.1.1 (A)
Toggles lack accessible names
Not linked to their field with a label.
WCAG 2.1, 1.3.1 (A)
Incorrect name on back button
Reads aloud "Navigate up" instead of "Back".
WCAG 2.1, 4.1.2 (A)
Icons for lift status not conveyed to screen reader
Information-carrying icons for lift and capacity lack support.
WCAG 2.1, 1.1.1 (A)
Email field lacks autofill
WCAG 2.1, 1.3.5 (AA)
Difficult to enter PIN code field with screen reader
WCAG 2.1, 2.1.1 (A)
Components lack accessibility roles
Lack roles such as button or link.
WCAG 2.1, 4.1.2 (A)
Horizontal separators receive focus and are read as "nameless"
WCAG 2.1, 1.1.1 (A)
Background video cannot be paused, turned off, or hidden
WCAG 2.1, 2.2.2 (A)
Buttons for destinations lack roles and names
WCAG 2.1, 4.1.2 (A)
Error message about missing phone number not conveyed
WCAG 2.1, 4.1.3 (AA)
Multiple buttons use the same accessible name
WCAG 2.1, 4.1.2 (A)
Insufficient color contrast (e.g., right-chevron)
WCAG 2.1, 1.4.3 (AA)
Several buy and book buttons have hidden nameless images
WCAG 2.1, 1.1.1 (A)
Inconsistent or illogical focus order
Focus order does not match visual placement.
WCAG 2.1, 2.1.1 (A), 2.4.3 (A)
Focus on components in the background instead of bottom sheet
WCAG 2.1, 2.4.11 (AA)
Problems navigating or selecting dates in calendar
WCAG 2.1, 1.3.1 (A)
Error message for purchase terms not read aloud
WCAG 2.1, 1.3.1 (A)
Accommodation rating not read aloud
WCAG 2.1, 1.1.1 (A)
Screen reader users get stuck in onboarding
WCAG 2.1, 2.4.3 (A)
Screen reader users cannot become members or log in
WCAG 2.1, 4.1.2 (A)
Destinations are read unclearly or cannot be changed
WCAG 2.1, 1.3.1 (A), 4.1.2 (A)
Buttons on cards (weather, lifts, etc.) are unreachable
WCAG 2.1, 1.3.1 (A)
Tabs are read as plain text instead of interactive elements
WCAG 2.1, 1.3.1 (A)
Tables and relationships are unclear for screen readers
WCAG 2.1, 1.3.1 (A)
Buttons on cards are unclearly linked to content
WCAG 2.1, 2.4.4 (A)
Keyboard navigation support is insufficient
WCAG 2.1, 2.1.1 (A)
Landscape mode does not work
WCAG 2.1, 1.3.4 (AA)
No support for dark mode
EN301549 - 11.7
Text size is not always respected
WCAG 2.1, 1.4.4 (AA)
Information conveyed by color only
WCAG 2.1, 1.4.1 (A)
Incorrect semantics: lists, links as buttons
WCAG 2.1, 4.1.2 (A)
Input fields lack labels when placeholder disappears
WCAG 2.1, 2.4.6 (AA)
Email communication accessibility
Our emails have a number of common shortcomings and errors that affect accessibility. Support for user selection of light/dark mode is lacking, the text can be small and difficult to read, links are presented with the URL, and alt texts are missing on images. Additionally, visual headers are not coded as such, making it difficult for screen reader users to understand the structure of the emails. In some cases, input fields lack labels, focus lands behind pop-up windows, and checkboxes automatically change state during tab navigation.
Support for user selection of light/dark mode is missing
Legal requirement: EN 301 549: 11.7
Open in browser, small text
Legal requirement: Recommendation
Link presented with the link address
Legal requirement: 1.3.1 (A)
ALT-texts missing
Legal requirement: 1.1.1 (A)
Visual headings are not coded as such
Legal requirement: 1.3.1 (A), 2.4.6 (AA)
Visually hidden elements are read aloud
Legal requirement: 1.3.1 (A)
Content lacks language reference
Legal requirement: 3.1.1 (A)
Line breaks are presented as "empty"
Legal requirement: 1.3.1 (A)
Color as the only way to distinguish link
Legal requirement: 1.4.1 (A)
Content does not reflow with text enlargement
Legal requirement: 1.4.10 (AA)
ALT text does not describe the image
Legal requirement: 1.1.1 (A)
Text in image does not appear
Legal requirement: 1.4.5 (AA)
Text contrast is too low
Legal requirement: 1.4.11 (AA)
Link lacks accessible name
Legal requirement: 2.4.4 (A)
List not coded as a list
Legal requirement: 4.1.2 (A)
How we work with accessibility
We collaborate with Axess Lab as an external reviewer of accessibility on our websites, apps, and ICT (Information and Communication Technology). Our goal is to create the best user experience we can. To ensure you feel secure with us as a customer, we continuously learn about accessibility.
Reporting to the supervisory authority
The accessibility requirements according to the law are considered fulfilled, with the exception of known deficiencies listed in this accessibility statement.
How do I report accessibility issues?
First, please tell us about any problem that prevents you from accessing our services. We can then rectify the deficiencies and assist you further. Details are available at the top of the page or in this report form. If you are not satisfied with our response, you can report it to the supervisory authority.
Last updated: 18 June, 2025