This Accessibility Statement explains how SalesSign works towards WCAG 2.1 AA and how to report barriers. We want everyone to be able to build, send, track and eSign proposals with SalesSign. This statement explains the accessibility standard we work to, what it covers, the issues we know about, and how to tell us when something gets in your way.
Last updated: 3 June 2026
SalesSign is committed to making our products and information accessible to as many people as possible, including people who use assistive technologies such as screen readers, screen magnifiers, speech recognition software and keyboard-only navigation. We treat accessibility as an ongoing responsibility rather than a one-off project, and we work to improve it as our website and application evolve.
We aim to conform to the Web Content Accessibility Guidelines (WCAG) 2.1 at Level AA. These guidelines, published by the World Wide Web Consortium (W3C), explain how to make digital content more accessible to people with a wide range of disabilities. Level AA is the standard most commonly referenced in procurement, regulation and contractual requirements.
Conformance with WCAG is measured on a sliding scale. Our target is full conformance, meaning the relevant content fully meets the standard without exceptions. Where we fall short of that target today, we describe the known gaps in the “Known limitations” section below and treat closing them as planned work.
This statement applies to:
Because SalesSign is a Salesforce-native application, parts of the experience are rendered using the Salesforce platform and its standard user-interface components. The accessibility of those underlying platform components is determined by Salesforce. Our commitment covers the parts of the experience we design and control; where a barrier originates in the underlying platform, we will say so and, where practical, raise it with the platform vendor and offer a workaround.
We consider accessibility when we design and develop new features, including semantic structure, colour contrast, focus order and keyboard operability.
We use a combination of automated checks and manual review, including testing with assistive technologies, to find and prioritise accessibility issues.
We invite reports of accessibility barriers from users and reviewers, log them, and use them to drive fixes and future improvements.
Despite our efforts, some parts of our website and application may not yet be fully accessible. We are transparent about the issues we are aware of so that you can plan around them and so that reviewers can assess our current position accurately. Known limitations currently include:
we are not aware of any material accessibility barriers at this time; if you encounter one, please tell us and we will put it right
If you encounter a barrier that is not listed here, please tell us using the details below. Reporting issues helps us keep this section accurate and helps us prioritise.
If you cannot access part of our website or application, or you find content that is difficult to use with assistive technology, we want to hear about it. When you contact us, it helps to include:
You can report a barrier to: admin@salessign.io.
A Voluntary Product Accessibility Template (VPAT) describing how SalesSign measures against accessibility standards such as WCAG 2.1 and Section 508 is available to customers and prospective customers on request. Procurement, security and legal reviewers can request the current VPAT, along with any supporting conformance information, using the accessibility contact above.
We monitor the accessibility laws and standards that apply to our customers and to us, and we factor them into how we design and assess our products. In particular, we are aware of:
This statement is provided for transparency. It is not legal advice, and it does not by itself create or limit any rights or obligations under these or other laws. Where a specific contractual or regulatory accessibility requirement applies to your organisation, please raise it with us using the accessibility contact above so we can address it directly.
This statement was prepared on 3 June 2026 and last reviewed on 3 June 2026. It is based on a self-assessment carried out by our team. We review this statement regularly and update it as our website and application change and as we close known issues.