Accessibility Statement

SealMySignature is built so that everybody can send, sign and check a document, including people who use a keyboard instead of a mouse, a screen reader, voice control, magnification or high contrast settings. This statement says what we aim for, what it covers, how we check it, where we fall short today, and how to tell us about a problem.

1. Our Target

We aim to meet the Web Content Accessibility Guidelines (WCAG) 2.2 at Level AA. Accessibility is part of how the product is designed, built and released, and a change that would add a known Level A or Level AA problem does not ship.

We do not use an accessibility overlay or any widget that rewrites the page for you. The pages themselves are built to work with the tools you already use.

2. What This Covers

• The public website, including pricing, sign-up and the Verify a Document page.
• The application people use to prepare, send and track documents.
• The signing pages a recipient opens from an email, on a computer or a phone.
• Public signing links: the form a person fills in to start a document on their own.
• The emails the product sends.
• The PDF files the product produces: the signed document and the certificate of completion.

3. How We Check

• Automated checks run on the public pages, the sign-in screens, the signing pages, the application and the operator screens, in the light and the dark colour scheme, before every release.
• The complete journey is walked by keyboard alone before a release: signing up, uploading a document, placing fields, sending it, signing it and downloading the result.
• A screen-reader pass of the same journey is part of the release review. The date of the last one is in section 6.
• Pages are checked at a width of 320 pixels, the width a 400% zoom leaves, where the content has to reflow without scrolling sideways, and the contrast of text, controls and focus indicators is measured against the ratios WCAG sets.

4. Known Limitations

These are the gaps we know about as of October 13, 2026.

• Scanned and image documents. A document uploaded as an image, or a PDF that is a scan, carries no text a screen reader can read, and the product cannot add it. If a recipient uses a screen reader, upload a PDF with real text or a Word file instead. Text recognition for scanned documents is under consideration, and this statement will say when it is available.
• The structure of your own PDF. A PDF you upload keeps its text, so a screen reader can read it. When several documents are combined into one file, the product keeps the language of the first but not the headings or tags your files came with. The product does not add headings or a reading order to your own file, because the signed document has to be the one that was sent.
• Signing in. People with an account sign in with a password, and an authenticator app is an option. Password managers and pasting work in every sign-in field. A passkey or a sign-in link sent by email is not offered yet.
• The certificate of completion. The certificate is a tagged PDF: a title, a language, headings, tables with header cells, and a description on the QR code and on each signature image. The copy that combines the signed document and the certificate into one file is not tagged, and no file is certified to PDF/UA yet.
• Dense signing pages. On a page with many fields close together, an error message can sit over the next field. The list of outstanding fields at the bottom of the page reaches each one.

5. Tell Us About a Problem

If something in SealMySignature is hard or impossible to use, write to [email protected] with the subject Accessibility. Say which page or email it was, what you were trying to do, and the browser and any assistive technology you use, if you know them. A person reads every message and answers within five business days.

A problem that stops you from signing a document is treated as urgent and answered first. If an organization sent you a document you cannot open or sign, you can also ask that organization for another way to sign it.

6. This Statement

This statement was last reviewed on October 13, 2026. The last keyboard pass of the complete journey was on October 13, 2026. The first screen-reader pass is scheduled before the next release and its date will be recorded here. The statement is versioned: the version and the date it took effect are at the top of the page. We review it whenever the product changes in a way that affects accessibility.