Accessibility statement, version acc-2

. The statement

Sovrasign Accessibility Statement. Version acc-2, effective 10 November 2026.

In short: we want everyone to be able to sign and send documents with Sovrasign, including people who use a screen reader, a keyboard, magnification or voice control. Our target is the Web Content Accessibility Guidelines (WCAG) 2.2 at Level AA. This statement says where we stand, what does not work well yet, and how to tell us about a barrier. A person answers within 5 business days.

1. What this statement covers

1.1 Our services. The signing page (where people sign documents sent to them), the verifier, the web app for senders, our websites and help center, our emails, and our desktop and mobile apps.

1.2 The standards. We aim to conform to WCAG 2.2 Level AA and to the European standard EN 301 549 (version 3.2.1), which incorporates WCAG 2.1 and adds requirements of its own. We use the European Accessibility Act's requirements for services, and Section 508 for US public buyers, as our design targets. As a microenterprise we fall within the Act's service exemption today. This statement does not claim full compliance with either.

2. How accessible our services are today

2.1 Status per service.

"Fully conformant" means the content meets the standard without exceptions. "Partially conformant" means some parts do not, or that our evaluation is not finished yet; the table says which. Known limitations are in section 3.

2.2 How we built it. Signing never requires drawing: typing your name or a single button are equal choices, and your signature comes from confirming who you are, not from a drawing. Every field on the signing page is a real, labelled form control, in reading order, and you can complete the whole signing flow with a keyboard. Sign-in codes can be pasted and filled in by your device. We use no puzzles or image tests to tell people from robots. Pages follow your browser's zoom, text size and reduced-motion setting.

3. What does not work well yet

3.1 Known limitations.

• Reading the document. On the signing page, the document is shown as page images with your fields placed on them. The signing page has a "Fill in as a form" view that lists every field as a form with each page's text, but how well you can read the document itself depends on the PDF the sender uploaded. Alternative: ask the sender for an accessible copy or another way to sign, or write to us (section 5).
• Signed PDFs. We keep the structure of the PDF the sender uploaded, and the fields and signatures we add carry text descriptions. We do not yet produce fully tagged, accessible PDFs (PDF/UA).
• Screen readers. We have not yet finished testing with screen readers (NVDA, JAWS, VoiceOver, TalkBack); our automated checks and our keyboard review found no barrier left. If something is not announced well, tell us (section 5).
• Desktop and mobile apps. Not yet evaluated.

3.2 Pages of other companies. Some steps happen on other companies' pages, under their own accessibility commitments: signing in with Google, Microsoft or Apple, and paying with Stripe. If you cannot use one of those pages, tell us (section 5) and we will help you find another way.

4. How we test

Our last evaluation was on 31 October 2026: our own review, with automated checks (axe-core on every page and screen, in light and dark themes, with the text at 200 %, at 320 pixels wide, with increased text spacing and with Windows high contrast) and a review with the keyboard only. It found twelve barriers, which we fixed. A review with screen readers and an audit by an independent firm are planned. Automated accessibility checks run on every change to our pages before it is released, and we test new features by hand. We update this statement whenever a release changes how accessible a service is.

5. Tell us about a barrier

5.1 Contact. Write to support@sovrasign.com (there is no separate form yet). Tell us which page or step, what you tried, and the assistive technology you use if you like. A person answers, not our AI assistant, within 5 business days.

5.2 What we do. We help you complete what you were trying to do, for example by finding another way to sign with the sender. We aim to fix barriers in our own service that block a task within 30 days, and we offer you another way to do the task meanwhile. We cannot fix a sender's document or another provider's page, but we help you find an alternative.

5.3 Other formats. You can ask for this statement, our legal texts or the e-sign disclosure in another format, such as plain text or large print.

5.4 If you are not satisfied. In the EU, you can contact the authority that enforces the European Accessibility Act in your country (its market surveillance authority); we add a link to the list of these authorities before EU sign-ups open. Elsewhere, you can use the procedures your country's accessibility laws provide.

6. Reports for buyers

An Accessibility Conformance Report on the VPAT 2.5 international edition (covering Section 508, EN 301 549 and WCAG) will be available on request; we will give the date here.

7. About this statement

This statement was prepared on 31 October 2026 and last reviewed on 8 November 2026. Each version has its own id and date, and earlier versions stay available on our legal page.