Signicat Terms and Conditions

# Accessibility statement for Sign API v2

Effective date: 11/11/2025
Last updated: 11/11/2025

Signicat is committed to ensuring that our Sign API v2 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

  • 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) 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. Signicat 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

  • EN 301 549 Accessibility requirements suitable for public procurement of ICT products and services in Europe

# Feedback

We welcome your feedback on the accessibility of Signicat 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.

# Compatibility with browsers and assistive technology

Sign API v2 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 Signicat 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 and alternatives

Despite our best efforts to ensure accessibility of Sign API v2, there may be some limitations. Below is a description of known limitations.

We are committed to fixing any accessibility limitations on a continuous basis as part of our ongoing development. Please contact us if you observe an issue not listed below.

# 'Sign documents' page

  1. 1.1.1 Non-text Content (opens new window)
  2. 1.3.1 Info and Relationships (opens new window)
  3. 1.3.2 Meaningful Sequence (opens new window)
  4. 2.4.1 Bypass Blocks (opens new window)
  5. 1.4.4 Resize Text (opens new window) and 1.4.10 Reflow (opens new window)

# 'Select identity provider' page

  1. 1.1.1 Non-text Content (opens new window)
  2. 1.3.1 Info and Relationships (opens new window)
  3. 1.3.2 Meaningful Sequence (opens new window)
  4. 1.3.4 Orientation (opens new window) and 2.5.1 Pointer Gestures (opens new window)
  5. 1.4.4 Resize Text (opens new window), 1.4.10 Reflow (opens new window) and 1.4.11 Non-text Contrast (opens new window)
  6. 2.4.11 Focus Visible (opens new window)
  7. 3.3.1 Error Identification (opens new window) and 3.3.3 Error Suggestion (opens new window)
  8. 4.1.2 Name, Role, Value (opens new window)

# Assessment approach

Signicat has assessed the accessibility of its Sign API v2 solution through self-evaluation, using the following methods:

  • Axe Accessibility Testing Tools
  • WAVE Web Accessibility Evaluation Tool
  • Google Lighthouse