# Accessibility statement for Sign API v2
Effective date: 11/11/2025
Last updated: 01/10/2026
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
Signicat takes the following measures to ensure 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.
- 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. Sign API v2 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 Sign API v2 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.
# 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.
- The latest versions of TalkBack (Android) and VoiceOver (iOS).
- Keyboard navigation for physical keyboard users.
# Technical specifications
Accessibility of Sign API v2 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. Please contact us if you observe an issue not listed below.
Known limitations for Signicat Sign API v2:
- WCAG 2.2 Success Criterion 4.1.2 – Name, Role, Value: The language toggle does not have an accessible name. On mobile devices, the "More action" overlay causes hidden content to be announced.
- WCAG 2.2 SC 1.3.1 – Info and Relationships: The "Review" and "Sign" headings are not programmatically identified as headings.
- WCAG 2.2 Success Criterion 1.3.4 – Orientation: When the device is used in landscape orientation, the "Reject signing" overlay does not allow the user to scroll through its content.
- WCAG 2.2 Success Criterion 2.1.1 – Keyboard: On mobile devices, some content cannot be reached using keyboard focus. In Safari, certain interactive elements cannot be reached using keyboard focus.
# 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