Back to site

Legal

Accessibility Statement

Effective date: August 24, 2026

This document is a template for information only. It is not legal advice. Adapt it to your jurisdiction and operation before you rely on it.

Quathos Sign is used to sign documents that carry legal consequences. Someone who cannot use the interface cannot exercise a right — which makes accessibility a matter of fairness here, not a design preference. This page states what we target, what we have actually done, and what we have not.

1. Target

We build against the Web Content Accessibility Guidelines (WCAG) 2.1, Level AA. That is the target the interface is designed and reviewed against.

2. What is implemented

These are in the product today and are checked as part of development:

  • Keyboard operation throughout, including the signing flow, with a visible focus indicator and a skip-to-content link.
  • The sticky header never hides while the mobile menu is open or while focus is inside it, so focus is never obscured (WCAG 2.4.11).
  • Motion is reduced or removed when the operating system requests it (prefers-reduced-motion) — animated openings become static.
  • Light and dark themes, with contrast checked against the AA thresholds.
  • Semantic landmarks, labeled forms, and error messages tied to their fields, so screen readers announce what failed and where.
  • Loading states keep their text label in the DOM rather than replacing it with a spinner, so nothing goes silent for a screen reader.

3. What we have not done

We have not commissioned an independent accessibility audit, and we hold no VPAT or ACR. No formal user testing with assistive technology users has taken place. Documents you upload are your own files: if a PDF is an unlabeled scan, we cannot make it accessible to a screen reader, and neither the signing flow nor the evidence report can fix that at our layer.

4. Known limitations

Placing signature fields on a document is a spatial, drag-and-drop task, and it is the least accessible part of the product today. If this blocks you, contact us — we will help set up the envelope, and we treat these reports as defects, not as support tickets to close.

5. Telling us about a barrier

Email contact@quathos.com with what you were trying to do, the page, and the assistive technology you use. We will acknowledge you and tell you whether it is a fix, a workaround, or something we cannot solve — and if it is a signing deadline you are up against, say so and we will prioritize accordingly.