Signicat Terms and Conditions

# Accessibility statement for Finnish eIDs (FTN)

Effective date: 06/01/2024
Last updated: 24/08/2026

Signicat is committed to ensuring that our FTN broker service is accessible to all users, including those with disabilities. Our goal is to make our content as accessible as possible for all users. We are continually improving the user experience for everyone and applying the relevant accessibility standards. Accessibility is a fundamental aspect of our product development and delivery strategies. We aim to provide an inclusive and positive experience for everyone.

# Measures to support accessibility

Signicat takes the following measures to ensure the accessibility of FTN:

  • Include accessibility as part of our mission statement.
  • Incorporate accessibility throughout our internal policies.
  • Integrate accessibility into our procurement practices.
  • Appoint an accessibility coordinator.
  • Provide continual accessibility training for our staff.
  • Assign clear accessibility goals and responsibilities.
  • Employ formal accessibility quality assurance methods.
  • Partner with various organisations for support, training, and research.

# Conformance status

The Web Content Accessibility Guidelines (WCAG) (opens new window) defines requirements for designers and developers to improve accessibility for people with disabilities. It defines three levels of conformance: Level A, Level AA, and Level AAA. FTN is partially conformant with WCAG 2.2 level AA. Partially conformant means that some parts of the content do not fully conform to the accessibility standard.

# Other standards

FTN partially complies with EN 301 549, the accessibility standard for ICT products and services used in public procurement in Europe. See EN 301 549 Accessibility standard for ICT products and services used in public procurement in Europe (opens new window) for details.

# Feedback

We welcome your feedback on the accessibility of FTN for all users, including those with disabilities and those who use assistive technology. Please let us know if you encounter any accessibility barriers or have any questions or concerns by contacting us through the feedback widget below. We try to respond to feedback within 5 business days.

# Compatibility with browsers and assistive technology

FTN is designed to be compatible with the following assistive technologies:

  • The latest version of Microsoft Edge, Google Chrome, Mozilla Firefox and Apple Safari browsers.
  • The latest versions of NVDA and VoiceOver.
  • The latest versions of TalkBack (Android) and VoiceOver (iOS).

# Technical specifications

Accessibility of FTN relies on the following technologies to work with the particular combination of web browser and any assistive technologies or plugins installed on your computer:

  • HTML
  • CSS
  • JavaScript

These technologies are relied upon for conformance with the accessibility standards used.

# Limitations

Despite our best efforts to ensure accessibility of FTN, there may be some limitations. Below is a description of known limitations. Please contact us if you observe an issue not listed below.

Known limitations for FTN:

  • WCAG 2.2 Criterion 4.1.2 Name, Role, Value: The "Cancel" control is implemented as a link rather than a button. As a result, assistive technologies may announce it as a link, even though activating it performs an action. The control should be implemented as a button so that its role and expected behaviour are correctly communicated to assistive technologies.
  • WCAG 2.2 Criterion 1.4.4 Resize Text: Text in the application does not respond to the platform's text-scaling settings on Android or iOS. Increasing the system font size, including Large Font on Android and Dynamic Type on iOS, does not increase the size of the text within the application. This prevents users who require larger text from increasing the text size to make the content easier to read. The application should support the platform's text-scaling functionality and ensure that increasing text size does not result in a loss of content or functionality.
  • WCAG 2.2 Criterion 1.3.1 Info and Relationships: The group of buttons is not announced as a list by screen readers. As a result, screen reader users do not receive the same structural information about the group of buttons that is available visually. The relationship between the buttons should be programmatically exposed so that screen readers can communicate the list structure and its items to users.
  • WCAG 2.2 Criterion 2.1.1 Keyboard: The application does not support navigation and interaction using an external keyboard on iOS and Android. This may prevent users who rely on an external keyboard from accessing or operating interactive elements. All functionality should be operable using a keyboard interface, in accordance with the platform's supported keyboard interaction mechanisms.

# Assessment approach

Signicat assessed the accessibility of FTN by the following approach:

  • Self-evaluation