Accessibilité de Finnair.com

Niveau de conformité

Bienvenue dans la déclaration d’accessibilité de Finnair.com. Nous cherchons à rendre nos services plus accessibles à tous et nous nous efforçons de les améliorer en permanence. La conception et le développement de nos nouvelles fonctionnalités reposent toujours sur l’accessibilité. Nous améliorons continuellement l’expérience numérique des utilisateurs et appliquons les normes d’accessibilité pertinentes. La déclaration d’accessibilité de Finnair.com est régulièrement mise à jour.

Cette déclaration expose la conformité de Finnair.com aux directives d’accessibilité au contenu Web (WCAG) qui définissent les exigences pour les concepteurs et les développeurs afin d’améliorer l’accessibilité pour les personnes handicapées. Finnair.com est en partie conforme et en passe de satisfaire aux exigences de conformité des WCAG 2.2 Niveau AA. Le terme « en partie conforme » signifie que certaines sections du contenu, par exemple les contrastes de couleurs et les messages d’erreur, ne sont pas entièrement conformes aux normes d’accessibilité. Certaines pages ne sont pas entièrement compatibles avec les technologies d’assistance telles que les lecteurs d’écran. Les commentaires sur cette évaluation sont les bienvenus.

La dernière déclaration d’accessibilité a été mise à jour le 23/10/2022. L’accessibilité de Finnair.com a été vérifiée par une organisation externe.

Contenu non accessible

Le contenu indiqué ci-dessous n’est pas accessible pour les raisons indiquées : Non-respect de la loi sur la prestation de services numériques 306/2019 (en finnois).

Les fonctionnalités ou le contenu suivants (en anglais) ne répondent pas encore aux exigences des WCAG 2.2 AA :

General findings

3.1.1 Pages have undefined language
2.4.2 Page titles missing
4.1.3 Form errors, validation messages and status messages are not announced by the screen reader

Front page

1.1.1 Screen reader only announces the price in the destination ticket without announcing the travel class for that price
1.4.10 Chat and Feedback buttons disappear in mobile size
4.1.2 Destinations cards use <span> element without role, so aria labels might not work correctly

Log in

1.3.1, 4.1.2 Country code dropdown element does not have an accessible name
1.4.3 Login form fields and a checkbox have insufficient colour contrast
4.1.3 Form errors are not announced to screen reader

Booking

1.1.1 Review your purchase and Terms and conditions: Decorative SVG images focused and announced as 'blank' , the icons are marked up as "icon"
1.1.1 Entire contents of radio button not announced in the Flight selection 
1.1.1 Terms and conditions: Links opening in new window not announced 
1.1.1 Check prices and select dates modal: Only the price of each selection in the table is announced to a screen reader. Context and dates are not in understandable format
1.3.1 Check prices and select dates modal: Table header is empty, it does not have text visible to screen readers
1.3.1, 1.3.5 Element act as the link is implemented as a button without a descriptive label
1.4.1 State of booking steps is only indicated using colour
1.4.4 Terms and conditions: With 200% text resizing, the modal is stretched outside the window and it is not scrollable. User is not able to proceed.
2.1.1 Select travel dates: calendar cannot be focused with a keyboard. Users are able to set the date only with the date fields
2.1.1, 2.4.7. Trip type modal: Options do not get visible focus. Selection cannot be made with a keyboard
2.4.3 Modals in the booking flow do not capture focus
2.4.4 Terms and conditions: The link does not announce it leads to another webpage. It is only marked by the icon
2.4.7 Direct flights only does not get visible focus
2.4.7 Passenger details: Focus indication is time-limited
3.3.2, 4.1.2 Enter passenger details: Required fields are not announced as such
3.3.2 Select flights: Ticket type selections are not marked up as an interactive element (button or link). Screen reader user with mobile does not know that they are interactive.
3.3.2, 4.1.2 Enter passenger details: Required fields are not announced as such
4.1.2 Disabled Book now button announced without state 
4.1.2 Date picker invisible elements focused and announced
4.1.2 Select flights: Selected ticket is not announced to screen reader
4.1.3 Enter passenger details: Error messages for the form fields are not announced
4.1.3 Error, status and validation error messages are not announced

Manage booking

1.3.1 Sidebar navigation list and the list on the Add baggage page are not of correct HTML structure
1.3.1 Customise your trip: Add extra bags  dialogue title is not announced
1.3.3 Disruption: Strikethrough text on review flight detail page is not announced with screen reader
1.4.3 Insufficient colour contrast in the text fields
1.3.3 Details page: Passenger amount, Adding baggage and Booking reference are only explained as icons
1.3.3 Disruptions: strikethrough text is not announced by screen reader
1.4.3 Passenger details page: First name and Family name input labels have insufficient contrast
1.4.11, 2.4.11 Purchase button contrast is insufficient in relation to background, so focus state is not sufficient
1.4.11 Bathroom placement in the seat map has insufficient colour contrast
2.1., 2.4.3 Notification banner is not keyboard accessible
2.4.2 Navigating from the notification banner to the Change your trip page doesn't announce the page changing
2.4.3 Add travel extras button has an anchor link that does not work with a screen reader. The focus visually changes to the Travel extras section, but screen reader focus stays in the same place
2.4.3 Change booking: Which flights do you want to change modal does not capture keyboard focus
2.4.4 Safe travel link only says “Opens in a new tab” instead of the real link text as aria-label is used. Same with other links with external links, such as pdf link
2.4.7 Adding bicycle or pets buttons are missing focus styles
3.1.1 Page has undefined language (Manage, Cancel, Change)
4.1.1 Add baggage page: aria-labelled by pointing to non-existing element
4.1.2 Emergency contact details: Submit button does not announce the passive/disabled/not in use state to the screen reader users
4.1.2 Icons are missing a role
4.1.2 Change flights: Which flights you want to change modal: Both button states (selected/not selected) are announced "Select this flight to change" to the screen reader. Screen reader user does not know when the selection has been made
4.1.3 Error, status and validation error messages are not announced

Chat

1.4.3 Placeholder texts and "* Mandatory fields" instruction text on the contact information fields have insufficient colour contrast
2.4.7 Focus indication in the chat window is time-limited
2.4.11 Focus indicator on the buttons does not fulfil the requirements
3.3.1 Form errors are not indicated in text
3.3.2 Booking reference field is missing a label
4.1.2 Chat button on Contact Finnair Corporate Programme has no discernible name in mobile size
4.1.2 Submit button at the end of the form is invisible to screen reader user until it becomes not disabled
4.1.3 Error, status and validation error messages are not announced

Payments

1.1.1 Select payment method: Informative images and radio buttons not announced 
1.1.1 Pay with points view: Info icon does not have accessible name
1.3.1, 4.1.2 Payment card country selection dropdown does not have an accessible name
1.4.3, 1.4.11 Insufficient colour contrasts: Gift card number and PIN code placeholder texts and text fields, Proceed button in active state, Credit card - Select buttons for Personal and Corporate, style unselected and Select payment method: text fields
2.4.4 Booking confirmation: The button Offset flight does not tell it directs to another page and opens the content in a new tab
2.4.7 Select payment method focus indication is time-limited
2.4.11 Pay with points and Select payment method views: Focus indicator appearance does not fulfill the requirements in the Proceed and Pay now buttons
3.3.2 Select payment method: Required fields are not visually marked as such 
3.3.2 Select payment method: Interactive elements to select are not marked up correctly. Screen reader reads them as headings
3.3.2 Pay with points: The input of the slider is incomprehensible to the screen reader. It announces the amount of used points without the euro amount. It does not have any description of the amount, just the number
4.1.2 Select payment method: Widget 'Credit or debit card' announced without role
4.1.2 Select payment method: Checked radio button announced as not checked
4.1.2 Payment card country selection dropdown does not have an accessible name
4.1.2 Select payment method: Selected payment option is not announced
4.1.2 Select payment method: When payment method is disabled, it does not announce the state to a screen reader

Third-party payment operators:

1.1.1 Trustly, Select your bank: Bank icons are missing accessible text
1.1.1 Trustly, Something went wrong: Closing button is missing an accessible name
1.3.1 Trustly, Select your bank view: Search field is missing a label
1.3.1 Trustly, Select your bank view: List has direct children elements that are not of allowed format, they are <div> elements
1.4.3 Trustly, Select your bank: in the Trustly iFrame, "Search for your bank" placeholder text has insufficient colour contrast
2.1.1 Trustly, Select bank view: The bank selections in the Trustly iFrame cannot be focused by using tab on keyboard or with a screen reader
2.1.1 Trustly, Change language modal: The language selections do not get focus by keyboard or by screen reader
2.4.3 Trustly: modals do not capture focus
4.1.2 Trustly, Select your bank view: Search field is missing a label
4.1.2 Trustly, Select your bank view: Trustly application is working in iFrame. IFrame is missing an accessible name

Feedback forms/Special assistance form

1.3.1 User is not informed about the maximum of allowed characters for additional information field 
1.3.1 Day names are announced as abbreviations 
1.4.4 Text resizing has been prevented on the page by using "!important" attribute
2.4.2 Page is missing a title
2.4.11 In the form text fields focus appearance does not fulfil requirements
3.3.2 On the date field, the format is not clearly described to the screen reader user. It says only "DDMMYYYY", without the points in between
3.3.2 Radio button groups in the form do not announce the title of the group to the screen reader. The input instruction is not sufficient
4.1.2 Submit button in the form is invisible to screen reader users until it becomes not disabled
4.1.2 Radio buttons in the form use unallowed aria role
4.1.3. Form errors and status messages are not announced by a screen reader

Content pages

New cabin: 4.1.2 Destination cards are missing a role
New cabin: Chat button is missing a discernible name in mobile size
1.4.3 Finnish national parks: Social media sharing links have insufficient colour contrast
2.4.4, 4.1.2 Finnish national parks:  Social media sharing links miss discernible text

Travel requirements map

1.1.1 Travel info modal: Images do not have alternative text
1.1.1 Requirements map component does not have alternative text
1.3.1 Combobox elements are missing expected children roles
1.4.3 Insufficient colour contrasts: disclaimer text, placeholder texts on the form fields, "Here's where you can travel", "No test" and "No quarantine" buttons, full list of destinations: green text on "Open to travel", full list of destinations: yellow text on "Test to travel", Travel info modal: Connection and Country field placeholder texts and Destination cards label text "Open to travel"
1.4.4 Text resizing has been prevented on the page by using "!important" attribute
1.4.10 Page content hides content in Cookie consent banner, when scrolled downwards. Requirements map and other elements on the form overlap Chat button in the mobile size
3.1.1 Language of the page is not defined
4.1.2 There is a typing error in two of the "aria-labelled by" attributes
4.1.2 Comboboxes are missing a role
4.1.3 Error messages in the form fields are not announced to screen reader without user navigating to them

Contact Finnair Corporate Programme

1.4.3 Placeholder texts have insufficient colour contrast
1.4.11 Text fields have insufficient colour contrast
4.1.2 Radio button labels use aria attributes that are not allowed
4.1.2 Chat button does not have discernible name in the mobile size
4.1.2 Submit button in the form is invisible to screen reader users until it becomes not disabled
4.1.3 Form errors are not announced by a screen reader

Timetables

1.3.1, 4.1.2 Table showing the flight information has not discernible text in table header or visible content to screen readers
2.1.1 Modal content wrapper in Flight overview is not accessible by keyboard
2.4.3 Flight overview modal does not capture focus. User is able to navigate to the underlying content with a keyboard
2.4.3 Screen reader user is not able to open Flight overview modal
4.1.2 Chat button does not have discernible name in the mobile size

Destinations

1.1.1 Screen reader only announces the price in destination ticket without announcing the ticket class for that price
1.3.1, 3.3.2, 4.1.2 Sort by element does not have accessible name
1.3.1, 4.1.2 Combobox element Type or select destinations is missing a label
1.3.1, 4.1.2 Next button is marked aria-hidden, but still listed as a focusable element
2.4.3 In the mobile with Safari and Voiceover, in the calendar component each day of each month gets focus, even though you have a certain month opened
2.1.1, 3.3.2, 4.1.2 Tab selection (Round-trip prices and One-way prices) does not get a keyboard focus when navigated with a keyboard
4.1.2 Destination cards are missing aria role value

Cookie consent banner

1.4.11 Toggle elements have insufficient colour contrast
2.4.7 Toggle elements do not get visual focus

Check-in

1.3.1 Info and Relationships: In the Check-in web view, after the Identification title, a screen reader says "Help lane equals..." etc. This information should not be read by a screen reader
1.3.2 Meaningful sequence: Check-in button is the last item in the Flight information view for a screen reader. In the UI logic, it is after Title and Terminal information
The seat map is totally empty to screen reader users with no information or instructions. When a user closes the seat selection view, the application returns to the Flight information, not the previous view
2.4.2 Page titled: Check-in view has no name or title that a screen reader is able to read when a user arrives at the view
3.3.2 Labels or Instructions: Check-in button has no label. A screen reader says "Unlabelled". A user is not able to understand the function where to start check-in
In the Check-in view, the close button is missing a label. A screen reader says "Unlabelled button"
4.1.2 Name, Role, Title: The seat map modal is missing a title

A continuous effort will be made to rectify these problems.