# Accessibility statement for Signicat developer documentation
Effective date: 13/08/2026
Last updated: 13/08/2026
Everyone should have an equal opportunity to use Signicat's developer documentation. 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.
Page contents
# Signicat developer documentation
Signicat's developer documentation provides software developers, architects and integration specialists with comprehensive guides, API references and SDKs to implement digital identity, verification and electronic signing solutions. The developer documentation is designed to streamline the integration workflow, helping teams quickly find the resources they need to build secure and compliant identity journeys.
For technical resources, API reference guides and integration assistance, visit the Signicat Developer documentation (opens new window).
# Measures to support accessibility
Signicat takes the following measures to ensure accessibility of Signicat's developer documentation:
- 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.
# 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's developer documentation 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.
# Feedback
We welcome your feedback on the accessibility of Signicat's developer documentation. Please let us know if you encounter accessibility barriers on Signicat's developer documentation:
E-mail: accessibility@signicat.com
We try to respond to feedback within 2 business days.
# Technical specifications
Accessibility of Signicat's developer documentation 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
- WAI-ARIA
- 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 Signicat's developer documentation, 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's developer documentation:
- Screen reader support is currently being improved across the developer documentation. While many interactions are accessible, users who rely on screen readers may encounter areas where information, status changes or interface elements are not communicated as clearly as intended. This may occasionally lead to confusion or make certain tasks more difficult to complete.
# Assessment method
This accessibility statement is based on a self-evaluation of Signicat's developer documentation.