Skip to main content

Accessibility statement — My F‑Secure

F‑Secure is committed to making its e‑commerce services accessible, in accordance with the European Accessibility Act (EU 2019/882). Our commitment to accessibility is part of our broader mission to make the digital world safer and more inclusive for all.

This accessibility statement applies to My F‑Secure portal, which allows F‑Secure end users to manage their licenses and subscriptions.

Accessibility status

This website partly fulfils the requirements of the European Accessibility Act (EU 2019/882). Please see below for a list of non-conformities and exceptions applicable to the criteria.

Non-accessible content

  • The content discussed below is non-accessible for the specified reasons: Non-compliance with the European Accessibility Act (EU 2019/882). The following content and/or functionalities do not yet meet the requirements:

  • The keyboard and screen reader focus goes inside the Menu and F‑Secure help menu without the user activating the menu (2.1.1).

  • When the focus is on the online manuals inside the F‑Secure help, it’s fully obscured if the menu has not been opened (2.4.11 – WCAG 2.2).

  • The language menu is not accessible by keyboard. The keyboard focus is not taken to the menu overlay (2.4.3).

  • Keyboard focus is not always automatically taken to the dialogues and not kept inside of the dialogues. In most cases the dialogues can be accessed by navigating at the end of the page first (2.4.3).

  • The keyboard focus is not visible on any interactive element in the most parts of the portal. Focus is visible in account related content (2.4.7).

  • Many elements don’t have correctly defined name and role (4.1.2).

  • Subscription information is presented in data table format without correctly marking the header cells (1.3.1).

  • Some non-heading content has been marked as headings and some heading levels have been skipped (1.3.1).

  • Some input labels are not programmatically associated with the input elements (1.3.1).

  • There is no visible error feedback for the subscription code input field (3.3.1, 1.4.1).

  • The error messages are not programmatically associated to the input element and the input fields with error have not been marked as invalid (3.3.1).

  • The color contrast for some text content is too low (1.4.3).

  • The color contrast for some interactive components is too low (1.4.11).

  • The language of the language labels in the language menu has not been defined (3.1.2).

  • The information text about reviewing the subscription code, doesn’t fully fit in the view when the screen width is reduced to 320px or screen content increased by 400%. However, the subscription code is fully visible (1.4.10).

  • When text is resized to 200%, some link and button text are hard to read (1.4.4).

  • There is time limit on the page. In some cases, it might not be possible to extend the time limit (2.2.1).

Login, Create new account, Account settings

  • The iframes don’t have an accurate and descriptive title (2.4.1, 2.4.2).

  • The text input fields in the login and create account forms are not visually identifiable and don’t have any visual label (1.4.11, 3.3.2).

  • Input fields that are collecting user information don’t have autocomplete attributes to identify the information type (1.3.5).

  • There is a tooltip that works on hover in the password field in create an account form. The tooltip is not accessible with touch, keyboard or screen reader, doesn’t have any accessible name or role and cannot be closed with esc (1.1.1, 1.4.13, 2.1.1, 4.1.2).

    • The text in the tooltip: The password must have at least eight characters with at least one number and one lowercase or uppercase letter.

  • The input field for entering the two factor code has a visible label that is not included in the programmatically defined label (2.5.3).

  • The color contrast for some text content is too low (1.4.3).

  • The text content inside iframes cannot be resized and it doesn’t adapt to text spacing changes (1.4.4, 1.4.12).

  • The table of trusted devices doesn’t fully fit when the screen width is reduced to 320px or screen content increased by 400%. The content cannot be horizontally scrolled to the left and some part of the informative text and the device name are not readable (1.4.10).

The following content cannot be fixed and will be at end of life at the end of 2025

The following non-conformities apply to the main content area of the portal after the user has logged in. In this area the user can add new users and devices to their subscription. Similar problems are present also in the ID monitoring page which is out of scope of the applicable legislation. This service is at the end of it’s life and cannot be improved. The functionality is planned to be offered in an other way in 2026.

  • None of the interactive elements in the devices view is keyboard accessible, however the elements are accessible with screen readers (2.1.1).

  • Most elements in the dialogues that can be opened from the devices view are not keyboard accessible, but are accessible with screen readers (2.1.1).

  • The keyboard focus is not visible for most of the elements that receive keyboard focus (2.4.7).

  • The keyboard focus is not automatically taken to the dialog. The focus usually remains behind the dialogue (2.4.3).

  • The reading order is not always logical. The close buttons in the dialogues are not accessible with screen readers as they have been hidden from screen readers (1.3.2).

  • All images are missing text alternatives (1.1.1).

  • Many of the interactive components are missing a correct role. For example, the device options are not marked as radio buttons (4.1.2).

  • The state of the selected device options has not been marked programmatically (4.1.2).

  • The text content inside iframes cannot be resized and it doesn’t adapt to text spacing changes (1.4.4, 1.4.12).

  • The input labels are not programmatically associated to the input elements (1.3.1).

  • The color contrast for some text content is too low (1.4.3).

  • The color contrast for some interactive components is too low (1.4.11).

  • Input fields that are collecting user information don’t have autocomplete attributes to identify the information type (1.3.5).

  • Iframes don’t have titles and the iframe source pages don’t have descriptive titles (2.4.1, 2.4.2).

  • There is time limit on the page. In some cases, it might not be possible to extend the time limit (2.2.1).

Certain content is excluded from the applicable legislation

The ID monitoring section of the portal is not within the scope of the applicable legislation. ID monitoring section is part of the offered security product and not part of the e‑commerce service and the subscription related to it.

Preparation of this accessibility statement

This statement was prepared on 7 March 2025. The statement is based on a third-party assessment. The statement was last reviewed on 26 May 2025.

Other service alternatives

If you are unable to use the My F‑Secure portal and can’t for example download the application you can contact us by email at accessibility.feedback@f-secure.com or through our other support channels.

Feedback

We are happy to receive feedback on the accessibility of the f-secure.com website.