Signicat Terms and Conditions

# Accessibility statement for ReadID

Effective date: 20/04/2026
Last updated: 20/04/2026

Signicat is committed to ensuring that ReadID 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.

Page contents

# Measures to support accessibility

Signicat takes the following measures to ensure accessibility of Signicat:

  • Include accessibility as part of our mission statement.
  • Include accessibility throughout our internal policies.
  • Integrate accessibility into our procurement practices.
  • Appoint an accessibility officer and/or ombudsperson.
  • Provide continual accessibility training for our staff.
  • Assign clear accessibility goals and responsibilities.
  • Employ formal accessibility quality assurance methods.

# Compliance status

The Web Content Accessibility Guidelines (WCAG) (opens new window) define 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. ReadID is fully compliant with WCAG 2.2. level AA.

# Other standards

ReadID complies with EN 301 549, the accessibility standard for ICT products and services used in public procurement in Europe.

# Feedback

We welcome feedback on the accessibility of ReadID from 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 five business days.

# Compatibility with assistive technology

ReadID is designed to be compatible with the following assistive technologies, including but not limited to:

  • The latest versions of TalkBack (Android) and VoiceOver (iOS)
  • Support for Dynamic Type (iOS) and Large Font Sizes (Android)
  • Keyboard navigation for physical keyboard users

# Limitations and alternatives

Despite our best efforts to ensure accessibility of ReadID, there may be some limitations. These limitations are primarily due to constraints within the operating systems. Below is a description of known limitations specific to the ReadID product and platform.

Note that ReadID UI SDK is part of ReadID Ready app. Please contact us if you observe an issue not listed below.

# ReadID UI SDK

  • VIZ Capture: Currently supports only landscape mode due to technical limitations. This means the content does not fully comply with WCAG 2.2 - 1.3.4: Orientation. This limitation is considered an exception as supporting both orientations is not feasible in this context.
  • iOS NFC action sheet: in iOS 15, the textual instruction remains default size when Dynamic Type is used. WCAG 2.2 - 1.4.4: Resize Text.
  • iOS 15 NFC action Sheet: Text in the NFC action sheet remains at the default size due to system-provided iOS UI behavior. As a result, it does not fully meet WCAG 2.2 - 1.4.4: Resize Text.

# ReadID Ready app

  • Android "I don't have a QR code" bottom sheet may not always be fully accessible with TalkBack. This is likely due to limitations in Compose. WCAG 2.2 - Success Criterion 4.1.2: Name, Role, Value.
  • iOS Scan QR screen: The torch button label does not scale fully when Dynamic Type is used. WCAG 2.2 – Success Criterion 1.4.4: Resize Text.
  • iOS Result screen: Segmented control button labels do not scale automatically. Users can view scaled text via long-press, which is native iOS behavior. WCAG 2.2 - Success Criterion 1.4.4: Resize Text.
  • Android Verify your identity screen: Cancel the session dialog text is cut off when large font size is used. It is a custom component which does not have much flexibility. WCAG 2.2 – Success Criterion 1.4.4: Resize Text.
  • iOS Result screen: segmented control button not navigable with keyboard. WCAG 2.2 – Success Criterion 2.1.1: Keyboard.

# Assessment approach

Signicat assessed the accessibility of ReadID by the following approaches:

  • Accessibility snapshot testing
  • Self-evaluation
  • External auditing