Signicat Terms and Conditions

# Accessibility statement for Enterprise SK Mobiil-ID

Effective date: 12/03/2024
Last updated: 26/06/2025

Signicat is committed to ensuring that Signicat's Enterprise Mobiil-ID solution 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 SK Mobiil-ID:

  • 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.
  • Work directly with institutions and their users to understand problems and areas for improvement.
  • Conduct usability research with users with disabilities.
  • 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. Signicat is partially conformant with WCAG 2.1 level AA. Partially conformant means that some parts of the content do not fully conform to the accessibility standard.

# Other standards

# Compatibility with browsers and assistive technology

SK Mobile-ID 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.

# Technical specifications

Accessibility of SK Mobiil-ID 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 Signicat Enterprise SK Mobiil-ID, 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 SK Mobiil-ID:

  • 1.4.5 Images of Text / 1.1.1 Non-text Content: The footer content, including the missing "Powered by Signicat" text, is presented as images instead of using actual text. This is unnecessary since the same visual presentation can be achieved using text alone.
  • 1.4.10 Reflow: When scaling the content to 400%, the "Powered by Signicat" footer disappears, violating the reflow requirement for content at increased zoom levels.
  • 1.4.11 Non-text Contrast / 2.4.7 Focus Visible: The focus indicator for interactive elements has a contrast ratio that is too low, failing to meet the minimum requirement of 3:1 against adjacent colours. This affects its visibility, making it difficult for users to identify which element currently has focus, especially for keyboard-only users or those with low vision.
  • 1.4.11 Non-text Contrast: The borders of input fields have a contrast ratio of 1.49:1, which is below the WCAG minimum requirement of 3:1 for user interface components. This makes it difficult for users with low vision or colour vision deficiencies to identify the input fields, especially in low-contrast environments.
  • 2.4.6 Headings and Labels / 3.3.2 Labels or Instructions: The labels for input fields, such as "Phone number" and "Personal code," are not descriptive enough. For example, the label "Phone number" does not provide clear instructions that users should "Enter your phone number." The same issue applies to the "Personal code" field.
  • 3.3.1 Error Identification and 3.3.3 Error Suggestion: Error messages are displayed within the text field itself, which is not a recommended practice for accessibility and usability. Additionally, the error icon is not visible, further reducing the effectiveness of error communication. Users, especially those with cognitive disabilities or using screen readers, may have difficulty identifying and understanding errors.
  • 3.3.1 Error Identification / 1.4.1 Use of Color: The error message for the personal code input field cannot be read by assistive technologies as it relies solely on a red border and an icon within the text field to indicate the error. There is no accompanying text explanation to describe the error or guide the user on how to fix it.

# Assessment approach

Signicat assessed the accessibility of SK Mobiil-ID by the following approach:

  • Self-evaluation